2 ms·
Because someday you're going to want someone other than yourself to work on the code. Or, even if you don't want it, the company will.
by AnimalMuppet 5y ago
Because someday you're going to want someone other than yourself to work on the code. Or, even if you don't want it, the company will.
- Zababa 5y agoHiring is another problem entirely. If you need lots of people very quickly it'll be hard for F# to compete with something else, but for every other case I don't think it's so clear cut. People that use and like F# really want to work with it, and are usually more experience programmers than people that know only C#. Thus, hiring for F# makes a great filter. Considering how hard interviewing and hiring is, having another signal is a good thing. Maybe building your startup that needs 100 new people every year on F# is a bad idea, but for enterprise projects that don't move much, it seems a reasonable choice.
- AnimalMuppet 5y agoHiring isn't a problem if you want to use a language for your own project or for your own learning. Do whatever floats your boat. Hiring (or having others on the team who can work on the code) is a problem if you want to use a language in a company. (I mean, it's not if you just want to write a one-off program. It is if you're writing a program that is going to survive for a long time and be depended on by others.)