10 comments

[ 2.5 ms ] story [ 30.9 ms ] thread
I was excited about this until I saw it's from jet.com. Heard too many things about bad dev practices there to believe a conference presentation about it.

It's unfortunate there aren't more F# jobs. I've always worked exclusively with Linux, but would switch to MS and all associated headaches in a second if I could write functional code with F#.

> I've always worked exclusively with Linux, but would switch to MS and all associated headaches in a second if I could write functional code with F#.

That seems... odd. Surely you can write functional code in a different language on Linux? Or write F# on Mono?

Soon .net core, they're making good progress on the CoreCLR support.
Sorry if I wasn't clear ... I do write Haskell on Linux.

I meant that F# would be enough to entice me away from Linux and overcome my activation barrier against using Windows. As long as it wasn't glorified C# with a thin functional wrapper, and it was a focus on real functional techniques, it would be highly interesting for me.

I do not have much of any F# experience but I write C# in my day job. I've heard nothing but good things about F#, including from people similar to you with a functional background incl. Haskell.
It is one presentation from jet.com employee (who is cool in my opinion). There are multiple presentations from different organizations/people.

Also F# on Linux works like charm on Mono and CoreCLR support is around the corner.

There are a lot of cool engineers with cool presentations. You can't watch them all, and filtering by properties of the company backing the work can sometimes be a useful way to find only the things more relevant for you.

> Also F# on Linux works like charm

Yes, my only current knowledge of F# comes from working through tutorials on my Ubuntu laptop.

My comment was meant to suggest that F# makes it worthwhile to endure the pains of working in a Windows environment. I love Python, for instance, but would not consider a job coding Python from Windows. For F#, I would consider it.

What sort of bad dev practices have you heard about?
Every C# shop right now is a potential F# shop in the future.

They only need to see why, in many cases, C# is totally wrong for the problems they are trying to solve :)

It's unfortunate there aren't more F# jobs.

I've found that several C# shops are open to using F# where it makes sense. If you see an interesting job opening and they mention C# it's definitely worth asking about F#.