Size Optimization Tricks

I started with a 0.9 MHz system with 64.5 kB of RAM. And plenty of people have started with even less.

By the time we were at 386s, code bloat was already pretty bad.

Bad energy wasting performance is even worse than bloat. I'm horrified how much electrical energy bad code costs. We're already talking about a bunch of nuclear powerplants' output wasted!

Author here. We learned this a couple weeks ago when I blogged about logging C functions. https://news.ycombinator.com/item?id=31443198#31444751 I've been in contact with several employees trying to get it resolved. One of our regular contributors is even a staff security engineer at Amazon and he's just as confused about what's happening as the rest of us. There's a real lack of transparency so far on the part of Amazon and there's no official channels for appealing these sort of black box decisions. It's a real shame, since this isn't just my blog, but it also represents all the people who've been working hard to contribute. If we've been blacklisted by a company like Amazon then I'd like to at least know what's wrong and what steps I can take to address the situation.