4 ms·
Hijacking the thread (bear with me). Is f# a good language to work with in Linux servers? Is possible? Would you recommend it?
by spanxx 7y ago
Hijacking the thread (bear with me).
Is f# a good language to work with in Linux servers? Is possible? Would you recommend it?
- manojlds 7y agoWith .NET core in place, definitely yeah.
- adgasf 7y ago.Net Core makes this work very well.
- dustinmoris 7y agoAbsolutely. F# is just one of 3 languages which you can use to develop .NET Core applications. .NET Core itself is cross platform and really well supported on Linux and macOS. The other two languages are C# and VB.NET, but personally I think that F# is just the nicer of the three. It's also worth noting that .NET Core is not only cross platform, but an extremely performant runtime which really hits the ceiling in various benchmarks https://www.techempower.com/benchmarks/#section=data-r17&hw=ph&test=fortune&l=hra0hp-1 https://www.techempower.com/benchmarks/#section=data-r17&hw=...
- BorRagnarok 7y agoNot really, and the highest Core test spews errors in that test. [0] [0] https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/
- oblio 7y agoI see 1 error for: aspcore-ado-pg
- libria 7y agoI'm trying to imagine that one tortured soul out there doing VB.NET on macOS.
- merb 7y agoto be fair most tests in this benchmark are not real world. most stuff above 150.000 is basically cheating. .NET Core including. Which sane person would would write a whole app with app.Run(async context => { await context.Response.WriteAsync("Hello, World!"); });
- nulagrithom 7y agoWhile we're hijacked... Is F# still the red-headed step-child of Core? Last I fiddled with it F# was looking pretty unloved, but to be fair C# was still having a hard time with Core itself.
- phillipcarter 7y agoSounds like you popped in before mid-2017 when things were rough all around. F# is fully supported on .NET Core and, including tooling in VS. Give it a shot!
- McWobbleston 7y ago> Is F# still the red-headed step-child of Core? Yup. Although this doesn't really come into play with server code in my experience. I don't imagine I'd want to deal with it writing WPF / UWP things though where language support is more important Even then I might just write the business logic in F# and glue things together with C#
- wyoung2 7y ago> I don't imagine I'd want to deal with it writing WPF / UWP things though where language support is more important As the article points out, there never has been any visual forms designer type stuff for F#, so if you're writing a GUI app with F#, it's best to wrap it in a C# shell anyway. Which is fine, because you wanted to separate your core application logic from the GUI anyway, right? > I might just write the business logic in F# and glue things together with C# It's a perfectly reasonable way to go. The only difficulty is that it simplifies things if you don't try to do all the fancy FP stuff at the boundary between the F# and C# parts of the app. While there are ways to pass, say, a tuple from F# to C# and cope with it on the C# side, it's better to limit types at this interface to things both languages support as first-class citizens: arrays, objects, simple scalars, etc.
- infiniteseeker 7y agoI asked the same question and basically my findings are that unless you need .Net, stick to Ocaml for *nix systems
- Nelkins 7y agoYup. I said so in another comment on this thread, but I've got a decent amount of code (30K LOC) running in a combination of AWS Lambda and Docker containers. Been doing it for just over a year now, it's working very well for us.