21–30 of 31 posts
Is F# support ready for Prime Time?
Earlier quoted context omitted.
.Net isn't IIS. It's just one web server that can host it. And I'd take IIS over WebSphere any day!
Me too. Websphere is such a pain to use, yet it still is everywhere on enterprise projects.
Earlier quoted context omitted.
Me too. Websphere is such a pain to use, yet it still is everywhere on enterprise projects.
Curious to know why you think WebSphere is a pain - I find it about as good as any complicated piece of software can get - it's reasonably documented, works most of the time and performance is good.
It is the typical enterprise software suitable to sell consulting experience in what concerns configuration and management.
Endless list of configuration options, some of them only available via scripting and best of all IBM J9 specific features.
One of the issues we once had around 2006 was that our entity beans stubs would only work properly if compiled via J9.
It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.
I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…
I am looking F# for CoreCLR status page, https://github.com/Microsoft/visualfsharp/wiki/F%23-for-Core... Is F# support ready for Prime Time?
It's a good start, lot of things work, lots doesnt.
Is for early adopters but it's not bleeding edge anymore i think. Not ready for production
F# using .net core sdk from command line works (new, restore, build, run, test, publish) like c#.
xplat is ok where .net core is supported, so osx/ubuntu/win/docker.
Docs need some improvements, but lots are language agnostic, or c# examples help (docs are open source, if someone want to help).
Important wip or not implemented yet feature of compiler/language:
- type providers
- portablepdb for enable debugging
- f# repl
The f# libraries in ecosystem are starting to support .net core (netstandard), like FSharp.Compiler.Services (the compiler as library), Suave ( github.com/SuaveIO/Suave-CoreCLR-sample ), Argu, Fable. These are not hello world examples, so it works. Some are in prerelease, but it's expected because it's a new framework/tooling and need testing.
There are only few libraries of the f# ecosystem who support .net core, but it's expected because is a bootstrapping issue in lot of cases (i need to wait .net core support for my dependencies add support..)
Obv it's possibile to use all others .net libraries who support .net core (netstandard) like the BCL, Kestrel, etc.
As editor, vscode has the best support using usual the amazing Ionide plugin for f# (who already give f# support for .net and mono). Intellisense, build, run is ok but not debugging.
Using Visual studio, only build/run works (xproj and project.json), but not intellisense or debugging.
If you want to chat there are two good f# slack groups
- #dotnetcore in fsharp.org slack (other chan too)
- #fsharp in fpchat.com
I am looking F# for CoreCLR status page, https://github.com/Microsoft/visualfsharp/wiki/F%23-for-Core... Is F# support ready for Prime Time?
Earlier quoted context omitted.
Curious to know why you think WebSphere is a pain - I find it about as good as any complicated piece of software can get - it's reasonably documented, works most of the time and performance is good.
I used to know Websphere quite well (all the 5 - 6.x versions) and am happy to have managed to avoid it in the last three years. It is the typical enterprise software suitable to sell consulting experience in what concerns configuration and management. Endless list of configuration options, some of them only available via scripting and best of all IBM J9 specific features. One of the issues we once had around 2006 wa…