I see some F# praising in here. any good learning resources one can recommend to me (Ik I can "google it" or whatever. I mean something you had experience with and would recommend)
Fable 3: F# to JavaScript compiler
101–110 of 131 posts
Re: Fable 3: F# to JavaScript compiler
#102here's a 3d bin packer written in Fable:
http://bindrake.com/
and source:
https://github.com/OnurGumus/BinDrake
Re: Fable 3: F# to JavaScript compiler
#103Does anybody here use F# in a Linux shop? I'm generally keen on the more functional languages, but have tended to avoid F# under the assumption that if I use F# I'll probably also end up needing to use Windows to get the most out of it (or get a job using it).
Re: Fable 3: F# to JavaScript compiler
#104Earlier quoted context omitted.
From my experience it’s still not easy to find an F# Job. It’s a niche, but it exists and is growing. If you want one and are willing to take a few compromises you’ll find one.
I see a decent number of openings in the City of London quite regularly for finance and insurance positions. Also OCaml and sometimes Haskell. Even Rust has started popping up recently. I find this a bit intriguing because the library support for linear algebra, probability and statistics is pretty slim both in .NET and OCaml. The latter has OWL, which is very cool, but it's mostly a 1-person project. Do they develop…
Interesting in the ML space is https://diffsharp.github.io/ which is heavily developed by Don Syme at the moment.
Re: Fable 3: F# to JavaScript compiler
#105Does anybody here use F# in a Linux shop? I'm generally keen on the more functional languages, but have tended to avoid F# under the assumption that if I use F# I'll probably also end up needing to use Windows to get the most out of it (or get a job using it).
I used it years ago in a Linux shop using Mono. It was perfectly fine. I gather these days with the new .NET Core running natively on Linux it's even better.
Re: Fable 3: F# to JavaScript compiler
#106Earlier quoted context omitted.
Workarounds are not official support and won't fly for many customers deciding what to place in production when picking technology stacks, so the choice ends up being C#, VB, C++, Rust, JavaScript and Python. The official set of programming languages getting UWP support as part of Project Reunion.
WinUI / Project Reunion is just a continuation of the UAP (Universal App Platform) libraries. The support for C# works for F# - just like basically any other C# library can be used from F#. I figure the reason they don't mention F# is because it is obvious and/or implied but perhaps at the same time don't want to infer there is some kind of F#/FP-style syntax. I wouldn't confuse Project Reunion and the arbitrary Wind…
Good luck with that reasoning when Windows 10X comes out next year.
UWP is still the future of Windows API, Reunion is only lifting it from the Windows kernel, and exposing the respective COM infrastructure on the Win32 side as well.
When I create applications for customers I don't select technologies that require me to place workarounds that might make them repent for having me there in first place.
Hence why as much as I like F#, it is never going to be an option for me, until it has a seat at the table of the official languages.
Apparently that isn't an issue in your case, so good luck with the endeavours.
Re: Fable 3: F# to JavaScript compiler
#107Earlier quoted context omitted.
WinUI / Project Reunion is just a continuation of the UAP (Universal App Platform) libraries. The support for C# works for F# - just like basically any other C# library can be used from F#. I figure the reason they don't mention F# is because it is obvious and/or implied but perhaps at the same time don't want to infer there is some kind of F#/FP-style syntax. I wouldn't confuse Project Reunion and the arbitrary Wind…
Good luck with that reasoning when Windows 10X comes out next year. UWP is still the future of Windows API, Reunion is only lifting it from the Windows kernel, and exposing the respective COM infrastructure on the Win32 side as well. When I create applications for customers I don't select technologies that require me to place workarounds that might make them repent for having me there in first place. Hence why as muc…
There is nothing concerning Windows 10X that undermines anything I have said.
UWP is the future of Windows - correct.
I'm not sure any significant part of UWP has ever been in the kernel per se.
It sounds like you're a consultant where taking risks on behalf of your customers, no matter how small or logical the risk, is obviously not part of your job description.
Your offerings of good luck appear to be disingenuous.
Re: Fable 3: F# to JavaScript compiler
#108Earlier quoted context omitted.
I think you are missing the biggest advantage of F#: computation expressions. Computation expressions are like do-notation and list comprehensions in one feature. Now that I have tried them, I don't want to go back to a language without!
Interesting. But is it true that that is nothing like that in other languages?
They are a bit like do-notation in Haskell, but with a few extra things. They are also like a more restricted / opinionated version of Clojure macros.
What's really cool is that things like ```async function *``` from JS can be implemented as libraries in F#.
Re: Fable 3: F# to JavaScript compiler
#109Earlier quoted context omitted.
Good luck with that reasoning when Windows 10X comes out next year. UWP is still the future of Windows API, Reunion is only lifting it from the Windows kernel, and exposing the respective COM infrastructure on the Win32 side as well. When I create applications for customers I don't select technologies that require me to place workarounds that might make them repent for having me there in first place. Hence why as muc…
There is nothing concerning Windows 10X that undermines anything I have said. UWP is the future of Windows - correct. I'm not sure any significant part of UWP has ever been in the kernel per se. It sounds like you're a consultant where taking risks on behalf of your customers, no matter how small or logical the risk, is obviously not part of your job description. Your offerings of good luck appear to be disingenuous.
Picking F# over official supported languages has zero value on the sales of customers, that is what they care about, not cool software stacks.
So if their IT goes down and the reason is that a risky loving consultant used unofficial workarounds, I rather not get unnecessary phone calls.
As for the wishing luck, I was being honest, take it as you wish.
Re: Fable 3: F# to JavaScript compiler
#110Earlier quoted context omitted.
Good luck with that reasoning when Windows 10X comes out next year. UWP is still the future of Windows API, Reunion is only lifting it from the Windows kernel, and exposing the respective COM infrastructure on the Win32 side as well. When I create applications for customers I don't select technologies that require me to place workarounds that might make them repent for having me there in first place. Hence why as muc…
There is nothing concerning Windows 10X that undermines anything I have said. UWP is the future of Windows - correct. I'm not sure any significant part of UWP has ever been in the kernel per se. It sounds like you're a consultant where taking risks on behalf of your customers, no matter how small or logical the risk, is obviously not part of your job description. Your offerings of good luck appear to be disingenuous.
We've been running F# in production since 2014 - almost 7 years. It is quite shocking to hear anyone imply that F# is not ready for production use - that it is just "cool" tech. (when has F# ever been cool in the minds of the masses?)
I suspect you'll say "7 years is nothing" and maybe it is nothing. But it is still something. It is long enough that we made a couple bad framework/library dependency choices early on and to have learnt lessons from such mistakes.
By far the biggest technical challenge we've faced in that time is the .NET 5 migration - but even that might turn out to be a lot easier than I currently envisage.