isaacabraham79

What are you thinking of when you say "something goes wrong"?

Because JS is pervasive.

Since the F# transpiles into JS at runtime it's really no different than, say, TS in terms of performance concerns.

Unless you meant something else there?

The Director of the Foundation is a Microsoft employee and they are the creators of the Foundation.

In addition to the obvious issues, this is also about Microsoft and their relationship with the Foundation.

No. In languages like F#, you can encode in the type system that the result can be either a customer or an error. And the compiler won't let you "access" the customer until you've safely checked that the result is, indeed, the customer rather than an error.

In this way you end up encoding more intent within your types and behaviours rather than implicitly letting the consumer figure it out themselves.

'0' is a string (or char), not a number. Just saying.

Yep, this is definitely something that should be made easier and there's an RFC to address it.

There are also some libraries out there that make this easier.

I'd say it's an annoyance and should be improved, but it's nowhere near a blocker for us.

Try here https://dotnet.microsoft.com/download. We also put some beginner videos on our you tube channel here https://m.youtube.com/compositionalit.

Thank you :-)

Disclaimer: I'm one of the maintainers of the SAFE stack.

The SAFE Stack is slightly different in that in itself it's not a technology as such, aside from the .NET template that we a lot of invest time into. Instead, it brings together several distinct technologies that when pieced together form an excellent end-to-end stack.

I would say that SAFE seems to currently have a larger community movement around it (as well as a commercial support aspect for those people that want / need that).

SAFE Stack doesn't support WASM though - the client side story is instead built on top of the excellent Fable (an F#-to-Babel-to-Javascript transpiler). In this regard I think SAFE is also slightly different to WebSharper in that (from when I last tried WS out at least) WS is more of a complete framework whereas SAFE contains a number of libraries and components that you can opt in / out of as you see fit and lives a bit closer on the JS ecosystem side (again, happy to be corrected here on the WS side).

Both Websharper and SAFE stack are excellent stacks, and both encourage the use of F# end-to-end - try them both out and see what fits better for you :)

Typescript has grown into way more than just "JavaScript with some type annotations". It's a much bigger superset with lots of language features that JS doesn't have.