4 ms·

Personally glad to be free of all that goofiness, Angular, JS or what have you. http://websharper.com/ http://websharper.com/ Almost two years in production.

Personally glad to be free of all that goofiness, Angular, JS or what have you. http://websharper.com/ http://websharper.com/ Almost two years in production. I even had the opportunity to try the F# Type Provider for Sencha Architect and although I do not like tooling I came away shocked at how productive the experience could be for back-end application development using that tool.

ep103 12y ago
What's it do, just compiles to js for the front end?
- davidgrenier 12y ago
  Compiles your client-side F# code to JS such that you write all your code in the same programming language. You get to leverage the sophisticated type system of F# for your client side code and get transparent interop between front-end and back-end code. There's no need for http/ajax requests to your back-end code because the WebSharper compiler takes care of wiring function calls from the client side directly. [<RPC>] let getName() = "David" [<JavaScript>] module Client = let page() = Div [ Span [Text (getName())] ] Not only is all of this statically typed, WebSharper takes care of transparently wiring the call for you and serializes any data structure that you may want to pass from the server to the client and vice versa. WebSharper has no problem generating both server-side markup through server-side combinators but truly reigns as a SPA architecture as you can choose to simply return data from your RPC calls and generate the markup on the client-side. Another benefit here is that you generally avoid the need to rely on libraries like JQuery to query your DOM and interact with the markup. Being able to simply keep a reference to any DOM element you create as opposed to having to query your DOM to get is just simpler. But WebSharper also offer a host of well thought-out abstractions on top of Web Development in the form of Sitelets/Formlets/Piglets and now UI.Next. The real benefit of those is composability. If you are are already familiar with an ML-like language you will be pleased at the benefits you get. If you aren't, I strongly recommend you take a look at the landscape of programming languages as three great families stand out... you would do yourself a major favor as a developer to learn at least one ML. Those that do never go back.

ep103 12y ago

What's it do, just compiles to js for the front end?

davidgrenier 12y ago
Compiles your client-side F# code to JS such that you write all your code in the same programming language. You get to leverage the sophisticated type system of F# for your client side code and get transparent interop between front-end and back-end code. There's no need for http/ajax requests to your back-end code because the WebSharper compiler takes care of wiring function calls from the client side directly. [<RPC>] let getName() = "David" [<JavaScript>] module Client = let page() = Div [ Span [Text (getName())] ] Not only is all of this statically typed, WebSharper takes care of transparently wiring the call for you and serializes any data structure that you may want to pass from the server to the client and vice versa. WebSharper has no problem generating both server-side markup through server-side combinators but truly reigns as a SPA architecture as you can choose to simply return data from your RPC calls and generate the markup on the client-side. Another benefit here is that you generally avoid the need to rely on libraries like JQuery to query your DOM and interact with the markup. Being able to simply keep a reference to any DOM element you create as opposed to having to query your DOM to get is just simpler. But WebSharper also offer a host of well thought-out abstractions on top of Web Development in the form of Sitelets/Formlets/Piglets and now UI.Next. The real benefit of those is composability. If you are are already familiar with an ML-like language you will be pleased at the benefits you get. If you aren't, I strongly recommend you take a look at the landscape of programming languages as three great families stand out... you would do yourself a major favor as a developer to learn at least one ML. Those that do never go back.