I love to bash MS, but this feels like an industry-wide trend to /never/ care about optimizing beyond the bar of “typical specs of new devices in rich countries”. I’m guessing it’s just to limit labor costs, and computers are less-rapidly-improving than the 90s/00s?
Browser canvas is one of the worst culprits: it has to keep a buffer with an uncompressed bitmap several screens in size.
Old browsers used to keep a single screen worth of canvas buffer, then redraw stuff as you scrolled… which made it a horrible experience. You can still find some of that with “clever” web designs where they replace fonts or move things dynamically as you scroll.
Then you have websites with “infinite scroll” that just keep increasing the canvas buffer size more and more and more, to infinity and beyond… and people wonder why their Facebook or Reddit tabs use so much RAM.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
I love to bash MS, but this feels like an industry-wide trend to /never/ care about optimizing beyond the bar of “typical specs of new devices in rich countries”. I’m guessing it’s just to limit labor costs, and computers are less-rapidly-improving than the 90s/00s?
Code optimization has pretty much fallen by the way side since ram prices keep going down and cpu performance keeps improving.
Why spend the time if you don’t have to?
Browsers are some of the worst culprits.
Browser canvas is one of the worst culprits: it has to keep a buffer with an uncompressed bitmap several screens in size.
Old browsers used to keep a single screen worth of canvas buffer, then redraw stuff as you scrolled… which made it a horrible experience. You can still find some of that with “clever” web designs where they replace fonts or move things dynamically as you scroll.
Then you have websites with “infinite scroll” that just keep increasing the canvas buffer size more and more and more, to infinity and beyond… and people wonder why their Facebook or Reddit tabs use so much RAM.
Just for the sake of a beautiful audited and blazingly fast codebase that tuns qo good that Raspberry Pi user can run your stuff too.
I love optimisation!
premature optimization is the root of all evil - Donald Knuth
which does not excuse a total lack of optimization, but gotta hit those kpi’s
if it remember it correctly it was said in relation to algorithm optimization > code optimization