veltas

Counterpoint, more than memory bugs exist, and everything's written in C. You're welcome to rewrite in Rust but you'll create countless bugs that aren't memory bugs that mostly already got fixed in the C version. I can't help but think things like fil-C are the most pragmatic route, despite performance costs, for most people relying on programs written in C.

It’s funny reading takes like this from software engineers that think the only way to meet people is at skateparks, and in… libraries...what?

They wanted shorter aliases for them to make their code clearer, I suppose.

Fact is that performance intensive code, games or whatever, has always optimised locality and so RAM speed shouldn't usually be a 1:1 impact on performance. Using older generations of slower RAM will be acceptable for many games and workloads.

As a counterpoint, you are lumping a lot and generalising a lot there, if we're specific then you can't really trivially replace e.g. the Linux kernel with an AI project in whatever language you want. An incredible amount of work has gone into the Linux kernel and its design, and the infrastructure under that veneer of a "UNIX kernel" is too significant to hand-wave away. The issues facing Linux are well beyond (but not excluding) those created by using a dangerous language like C, or using hacky/outdated UNIX interfaces and conventions.

Yes you can try and take things in an original direction but we're ignoring the incredible amount of work that's gone into Linux, solving most of the problems you can't imagine and that AI will burn though a lot of time and tokens trying to re-solve (badly, without a ton of intelligent intervention).

I think you're more likely to see more people experimenting with existing open source work, rather than generating new projects. These new projects are easy come, easy go.

Wouldn't they have to fine themselves first?

That's not what I see reported, they say Haskell tends to have bad memory layout generally and takes a 5x or so hit to performance.

They may have done you a favour if that's what they sack you for, good luck finding another job!

This is the sort of thing I've wanted to write for a long time. Yes it looks like this is vibe coded but I'm glad this was made because it's cool to see what can be done, and it's interesting seeing how AI can be used as a compiler essentially given the output is assembly.

I'd be interested if the author would tell us more about what they did here and what went into the design and evolution, rather than the AI README.

That's how I feel right now talking in my only language of English.

Don't overthink it, I think you are being a bit cynical. If your kid enjoys it then it's worth the money. If you can't afford that then find other things your kid enjoys.

The reward of a game is playing it, not the 'prize', although that can add to the enjoyment too.

That's actually the point of the .name TLD is that it's not for businesses, it's for individuals. This whole situation demonstrates ICANN is more for businesses than individuals. It should just be there for everyone and every organisation that's trying to use URI's, shame that it's not worked out that way. This is exactly what the big tech companies want, they might as well hand ICANN over to Facebook or Google, they wouldn't do much worse.

Okay but that's not really relevant as the name changing is not a reason to leave/boycott?