3 ms·
Switching to another language is often not very practical, especially if you're working as part of a large team, or need to leverage the ecosystem or community
by pmoriarty 10y ago
Switching to another language is often not very practical, especially if you're working as part of a large team, or need to leverage the ecosystem or community of that language.
If you're at a company who've standardized on Python, you can rarely just up and start writing your part of the project in Haskell (even if you know the language, much less if you don't and need to learn it first). And good luck convincing everyone else at your company or even just your team to switch from Python to Haskell (or whatever language you think is the right tool). People get used to their tools, get attached to them, and many won't part with them without a fight.
Then there are all the Python libraries that Python programmers have invested a significant amount of time and effort to learn and possibly even love, like numpy, pandas, scipy, etc. If you need the functionality from those libraries, now you not only have to switch languages yourself, convince everyone else on your team/company to use/learn it, but also learn whatever the equivalent libraries in Haskell are (if it has them).
Then there's all the Python code at your company that you often need to leverage or interact with. You generally aren't going to rewrite it all in Haskell, and you can't ditch it.
So if you're a one-man shop, or are a student with no commitments or demands from anyone else, sure, you can switch languages on a dime (assuming you already know the language you want to switch to). For everyone else, it's rarely that simple, unless those you work with are already fluent and comfortable with the other language and its libraries.