←back to thread

Why F#?

(batsov.com)
438 points bozhidar | 3 comments | 01 Apr 25 12:34 UTC | HN request time: 1.073s | source
Show context
darksaints ◴[01 Apr 25 18:08 UTC] No.43549778[source]▶
I'm completely convinced that F# (along with Scala, Haskell, and OCaml) adoption has stalled due to having ridiculously bad build systems. More significantly, they are being passed up in favor of Rust, which is a great language but nonetheless a bad fit for a lot of problem domains, simply because Rust has a superior build system. Hell, 80% of the reason I choose Rust over C++ for embedded work is because of the build system.

It baffles me that there are languages with non-profit foundations and are financially backed by multiple corporations which still have bad build systems. It is the most important investment you can make into a programming language.

replies(7): >>43551301 #>>43552671 #>>43554790 #>>43554888 #>>43555737 #>>43556392 #>>43559547 #
1. DeathArrow ◴[02 Apr 25 08:49 UTC] No.43554790[source]▶
I would call .NET build system excellent.
replies(1): >>43558123 #
2. fodkodrasz ◴[02 Apr 25 15:56 UTC] No.43558123[source]▶
Lets settle on a finally good enough. I can give honest compliments on learning from the past problems and from the better examples in the indsutry.

You may not remember the early .net core times with yeoman and other then-current javascript ecosystem originated things applied in really cumbersome, half-assed ways, with lacking docs and always being in flux for years. The project.json era was terrible.

Also msbuild was way worse 10-15 years ago...

Mono with automake was special circle of hell IMO, I have very small exposure but it was really unproductive and painful.

replies(1): >>43558788 #
3. jayd16 ◴[02 Apr 25 16:59 UTC] No.43558788[source]▶
Whats pretty interesting is how outdated opinions of .NET are so sticky. Are we talking about what javascript was like 10-15 years ago?

I guess Microsoft could really make some headway if they got more folks to try it today.