Comment Re:easy (Score 2) 484
There is quite a bit that is legitimate in criticizing the new trend of 400 layers of abstraction each adding their overhead for the sake of rapid development. Those old development models produced more stable and dramatically more efficient software. Nobody really denies that, they just argue that developer time is more valuable than computer time and improvements in hardware make up the difference in most use cases.
But what happens when hardware stops getting dramatically faster? We'll have to go back to making things more efficient to see gains and suddenly you'll have a great deal of respect for dad who could make a word processor with 90% of the functionality of word that weighed in under 1mb and ran smoothly on as little ram with a processor your smart phone could emulate 200 times over. There is a reason where the browser makers, the home of high level abstraction and high level languages, are finally all actually in agreement and collaborating and the thing that brings them together is making c/c++ compile to a uniform standard that all browsers can execute at near native performance.
The circle comes around, it always comes around.
But what happens when hardware stops getting dramatically faster? We'll have to go back to making things more efficient to see gains and suddenly you'll have a great deal of respect for dad who could make a word processor with 90% of the functionality of word that weighed in under 1mb and ran smoothly on as little ram with a processor your smart phone could emulate 200 times over. There is a reason where the browser makers, the home of high level abstraction and high level languages, are finally all actually in agreement and collaborating and the thing that brings them together is making c/c++ compile to a uniform standard that all browsers can execute at near native performance.
The circle comes around, it always comes around.