2 ms·
Much easier question to answer: there aren't that many of them, and network effects are important. There's a reason code-bases like Facebook Chat get successfu
by derefr 10y ago
Much easier question to answer: there aren't that many of them, and network effects are important.
There's a reason code-bases like Facebook Chat get successful, and then get rearchitected from niche languages (Erlang) to popular languages (C++), and it isn't ease of development or quality of result. It's the ability to hire people to maintain the thing. And, in large corporations, that reason is usually considered early-enough on that nobody lets development happen in such languages in the first place.
As such, it's only small ISVs that will end up using niche languages. (Sometimes small ISVs that get crazy successful—like WhatsApp—but still, small.)
Even then, the problem is that a code-base that's full of elegant abstractions... is still a codebase you have to learn. The fact that not everybody understands those abstractions is a bad thing for hire-ability, just as much as it's a good thing for ease-of-development and maintainability.
It's just like use of macros in a code-base: they (usually) make the resulting code better once you have taken the time to understand it—but the code starts off more opaque to anyone who hasn't yet taken that time.
Haskell's elegance happens when people who read math papers write software. People who haven't read those math papers can't maintain that software. Thus: Not Viable In The Enterprise.
And, to bring the point home: if you write better software, at the same speed, you can win as an ISV, because your software is, well, better. But if you merely write the same software faster (or for less cost), your bigcorp rival is going to win. No customer cares about how little time or money it took you to build the software. They just care about the result. If FooCorp can spend 10x the resources to make a product that's 10% better than yours, they'll still capture your whole market.