4 ms·
Let's say we buy into the Java Trap Hypothesis; the question then is: what's next? What do you choose if you're a corporation with large projects and large team
by matrix 16y ago
Let's say we buy into the Java Trap Hypothesis; the question then is: what's next? What do you choose if you're a corporation with large projects and large teams of mostly non-rockstar developers. For the sake of the argument let's assume the JVM is out, and you can't use .Net (e.g. need Linux, or more flexible licensing, etc). I'm curious what people would choose, if given a clean slate for this kind of situation.
- ciupicri 16y agoFor Linux there is Mono for Linux and it has a pretty liberal license, a mix of MIT/X11, LGPL, GPL and MPL[1]. [1] http://mono-project.com/License http://mono-project.com/License
- alextingle 16y agoC? C++? (Or are you seriously suggesting that the average Java programmer is too feeble-minded to learn how malloc/free or new/delete work?) Python is a great choice too, provided you don't mind about performance (which is true in the majority of applications).
- jrockway 16y agoHaskell. Faster than java, easier than java, safer than java. And it even has a centralized repository of libraries.