Blog post comparing Vitest vs Jest

not sure how interesting to others, but i thought this was really cool.

(I am not affiliated with posthog at all. Just typed an incorrect address and came across it.)

Has anyone got any good resources for something like this? I haven't touched C in years, and never worked on anything game-like. But it does look like a really interesting project to start something like this.

If you have patience, the first 30 or so episodes of Handmade Hero are pretty good.

https://guide.handmadehero.org/code/

Handmade Hero is a bad idea for anyone wanting to learn how to make a game in C or C++. Casey intentionally avoids using standard libraries and frameworks and his irrational hatred of high-level code and modern standards will lead developers astray and waste their time.

Even if you're using C you don't need to implement your own renderer or do half the things he does. Get a library like SDL3 to handle the basics, maybe use Lua/LuaJIT for scripting. Learn OpenGL or Vulkan. Stay away from HH and Casey Muratori until you're experienced enough to tell the difference between his wisdom and his bullshit.

We'll have to agree to disagree on this one.

raylib is one possible starting place. Also might look at dos-like (https://mattiasgustavsson.itch.io/dos-like).

tldr - `tsc` can be replaced with `tsgo`. `eslint` replaced by `oxlint`, and `prettier` replaced with `oxfmt

this makes me want to play simcity again! really cool

just saw this today - "whenwords, a relative time formatting library that contains no code." I wonder with AI this will become a popular thing soon that we see other 'libraries' doing... provide good specs, leave it to AI (And trust ai) to interpret

ah i didn't see those. cool.

If GH has an issue, it seems to always be around 4pm or 5pm GMT. I'm starting to think that i should avoid any planned production releases around this time.

https://howtotestfrontend.com/blog Mostly blog posts about testing react apps, latest news about FE testing, Vitest / Jest etc.

while this approach is useful, i think the diff is too small to catch a lot of bugs.

i use https://www.coderabbit.ai/ and it tends to be aware of files that aren't in the diff, and definitely can see the rest of the file your are editing (not just the lines in the diff)