4 ms·
You realize having to write better code is a bad thing, right? It makes writing software more expensive, and decreases the supply of people who can do it. Also
by Strilanc 11y ago
You realize having to write better code is a bad thing, right? It makes writing software more expensive, and decreases the supply of people who can do it.
Also, people aren't going to start valuing craftmanship because you added more constraints. Adding a speed constraint won't make the pile of hacks upon hacks smaller, it will add a layer of speed hacks. It won't fundamentally rewrite the incentives for software, where companies that do the minimum amount of work to hit an acceptable speed are rewarded. It just culls companies naive enough to think they could write something elegant or concise.
- JustSomeNobody 11y agoSo? I see that as good.
- justincormack 11y agoZero cost abstractions are a great thing. Rust is working towards this. Readability and speed is a great goal and there is no reason to believe it cannot be achieved.
- Strilanc 11y agoThose are great developments, and they shift the pareto curve of cost-vs-readability-vs-speed downward, but the curve is still there.
- GFK_of_xmaspast 11y ago> It makes writing software more expensive. As someone who gets paid for writing software....
- TeMPOraL 11y ago... as little as your boss can get away with, and who pressures you to write it faster...
- mrrrgn 11y ago> It makes writing software more expensive, and decreases the supply of people who can do it. That sucks for business types, but this has a real upside for professional programmers. Despite propaganda, salaries are based on supply/demand, not impact.