Re:Rust in 2018: easier to use
by phillipcarter on Sunday January 14, 2018 @04:23PM
(#16146568)
(I work on F# at MS)
Do you remember the library? The landscape has changed dramatically in the past ~6 months with .NET Core 2.0 support. For example, I can use Fable[0] and Giraffe[1] with the .NET CLI[2] to build full-stack F# apps on my machine which runs .NET Core. The big remaining blocker for most people to just jump wholesale onto .NET Core and forget anything Windows-based is the lak of Type Provider support, but we're quite close to finishing that.
[0] http://fable.io
> The big remaining blocker for most people to just jump wholesale onto .NET Core and forget anything Windows-based is the lak of Type Provider support, but we're quite close to finishing that.
Is there a viable cross platform ui option for f# on core?
Check out https://github.com/AvaloniaUI/Avalonia
Re:Rust in 2018: easier to use
by phillipcarter on Sunday January 14, 2018 @06:46PM
(#16147292)
Yup! Fable. In fact, a web app written in fable will even run in more places than a .NET Core app due to the reach of browsers.
I was looking at Brahma.FSharp and something else with type providers, both with Nu Get instructions, and I didn’t see how to get it working with VS Code.
Re:Rust in 2018: easier to use
by phillipcarter on Monday January 15, 2018 @12:01PM
(#16151708)
Ah, yes, this is using Code Quotations to generate code into OpenCL. Useful, but unfortunately, not something that is likely to work on .NET Core for a number of reasons today.
As Python dev since 10 years I can't point fingers -- Python is probably worse though I've memorized the idiosyncrasies -- but I couldn't justify my way up the tooling learning curve in addition to the language curve.