The project is really great, however license is really bad. A modern framework, should be open source under liberal license. Licenses like this worked in 90s, but currently they don't work.
How do you propose they make money to pay salaries?
WebSharper: Make web apps in F#
11–20 of 86 posts
Re: WebSharper: Make web apps in F#
#12The project is really great, however license is really bad. A modern framework, should be open source under liberal license. Licenses like this worked in 90s, but currently they don't work.
How do you propose they make money to pay salaries?
Paid support, tools, there're plenty of companies which follow this business model. Extjs, Vaadin, Typesafe, etc.
I understand that they want to make a money, however, using their license is unacceptable risk, especially taking into account there're comparable alternatives. I'd rather use GWT/TypeScript/Scala.js, than proprietary framework which I won't be able to work with if they changed license to something unacceptable (for example, charge per server or whatever).
Re: WebSharper: Make web apps in F#
#13This looks super interesting. I don't think I've ever seen anything like it. At first I thought it was similar to Classic ASP or JSPs, but after looking at some the examples, it's more like a JS framework in that it generates HTML dynamically with client side code. But, the thing that really looks cool to me is the interop between client and server that you can do. You can use the exact same "type Person = {Name:stri…
opa [http://opalang.org/] does something very similar too
Re: WebSharper: Make web apps in F#
#14It's well intentioned, but this project is destined to go nowhere fast.
Abstracting away web development and http has been tried again and again, and always ends up being more hassle than plain ol' HTML+JS+HTTP.
Then you've limited yourself to interop with the js libraries they've provided leaky wrappers over, or you can write your own leaky wrapper if you want to use coolnewthing.js you saw on github.
And to cap it all, this framework requires commercial licensing for closed source projects!
Re: WebSharper: Make web apps in F#
#15Is this an arms length Jetbrains thing? If not, it seems awfully odd that its name is so close to Resharper and the parent company is called IntelliFactory, which is so close to IntelliJ. I guess there's nothing wrong with that. Just odd.
Re: WebSharper: Make web apps in F#
#16Earlier quoted context omitted.
How do you propose they make money to pay salaries?
Paid support, tools, there're plenty of companies which follow this business model. Extjs, Vaadin, Typesafe, etc. I understand that they want to make a money, however, using their license is unacceptable risk, especially taking into account there're comparable alternatives. I'd rather use GWT/TypeScript/Scala.js, than proprietary framework which I won't be able to work with if they changed license to something unacce…
If you worry about such hypothetical licence or price changes, you could also contact the company and negotiate a custom licence/contract.
Re: WebSharper: Make web apps in F#
#17Does anybody know what's the 2 chrome extensions displayed in the screenshot?
Re: WebSharper: Make web apps in F#
#18Does anybody know what's the 2 chrome extensions displayed in the screenshot?
The first is "Google Hangouts" (https://chrome.google.com/webstore/detail/hangouts/nckgahada...), the second is "Awesome Screenshot" (https://chrome.google.com/webstore/detail/awesome-screenshot...).
Re: WebSharper: Make web apps in F#
#19Another monolithic framework that will likely catch some unsuspecting CTO or director and ultimately be his demise, or someone who doesn't want to learn javascript (such people still exist, sadly).
Re: WebSharper: Make web apps in F#
#20It's well intentioned, but this project is destined to go nowhere fast. Abstracting away web development and http has been tried again and again, and always ends up being more hassle than plain ol' HTML+JS+HTTP. Then you've limited yourself to interop with the js libraries they've provided leaky wrappers over, or you can write your own leaky wrapper if you want to use coolnewthing.js you saw on github. And to cap it…
I don't really think requiring commercial licensing for closed source projects is really a con. Seems like a logical way to make money, yet still allow open source projects to benefit.