3 ms·
Simplicity, speed, abstraction: Choose two https://cs.stackexchange.com/questions/57904/why-do-we-have-to-trade-abstraction-for-speed https://cs.stackexchange.
by simonh 9y ago
Simplicity, speed, abstraction: Choose two
https://cs.stackexchange.com/questions/57904/why-do-we-have-to-trade-abstraction-for-speed https://cs.stackexchange.com/questions/57904/why-do-we-have-...
- fhood 9y agoCorrect me if I am wrong, but I believe that interpreted vs compiled has far more to do with python's speed then abstraction in this case. Also the post you linked literally states that abstraction doesn't necessarily mean slow.
- mirashii 9y agoIf making a language compiled is a magic bullet for speed, why isn't every language compiled? Because they have different levels of abstraction that lend their implementation to compilation or interpretation. You're just citing a specific example of one of the tradeoffs made in the language design that falls along those three axes.
- cat199 9y agochez scheme, choose one.
- LrnByTeach 9y agoThis "choose Two" mantra captures essence of tradeoffs among the modern popular programming languages Go, Python, Java, C++, C, JavaScript > Simplicity, speed, abstraction: Choose two https://cs.stackexchange.com/questions/57904/why-do-we-have-to-trade-abstraction-for-speed https://cs.stackexchange.com/questions/57904/why-do-we-have-...