samual.uk
Software Developer. 22
https://samual.uk/
94 posts
97 followers
898 following
Active Commenter
comment in response to
post
I opened it up in Helix with wat_server configured and it right away notified me I had an unused local. thank you!
helix-editor.com
comment in response to
post
here's my implementation of sha256 in WAT if anyone's curious
gist.github.com/samualtnorma...
comment in response to
post
linux drivers
comment in response to
post
I don't think the pope is christian
comment in response to
post
looking forward!
comment in response to
post
america is the world and jsx is react
comment in response to
post
ty! I thought I heard it from a podcast. this is a great blog post though!
comment in response to
post
I don't think it matters what us developers think. I once heard a story from @jakearchibald.com that goes along the lines of "there is a doctor's website and 2 browsers, one browser shows an error message, and the other browser just shows the website". which browser would the user think is better?
comment in response to
post
I don't think this sort of thing is big deal
comment in response to
post
why do you think it helps no one?
comment in response to
post
sorry, am I being rude?
comment in response to
post
then I think your real problem is with the naming of "warning" and "error". a warning is a diagnostic you will be shown and nothing else. an error is a diagnostic you will be shown and will stop CI. if both warnings and errors stopped CI, what would be the point of the distinction?
comment in response to
post
warnings aren't enforced which means they inevitably get ignored so might as well not exist. lint warnings were a mistake and all lint errors should be errors
comment in response to
post
no this is just dodgy HDR support
comment in response to
post
this was a great listen!
comment in response to
post
most of us don't do that
comment in response to
post
it's a known thing outside of programming that gradual change over time is easier in the long run than short and sudden change
comment in response to
post
being apolitical is a fantasy. it's just that usually people's opinions line up with the status quo and that's what they think being apolitical is
comment in response to
post
great work! does the mini library take any inspiration from valibot by any chance?
comment in response to
post
justforfunnoreally.dev
comment in response to
post
I know this is a nonsense baseless graph, but what is the Y axis supposed to represent? I would also bet a lot of money that "traditional" programming will not be dead by 2027
comment in response to
post
yes but I think it's still valid to fear the same thing will happen again
comment in response to
post
mine uses `
comment in response to
post
we already have had a v2 language on the web, XHTML, and it was a resounding failure. even if we did get JS v2, people will keep targeting JS v1 anyway and it'll be years before developers start targeting it. I think time is much better spent on making WASM more competitive with JS
comment in response to
post
you know why
comment in response to
post
know what they do, I would advise to remove them for now and add the complexity as and when you need it. otherwise I'm sure I can figure it out
comment in response to
post
okay so I'm reading more into it, and it looks like the template is also setup to be a pnpm monorepo which I've also not used (I tried it out but couldn't use it for technical reasons) and Changesets is a tool that has really good support for monorepos. if you don't need both these things and don't…
comment in response to
post
I can help with other more general stuff though
comment in response to
post
I see you're using Changesets which I've never used before so I won't be able to help with that
comment in response to
post
ah do you mean push the commit that `npm version` creates? if so yes I do, and then once I've `git push --tags`'d it, I go on GitHub and create and write a changelog for the release from the tag that then triggers my workflow
comment in response to
post
also no problem, happy to help!
comment in response to
post
uhh what do you mean "commit the changes from npm"?
comment in response to
post
version (for example 0.21 github.com/samualtnorma...) and start cherry picking commits to it from the main branch. you also have the option of just committing or merging PRs straight to it
comment in response to
post
quickly and make releases often whereas some don't. if your unsure whether the version increment should be major/minor/patch, you should read Semver semver.org. sometimes you might need to backport fixes to an old major/minor version in which case I create a branch named after its major.minor…
comment in response to
post
where `npm` will automatically increment the version number in your package.json and create a git tag for you. you'll then want to make sure to `git push --tags` that tag so it appears on the remote. as for when to create these tags, again it's up to personal preference. some projects move very…
comment in response to
post
okay so all of this is up to personal preference. what I personally do is have a branch named main that all changes go to (for a team PRs will be merged into it, most my projects are solo so I commit directly to it), since your project is an NPM package, you can run `npm version major/minor/patch`…
comment in response to
post
if your project is open source, I wouldn't mind opening a PR to add a super minimal workflow and then let you go from there
comment in response to
post
the basic idea is to use the pre-made github action to setup Node.js (and PNPM if you're using it) and then just do what you'd normally manually do in the workflow (build and then run (p)npm publish
comment in response to
post
are you using github? if so, have you used github workflows before? here's an example one of my workflows for auto publishing github.com/samualtnorma... mine may be a little overkill for your needs however (mine also does dev releases and provenance)
comment in response to
post
I was there right for the tail-end of webpack's life and only ever used webpack for 1 project. I've long since switched to rollup and vite and never looked back. I definitely apreciate it
comment in response to
post
Large Language Model or LLVM?
comment in response to
post
(but probably a joke)
comment in response to
post
ignorant take
comment in response to
post
in your article you imply the main motivator for deno moving away from http imports is so they could have wider adoption faster but if you read deno's article it is clear that is not true
comment in response to
post
or Grok on X the everything app
comment in response to
post
Dan is talking about Lean the programming language lean-lang.org not recreational drug use just in case anyone is confused
comment in response to
post
it's on by default as of 23.6
nodejs.org/en/blog/rele...
comment in response to
post
nice! I've now updated my cookie library github.com/samualtnorma...
comment in response to
post
unocss.dev/presets/icons