Spotify using several processes and GB of memory just play some music and browse a library is an abomination. WinAMP did most of that 20 years ago while using a fraction of the resources.
Discord similarly is an affront.
don’t worry, this will all be solved now with incompetent vibe-coders, just give it a while
or you will look back to this with a nostalgic tear in the eye. one of these.
If there’s any upside to the entire situation, it’s that perhaps, maybe, developers will again start paying more attention to optimization instead of just throwing more powerful hardware at it.
Some of the greatest games ever developed for consoles were great because the developers had to get extremely creative with the limited resources at their disposal. This led to some incredibly optimized games that could do a whole lot with those very limited resources.
You don’t even need to go that far back. It blows my mind that the 360 and PS3 have 512mb of RAM. Halo 4, GTA 5, and The Last of Us did some impressive graphics work with 512mb.
Oh wow my mind is blown. Even more so that it’s 256mb of DRAM and 256mb of VRAM separately.
We have really gone down hill and fast ;(
In my brain memory I find it hard to believe all the textures loaded at one time could ever be so small. Im amazed.
tbf, the PC version of console games of the time ran like utter shit on computers with less than 2GB RAM and graphics cards worse than a Geforce 9800. A lot of people were still on WinXP, which was bloated compared to WinME-2000, but by 2006 it was fine.
NodeJS is worse. One dude just had to write a cli based JavaScript runtime and holy hell now entire backends run on the least performant runtime possible.
You can bash the Javascript language all you want, but don’t come for its performance lol. Nodejs was very fast across the board when it came out, and still beats most scripting languages. Even some bigger runtimes in IO.
Its performance as a backend server is abysmal compared to standard compiled languages.
It’s absolutely wasteful to use it.
The reality is that most backends don’t use compiled languages, but stuff like PHP, Java and Python.
NodeJS scores very high on performance, concurrency, and especially IO, in that category.
And calling it abysmal compared to compiled languages is not fair, but yes, there are much better alternatives.
