8 ms·
As another F# enthusiast, I share the sentiment, but practically speaking I don't think F# would have been in any position to be the Python of today. It might h
by iammiles 6y ago
As another F# enthusiast, I share the sentiment, but practically speaking I don't think F# would have been in any position to be the Python of today. It might have had a greater chance if .Net Core existed 15 years ago, but being tied to Windows was a big show-stopper regardless.
- bmitc 6y agoI agree that my comment takes into account too much hindsight, but certainly this is part of the pain. If Microsoft had transitioned .NET to be cross-platform much sooner or from the beginning, then they would have been better off. I was recently surprised to learn that Mono basically existed from the beginning of .NET, as I had no idea it was so old, so it's clear that people wanted something like .NET Core from the beginning. It's confusing to me that Microsoft embarked on their Iron <x> project, or whatever it was called, to stress test the CLR, got F# out of the project, and then decided to sit on it. They have incorporated F# features into C#, but it is confusing to me that they saw the rising popularity of Python and decided to let it happen unchecked because C# will never be F# or a language that appeals to Python programmers.
- lostmsu 6y agoIt worked on Mono