21–30 of 74 posts
great! now we just need more than two people that know f#. i keed...kinda ;)
That would require Microsoft, the F# team, and the vocal F# community members to actually want F# to be a proper first-class .NET citizen, which sadly isn't the case. https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many...
> export { _ as $2665$ }; Why significance does that have in javascript? http://fable.io/repl/
let (heart) x y = x + " loves " + y
Earlier quoted context omitted.
That would require Microsoft, the F# team, and the vocal F# community members to actually want F# to be a proper first-class .NET citizen, which sadly isn't the case. https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many...
As a sometimes-user of F#, I’m quite happy not caring about a dead-end technology like UWP and .NET Native, thank you very much. I’m glad everyone else seems to agree about that, too.
https://np.reddit.com/r/csharp/comments/75mc1m/announcing_uw...
All this FUD and hostility from the F# community (including the Fable devs) towards UWP, or anything that's of interest to most Windows and C# developers making the switch, is why F# will never be popular.
And for most people who need to have their code running on anything else than Windows, F# and .NET wouldn't be their first choice anyway, given that there are plenty of better alternatives around, like Haskell, Scala, ReasonML, OCaml etc.
great! now we just need more than two people that know f#. i keed...kinda ;)
some people said in the Reason3 update article that F# is better suited for JS devs than OCaml.
The first thing I worry about reading something like this is how leaky the abstraction will be. I would love to ditch JavaScript for pretty much anything else but if I need to think about the JavaScript part anyway because of certain things that I can or cannot do I prefer to think in JavaScript from the get go.
Earlier quoted context omitted.
As a sometimes-user of F#, I’m quite happy not caring about a dead-end technology like UWP and .NET Native, thank you very much. I’m glad everyone else seems to agree about that, too.
UWP is the primary Windows client application platform going forward. https://np.reddit.com/r/csharp/comments/75mc1m/announcing_uw... All this FUD and hostility from the F# community (including the Fable devs) towards UWP, or anything that's of interest to most Windows and C# developers making the switch, is why F# will never be popular. And for most people who need to have their code running on anything else than Wi…
Earlier quoted context omitted.
UWP is the primary Windows client application platform going forward. https://np.reddit.com/r/csharp/comments/75mc1m/announcing_uw... All this FUD and hostility from the F# community (including the Fable devs) towards UWP, or anything that's of interest to most Windows and C# developers making the switch, is why F# will never be popular. And for most people who need to have their code running on anything else than Wi…
Replying to check back in one year. Good luck chasing Microsoft's moving cheese!
Earlier quoted context omitted.
Replying to check back in one year. Good luck chasing Microsoft's moving cheese!
Nothing is being moved. UWP has been here since the dawn of Windows 10, which evolved from WinRT, going back to Windows 8, and is constantly being extended with new APIs.
It's nice when you're where the cheese is currently at, that's not what I'm talking about though.
I do hope for your sake you don't wind up in the next lifeboat after the Silverlight crew, I really genuinely do. Good luck!
great! now we just need more than two people that know f#. i keed...kinda ;)
That would require Microsoft, the F# team, and the vocal F# community members to actually want F# to be a proper first-class .NET citizen, which sadly isn't the case. https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many...
And I can go pretty far - I have one working spouse, no major commitments, and have lived in one spot long enough I would prefer that my next role be elsewhere.
Admittedly, any other comparable (or even better?) language could lure me just as readily.
The first thing I worry about reading something like this is how leaky the abstraction will be. I would love to ditch JavaScript for pretty much anything else but if I need to think about the JavaScript part anyway because of certain things that I can or cannot do I prefer to think in JavaScript from the get go.
This is exactly why I standardised on TypeScript. Their isn't actually much of an abstraction in one direction, valid ES6 is valid TS and the types are inter-operable. Throw in better typing, proper classes, down compiling of async/await to ES3/ES5 (still magic to me) and the ability to progressively port from one to the other (and you can even get a lot of the TS benefits just by annotating your existing JS as a goo…
Coming from a C# and Python fan, TS hits the mark pretty solidly on all levels.