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 :)
There's a response to your question from one of the SAFE stack developers, but it is dead so only those with "show dead" on see it. I'm not sure if dead comments show up for people without "show dead" on if they follow a direct link to it, but if they do, here is a link [1].
I'm curious why it is dead. The account has only posted two comments, both technical comments on F# threads, and both are dead. It has no submissions. So how did it get killed?
Accounts without much history are subject to additional software filters, mainly because of past abuse by trolls. We've marked isaacabraham79's account legit so it won't happen again.
If you see a [dead] comment that shouldn't be dead, please vouch for it instead of posting offtopically about its deadness. Usually that will just fix the problem. That's why we implemented vouching!
To vouch for a dead comment, click on its timestamp to go to its page, then click 'vouch' at the top.
Yeah, when I saw it had become visible I was curious if my vouch made a difference, and so un-vouched to see if it would disappear again. If it had, I would have re-vouched.
Not sure exactly how HN works, but I'm guessing this happened due to high number of downvotes. I just upvoted him and the comment is not dead anymore, though.
I haven't, I'm curious to know whether it has transparent, type-checked, client-server RPC calls like WebSharper? Hands down must-have from my perspective.
As for declarative UI development I had worked with Formlets -> Piglets -> UI.Next and felt they had nailed it at the end. I haven't worked with Elm, my hopes are high. The only other thing I know likely has a good model would be: https://github.com/calmm-js
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 :)