Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fable: F# to JavaScript compiler

fable.io

Post reply on HN
Print view View original

71–74 of 74 posts

Re: Fable: F# to JavaScript compiler

#71

Post by MangelMaxime »

dep_b wrote: post #62
BigJono wrote: post #38

Earlier quoted context omitted.

> Plus, being a superset means that if you want to 'drop into' JS to take advantage of some quirk or whatever at any time, you can just disable your linter and do the deed. This is an exact example of what GP was talking about with leaky abstractions though. You don't have to just learn TS to use TS, you need to learn TS and JS. IMO a proper, strict typed language; and plain Javascript; are both much better options t…

Well I'm perfectly fine with something what languages like C++ or Objective-C are to C since the whole C interface is still available. If I have a problem in the C layer I can touch that directly and fix it. But I don't think it's possible to mix F# and JS code in the same code file without doing really ugly stuff.

In fact, Fable interop is a really powerful one.

If you want to make your own opinion, we have a really good guide here: https://medium.com/@zaid.naom/f-interop-with-javascript-in-f...

Re: Fable: F# to JavaScript compiler

#72

Post by TensorMetric »

enricosada wrote: post #69
pjmlp wrote: post #63

Earlier quoted context omitted.

Because Microsoft is the one paying the salaries of F# developer team. The F# comunity has become quite strange, always bashing the products of the company that actually develops their programming language. Not a good way to keep them motivated into supporting F#.

There are lot of scenario where F# can be used. In some scenario support is more stable, other experimental, other are not supported. like every technology. Because budget is not infinite, you need to prioritize. Just to show you things happened MS tech related to F# and .NET in the last two years: - .net core - .net standard (is not the same as .net core) - new project system for VS - new .net sdk (that mean work to…

To me and many early investors of F# (loyal Windows developers), the current direction is the worst thing that happened to the language.

UWP is not just a nice to have, it's the backbone of client Windows development right now and going forward.

I used to be a huge F# advocate and all the people I converted to F# over the years have left, due to the lacking Windows support. And the VF# program manager siding with anti-UWP, anti-Windows, anti-MS detractors isn't helping the situation.

Re: Fable: F# to JavaScript compiler

#73

Post by pjmlp »

enricosada wrote: post #69
pjmlp wrote: post #63

Earlier quoted context omitted.

Because Microsoft is the one paying the salaries of F# developer team. The F# comunity has become quite strange, always bashing the products of the company that actually develops their programming language. Not a good way to keep them motivated into supporting F#.

There are lot of scenario where F# can be used. In some scenario support is more stable, other experimental, other are not supported. like every technology. Because budget is not infinite, you need to prioritize. Just to show you things happened MS tech related to F# and .NET in the last two years: - .net core - .net standard (is not the same as .net core) - new project system for VS - new .net sdk (that mean work to…

We don't do Azure and .NET Core is meaningless for us, as it doesn't have GUI support and EF Core is a tiny subset of EF 6.

As consulting company we are not bound to a single language or platform. When we do UNIX projects we use programming languages that are better fit for such platforms, and that isn't .NET Core.

For us .NET only matters for Windows related development, and there F# keeps being the black swan since its early days.

No tooling support for Windows Forms, XAML, Blend, ASP.NET, EF, WCF and now not even .NET Native, because for some strange political reason F# is separated from the .NET development group, and never considered on the decisions of the .NET platform as such.

With C# and VB.NET our customers on Microsoft solutions can be 100% sure their code is safe regardless of what Microsoft thinks to do next, at maximum they would need to re-write parts of it.

Re: Fable: F# to JavaScript compiler

#74

Post by igouy »

tpetricek wrote: post #15
igouy wrote: post #12

also FunScript "F# to JavaScript with type providers" http://funscript.info/

Fable pretty much replaced FunScript - all the activity around F# to JavaScript translation moved from FunScript to Fable nowadays!

What's the licensing?

"you only pay for what you get"

Post reply on HN