Technology Choices for My SaaS in Retrospect

Re:Technology Choices for My SaaS in Retrospect by JaggerJo on Saturday September 24, 2022 @04:51AM (#32960849)

Actually - you have a bunch of options for building web front ends in F#

- via Fable (F# to JS Compiler)

- WebSharper (tightly integrated web frontend and backend)

- Blazor/Bolero Server Side (like phoenix live view)

- Blazor/Bolero WASM

We also start to see Avalonia running on WASM, but I wouldn’t say it’s ready yet.

[ Parent | on HN ]

Re:Technology Choices for My SaaS in Retrospect by ramraj07 on Saturday September 24, 2022 @05:07AM (#32960920)

When I googled how to create wasm apps, I got blazor. I come from a python background, so this is tempting to try our blazor for an interactive app, is it recommended? ( you don’t hear much about Microsoft tech here only Js or python)..

[ Parent | on HN ]

Re:Technology Choices for My SaaS in Retrospect by CharlieDigital on Saturday September 24, 2022 @08:51AM (#32962071)

As a long time Microsoft stack dev, I don't recommend Blazor for first time devs on dotnet.

There are a LOT of friction points that are just really difficult for new devs to work out.

dotnet is really, really good at building scalable, fast, secure web APIs but it is mediocre for building web UIs

[ Parent | on HN ]

Re:Technology Choices for My SaaS in Retrospect by JaggerJo on Saturday September 24, 2022 @05:53AM (#32961110)

haven’t used it for any big apps. We use Fable + React

[ Parent | on HN ]