How To Create Full Stack Web Applications In F# | SAFE Stack Overview 

This is a high level introduction and I don't go into much depth for now on how to get started. I am only presenting the technology options to write web applications. In subsequent videos, we will actually write a full-stack application. More on that in the next video. Also, this is not an exhaustive list of options. For example, I am looking at other libraries like Sutil for the front-end that look really cool. Hopefully you've enjoyed and stay tuned for more!

This series is gonna be great! Super excited dude :D

Thanks for taking the time to clear up so much confusion.

I am waiting eagerly for this tutorial

This channel is the best content I have watched all year! Keep up the great work. Do you have any plans to make a video on Elmish or Feliz? Sutil is cool but seems pretty raw as of now.

Lovely intro, thanks!

Appreciate the F# videos.

Really impressed with the channel content and has definitely inspired me to try out Giraffe (or at least a simple HttpListener within F# at least!)

Hi Ben! Enjoying the videos, let me to be a bit pedantic about ASP.NET Core: It's more a framework than a library, and it's not counter-idiomatic to F#, it just can use some sugar and love like MVC on top of ASP.NET Core for OOP, that's what Giraffe and other stuff is.

I had some experience with SAFE in the past weeks and I find it amazing! The only problem is that the docs from SAFE and SATURN assumes that the user have a lot of knowledge in FP and in .NET...

Awesome video! And Feliz is also Happy in portuguese :)

11:15 "greatness" 😹

We're starting to introduce F# as our primary language for the company I work. Things we constantly find ourselves lost in are database migrations and authentication. (We found multiple aways to do it). Do you plan on tackling any of those subjects later? btw, awesome content man!

"Normal Windows server"... I don't know anybody who uses a Windows server. I've seen some MSSQL instances (I suppose these are on Windows), but that's usually in a financial or lawyer's office when they are using some older tech that needs to connect their proprietary software with their print network. Maybe in government?

Thank you very much for taking the time to make this videos, it's truly helping me to refactor a messy nodejs app. About that, do you think it's a valid approach to progressively replace a Nodejs app with Fable code? The goal is to eventually move to full f# with dotnet.

I am a JS developer and reently heard of F#. Is there any resources that i can learn about F# and use it in my projects that uses JavaScript without depending on dot-net ?

Hello Ben, I have started learning SAFE Stack. I have experience with JS and React, Redux, and also with Elm, and I have a question. In SAFE Stack, is it possible to use MDU (Elmish) together with React (Fable.React)? MDU is architectural pattern from Elm, which have gained popularity in JS world with React and Redux. React is basically responsible for View, and Redux is responsible for Model and Updater. So React is responsible for rendering HTML, and Redux is responsible for state management. React has some build-in features of basic state management and can be used without Redux or together with other state management library like MobX. So, from your description, I guess that Elmish implements MDU but has it's own engine responsible for rendering actual HTML (like Elm), but I would like to use Elmish MDU with React and React.DOM because I have experience with it and its really powerful, and as you said - easier to sell. As a side note - I'm eager to learn SAFE stack and learn how it can solve certain problems. I think Redux is a great library and did a good job in promoting FP in JS world, but it has some limitations, i.e. error handling, reducers (updaters) cannot be monadic functions so there is not straight way to propagate errors and failures to Middleware. Besides JS and Typescript do not encourage FP practices, so there are a situation when Redux is not used as intended, i.e. tendency to have anemic reducers or hiding side effects outside middlewares.