Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The company I work for defaults to F# when choosing tech for a specific project.

We defaulted to PHP and C# in the past.

We have quite some experience training people who just graduated and even people with backgrounds outside of tech.

Training someone from zero to autonomously writing production code is a lot easier in F# compared to PHP and C#.

We educate people in Elm and Haskell and switch over to F# when they’re ready to try building the first real thing end to end.



F# is really a very nice pragmatic language. C# keeps cannibalizing features from it, which is both good and bad...


As a die-hard .NET/C# developer, I would be curious what you perceive to be the 'bad' side of that coin. I assume something like LINQ would be classified as 'good'?


What he meant by bad is probably the fear that MS will abandon F# once C# has borrowed enough features from it.


The other unfortunate is that as C# accretes features, the old still hangs around. Eventually you end up with too many valid ways of doing things, and cruft that either can't be worked around or was never updated.

It's been over a decade since generics were introduced, but I still encounter code using ArrayList today...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: