I don't think compiler optimizations matter much - supposedly the final build was compiled without optimizations, presumably by mistake, and the N64 has very specific hardware which compilers don't know how to optimize for.
What we certainly do have are much more powerful machines and software in general, letting you test, analyze and profile code much more easily, as well as vast amounts of freely available information online - I can't really imagine how they did it back then.
I think CSS animations are enough, no JS needed
Take a look at what Kaze Emanuar is doing with SM64 if you're curious what the N64 can do with modern software practices ;D
Git might not count because you can have branches that then merge? But yeah, git is useful, it's decentralized and distributed, it could be used P2P...
Applications disappearing from the launcher because you changed the greeter sounds very weird... And that's kinda what I mean. You had to give up on using this software, and instead go for an alternative, because of an issue that shouldn't even be related.
Granted, a lot of people are probably fine with it, and it sounds like an annoying issue to debug... But it still rubs me the wrong way.
You do raise a good point about replacing software - even just in my example I neglected to mention myself switching to pipewire a couple times and figuring out how they work. Interoperability between software is valuable and knowing you can always switch out one part of your system for an alternative is indeed a useful skill - I sometimes see people complaining about things like Linux's clipboard, or archive manager, being bad, something like that, without realizing that's just one option you can use.
Depends on the issue, but many issues come from misconfiguration - fixing the issue can help you understand your system, what went wrong and why, and not only fix that issue ans help you fix further issues, but also reveal things you didn't know about the software. I find it valuable to know how things work, so I can understand what I'm using, what I need, and what I can do with it.
As an example, messing around with pulseaudio and pipewire I understood a bit more about how it works. I found out I could enable the built-in echo cancel module and get rid of virtually all of my echo when using speakers and microphone. I then later also knew how to configure multiple virtual streams, so I can separate games and voice chat from my browser, so when I record clips when playing with friends, I can have those separate. And then also configured RNNoise for systemwide noise suppression for that bit more audio clarity.
I could find instructions on how to do each of those without understanding them, but when I wanted to ensure noise suppression happens after echo cancellation, I knew what to mess with to set that up.
I understand it's not for everybody, it's not feasible for most people - but I see the system as a complex machine you need to operate, and while having simple controls is a good idea, understanding how the machine is built can help not just with complete breakages, but also with avoiding smaller inconveniences that come from using it in unintended ways
Not necessarily, it could be that if they put the work into something else instead they would've made more when you account for the fine, so it could still not be worth it compared to alternatives.
That's the thing - none of those would've affected you negatively if you've been using Nvidia, so if you're just playing games and not following the news, you're more likely to just hear people complain about AMD this, AMD that, they broke it... But everything works fine for you
I remember hearing that when AMD surpassed Intel in multithreaded performance, userbenchmark adjusted they're benchmark scoring to favor single threaded performance over multithreaded
I'm pretty sure most people love NVidia, since it's the popular option, generally works, and provides features that aren't available elsewhere, both in gaming and GPU compute.
Of course, most of NVidia's advantages come down to marketing and pushing for their proprietary technologies, while avoiding supporting niche users and refusing to release their code. The thing is though, if you use Windows, NVidia is probably the better choice from an end-user's point of view.
The person I was replying to said that valve prioritizes making things work before making them pretty.
I was giving a major example of valve making something broken in terms of functionality but pretty, to replace something that was less pretty but functional.
It is usable, and to me it's fine, but I just think it's not valid praise to give to valve in general.
I don't think that's a valid criticism, I don't see death saying that, it'd be more like "Your time has come" - to contrast it further, wouldn't somebody say "It's your time to shine"?