2 ms·
The sad truth from a corporate / enterprise perspective, popularity (or perceived popularity) means safety and checklist fulfillment. Management knows it can f
by protomyth 7y ago
The sad truth from a corporate / enterprise perspective, popularity (or perceived popularity) means safety and checklist fulfillment. Management knows it can find people to plug into its empty slots, and HR has a easy thing to look for on the resume. People like comfort and safety.
Now, you could say you are a startup and need the advantage. Good, you can do it, but you might have to supply more code to fill the gaps and deployment might require some extra knowledge (ecosystem problems). Its a value judgement as developer productivity isn't the only part of your development. Still, you can have a heck of an advantage. Look no further than the founder of this board, but remember the second part of the story. The Lisp got rewritten because it wasn't a comfortable choice for the new owners.
Perceived popularity means comfort and ecosystem.
- neilv 7y agoExactly. I've been arguing this for awhile. I'd go more specific than startups, to narrow in on those who are doing something unusual, such that they know they'll have to implement nontrivial stuff from scratch, no matter what language and off-the-shelf libraries/frameworks they use. That's one of the places that Racket can be a win. Related to that, I've also been trying to get people to stop saying "batteries included", because that's misleading, and sends the wrong message about what the actual relative strengths are. In practice, I suspect the initial startup adoption will largely be chance/serendipity, until there's at least one great startup success story, to interest and inspire confidence in other startup efforts. (I have one great success story, which was due to such serendipity, but it's a non-public system, and I've been milking that one way too long already in promoting Racket.)