This keeps escalating... It needs to be stopped.
I personally think this is where it'll head after the bubble pops. We should be able to recover enough material to have something viable to run locally. The question will be "where the updated models come from?", it might be the public sector helping there and hopefully those will be truly FOSS and ethical (like Apertus).
Most JS projects end up incredibly bloated indeed. Luckily there are ways to improve the situation.
Indeed, it looks like Windows gave up on having a nice experience for native app development a while ago...
Interesting trick in Got, using SSH certificates to prove the origin on commits. This feels a bit rough though, tooling has room for improvement.
Interesting proposal for rust borrow checker. I wonder if it'll get any traction.
Interesting call, our field like anything undertaken by mankind is worthless without community. Also community can't sustain if you got an anti human agenda.
Yes the naming of resolutions is a mess... Couple that with marketing and it becomes misleading quickly.
Interesting story on how sometimes you can be betrayed by your memory allocator.
Indeed, there's no rush. No need to be first to jump on every new fashion.
The writing is on the wall I think... the real question is not if but when will the enshittification begins? It's been data harvesting for a while now.
This was stupid hype... Why do we have regularly this kind of fever in our industry?
Lots of interesting tricks in this code base. Gives also a good idea of the shape and tradeoffs of such ports.
So much this... I'm sick of all those little businesses having only an Instagram or Facebook account or whatever. I wish we'd have proper websites for all of those instead.
A very good talk which walks you through how to move from object-oriented design to data-oriented design. Shows quite well how you must shift your thinking and the difficulties you might encounter with data-oriented designs. I appreciate a lot that it's not just throwing object-oriented design out of the window, indeed you have to pick and choose depending on the problem space. Also it's interesting to see how C++26 reflection might make some of this easier.
Good explanation of where WebAssembly is going and why the current initiatives are important to its success.
Not all CPUs are born equal in term of branch prediction. Interesting little benchmark.
This is an account of how dark things can become when you align your identity with your contributions. Stay healthy, stay safe!
These are good rules. Take inspiration from them.
Nice little quality of life improvements coming to std::span in C++26.