>>95
What's so fucking hard about making sure the memory you're using is the right size? You don't even have to estimate, just count! It's so simple it should be common sense, and yet it isn't...
Don't ask me, my code is fucking perfect. Ask the fucktards whose commits I have to watch over because around 20% introduce a major security flaw. You've never worked in a team project? Then fuck your shit. I want something that the retards I have to keep in line can use without doing too much damage -- and I know damn right that it ain't C (or C++, I simply can't imagine what creative abominations they'd come up with if allowed to use C++).
Ignoring the reality and trying to cover it up by inventing more shit on top of it doesn't make it go away.
If someone writes shit
<proper low level language>, the only way I can fix it is by reverse engineering it and doing a full rewrite (the next person who submits complex code without commenting nor accompanying documentation I swear I will key their fucking car). If someone writes shit in
<proper high level language>, at least I can somewhat optimize it (assuming the code isn't completely broken), for example, by using more specific (typed instead of generic, in dynamically typed programming languages) data containers, at least in the cases where the JIT's type inference can't figure shit out. In any case, the code will be shorter and easier to read and hopefully I won't have as much work to do.
All in all, you are half of what is wrong with this world. The other half are the fucking java monkeys who just fell out of the TreeFactory and hit every enterprise branch on the way down.
a.sdkfjas;lkfjw I hate the world
;_;