5 ms·
> like Sun's Open Look clock tool, which gobbles up 1.4 megabytes of real memory Meanwhile the clock app on my phone is currently using 12 MB. A popular time t
by gok 7y ago
> like Sun's Open Look clock tool, which gobbles up 1.4 megabytes of real memory
Meanwhile the clock app on my phone is currently using 12 MB. A popular time telling website uses over 100MB on my laptop.
- tinus_hn 7y agoIs it http://whattimeisitrightnow.com/ http://whattimeisitrightnow.com/
- gok 7y agoThat was what I looked at yeah, and I appreciate that it's actually a Netflix gag site for Bojack Horseman but still.
- donio 7y agoIt's like the Eight Megabytes And Constantly Swapping joke for Emacs. These days a minimal Emacs is more like 18MB RSS rather than 8 but that's still tiny compared to modern apps.
- speedgoose 7y agoI don't know about your phone but mine which is not new has 6gb of ram and the latest Samsung s20 flagship has 12gb of ram. In comparison to the total ram, it's much better nowadays.
- 0xff00ffee 7y agoI bet 99% of that 12MB is graphical assets: different sized icons for different display geometries. I always found asset management for multiple platforms to be most annoying when developing for mobile. This reminds me of when people started to realize Microsoft Foundation Class (MFC) was blowing up and were bemoaning code-bloat. In 1997.
- hermitdev 7y agoThe very mention of MFC gave me shivers down my spine. The macro horror show and indecipherable error messages... Thankfully, I never had to do much MFC professionally, but holy shit, if you inadvertently messed with one of the generated macros, good luck. I remember it sometimes being easier to throw away everything and start from scratch than debug the horrible compiler errors.