• 16 Posts
  • 3.38K Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle
  • First of all, biodegradable doesn’t mean what you think it means. For example, PLA plastic is biodegradable - good luck trying to compost it at home.

    Second, source material doesn’t mean that the end result will be biodegradable as well. You will need to polymerise them and you’ll end up with the same plastic and rubber as if you’d use oil. PLA is an example again! It’s made from lactic acid, which you can and do eat. You can also eat pure PLA, but again - it’s not compostable.




  • All these packages don’t take much memory. Also tree shaking is a thing. For example, one of the projects I currently work on has over 5 gigs of dependencies, but once I compile it for production, the whole code based is mere 3 megs and that’s including inlined styles and icons. The code itself is pretty much non-existent.

    On the other hand I have 100KB of text translations just for the English language alone. Because there’s shit loads of text. And over 100MB of images, which are part of the build. And then there’s a remote storage with gigabytes of documents.

    Even if I double the code base by copy pasting it will be a drop in a bucket.








  • First of all, 350MB is a drop in a bucket. But what’s more important is performance, because it affects things like power consumption, carbon emissions, etc. I’d rather see Slack “eating” one gig of RAM and running smoothly on a single E core below boost clocks with pretty much zero CPU use. That’s the whole point of having fast memory - so you can cache and pre-render as much as possible and leave it rest statically in memory.





  • One frame for a 4K monitor takes 33MB of memory. You need three of them for triple buffering used back in 2002, so half of your 256MB went to simply displaying a bloody UI. But there’s more! Today we’re using viewport composition, so the more apps you run, the more memory you need just to display the UI. Now this is what OS will use to render the final result, but your app will use additional memory for high res icons, fonts, photos, videos, etc. 4GB today is nothing.

    I can tell you an anecdote. My partner was making a set of photo collages, about 7 art works to be printed in large format (think 5m+ per side). So 7 photo collages with source material saved on an external drive took 500 gigs. Tell me more about 256MB, lol.