News for hackers. Stuff that matters.
Re:Rust in 2018: easier to use by Nelkins on Sunday January 14, 2018 @11:59AM (#16145000)
F# sounds like it fits the bill. ADT, pattern matching, performant, great tooling (multiple amazing IDEs, a REPL, etc.), and a huge ecosystem of software packages to use with it (all of .NET). It's my favorite general purpose programming language (can be used for frontend programming, server, mobile apps, etc.).
Re:Rust in 2018: easier to use by andendau on Sunday January 14, 2018 @03:09PM (#16146084)
F# has hit a huge sweet spot for me in productivity, strong typing, inferred typing, multi-paradigm and syntactic sugar. The tooling just gets better and better. I struggle to think of a language that's so well rounded.
Re:Rust in 2018: easier to use by carlmr on Monday January 15, 2018 @10:07AM (#16150909)
Couldn't agree more. My only wish is more people would use it.
Re:Rust in 2018: easier to use by eggy on Monday January 15, 2018 @12:59PM (#16152137)
My wish too! I have no issues with F# on Windows or Linux using .NET Core I use F# as my general high-level language and Zig as my C replacement/Rust alternative for low-level work. I can gradually re-write C stuff in Zig, and be productive.

  [1] - ziglang.org
Re:Rust in 2018: easier to use by marmaduke on Sunday January 14, 2018 @03:33PM (#16146212)
I wanted to get into f# but had a hard time with tooling, cross platform. For example, I'd see a great library and the instructions assume VS while I'm on Linux. There are a variety of build tools and package managers.

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.

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

[1] https://github.com/giraffe-fsharp/Giraffe

[2] http://dot.net/core

Re:Rust in 2018: easier to use by e12e on Sunday January 14, 2018 @06:11PM (#16147100)
> 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?

Re:Rust in 2018: easier to use by Nelkins on Sunday January 14, 2018 @08:49PM (#16147848)
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.
Re:Rust in 2018: easier to use by marmaduke on Monday January 15, 2018 @02:15AM (#16149082)
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.
Re:Rust in 2018: easier to use by trumpsamerica on Sunday January 14, 2018 @12:03PM (#16145010)
Do you have a good learning guide and a development guide (setting up ide, vim, tools etc)? I want to jump start into f#
Re:Rust in 2018: easier to use by Nelkins on Sunday January 14, 2018 @12:25PM (#16145142)
For learning the language, there is no better guide than F# for fun and profit. Start here[1], then maybe check out this series[2] and this one[3]. If you want to learn about monads and such, go through this series[4]. Look through this[5] page for other good stuff.

Unfortunately, the fsharp.org site is kind of out of date. I think that's mostly a function (heh) of the MS F# docs becoming much better (can be found here[6]). These instructions for getting a dev environment set up are pretty good[7]. If you hunt around, you can also find blog posts which may be a little more comprehensive[8][9][10].

[1] https://fsharpforfunandprofit.com/why-use-fsharp/

[2] https://fsharpforfunandprofit.com/series/designing-with-type...

[3] https://fsharpforfunandprofit.com/series/thinking-functional...

[4] https://fsharpforfunandprofit.com/series/map-and-bind-and-ap...

[5] https://fsharpforfunandprofit.com/site-contents/

[6] https://docs.microsoft.com/en-us/dotnet/fsharp/

[7] https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/

[8] https://atlemann.github.io/fsharp/2018/01/13/fsharp-on-ubunt...

[9] http://www.prigrammer.com/?p=363

[10] https://medium.com/@edgarsanchezg/four-easy-steps-for-instal...

Re:Rust in 2018: easier to use by Nelkins on Sunday January 14, 2018 @12:28PM (#16145156)
Also a weekly roundup of F# news can be found here[1].

[1] https://sergeytihon.com/tag/newsf-weekly/