I agree with the sentiment, but in his linked project he says this:
Somewhat surprisingly, Trifecta does not touch the images it serves. This is a bit sad since it might be useful for the software to create thumbnails for example. The security record of most image libraries however is sufficiently depressing that it is not worth the cost to do any kind of conversion.
Apparently leaking EXIF data to the internet is not a concern of his.
Old enough to remember when folks took pride in how few lines of code they could write to get something done. Not unreadably dense undocumented code. Just lean, clean, and efficient.
There's still a place for large complex software, but 99% of business apps that just move text strings, datetime values, and decimals around from point A to point B aren't that place.
See it’s actually fine because computer power is just always going to get better and the next gen will handle it all fine.
Oh and there is definitely no reason to try and reduces electricity usage. See cause we’re totally going to run everything on solar panels any day now and we can just scale that up forever to meet demand without any problems.
Obviously, sarcasm. It is kind of infuriating how little a lot of companies care about keeping stuff lightweight.
Personally I’m very interested in projects to build functional lightweight systems and architecture, particularly stuff that could run on older process node chips. Like stuff that could be made without colossally complex supply chains.
What might be interesting is to go through some archive of old, say, accounting software and find whatever was really the best. Maybe something that ran on an IBM mainframe in the 70s or something, but got upgraded decades ago. Lo and behold we discover this software from the past (with some modern tweaks) is the best accounting software ever, and it can run amazingly on earlier node architecture that is extremely simplistic to adapt to modern architecture.
Join the cult of embedded engineers! My current project at work uses a cortex m0, so we have 32kB of code ROM and 4kB of RAM. It's really satisfying finding little optimizations to save a couple dozen bytes here or there, and there's never the pressure to just slap together code without worrying about size or speed since you can't afford it with the hardware you're using
It is exceptionally painful to read Niklaus Wirth’s article A Plea for Lean Software from 1995, which laments that 1995 era software needed whole megabytes, and then goes on to describe the Oberon Operating System which he built which needed only 200KB, including an editor and a compiler. There are now likely projects that have more than 200KB of YAML alone.
berthub.eu
Hot