Another way to look at is is, if web apps were so great, why are phone apps so dominant? In the early days of the iPhone, their stock answer was “write web apps”. That failed miserably, and they eventually caved in and allowed developers to write real apps. JavaFX would be faster than WebGL if it got some developer energy pumped into it. O is so fucking brain dead...
> On Mar 14, 2018, at 10:35 AM, cowwoc <cow...@bbs.darktech.org> wrote: > > I agree. If the web was such a great platform for desktop apps, you would > have seen many other projects/companies porting complex desktop applications > to it. They are not. > > Web technologies are great for basic interfaces. They are utter garbage for > Filty Rich Clients. > > Don't repeat the mistake of ORMs: jumping on a technology because it looks > great from far, only to discover that it doesn't do what you want when you're > "95% done". > > Gili > > On 2018-03-14 6:58 AM, Peter Steele wrote: >> One of the biggest limitations is the fact everything is single threaded. >> This isn't related to vaadin and gwt. >> >> I have used vaadin and like it alot, and to build certain types of >> applications it is a great candidate if you are used to java. I have also >> used GWT alot and have extended it for areas which it doesn't cover. >> (Vaadin uses GWT too) >> >> Another js pet hate for me is the fact it is not OO based, people have >> tried to put wrappers around us but they inevitably have issues because >> they are wrappers. >> >> Chrome has a good debugger but compared to debugging support from desktop >> languages it is inferior >> >> The language is too visual basic like for my taste, it's nice and easy to >> use but if you want to do anything complicated you are in trouble. Thumbs >> up for closure support, thumbs down for the complete over use of closures. >> >> Btw these are only my opinions, you may disagree with everything i say and >> that is ok. I am in the camp of "i will never use a web based ide" but i >> have no issues building apps that are designed for the web and work well on >> the web (like for thin clients). Forcing everything in to the browser is >> not they way forward. >> >> >> On 14 Mar 2018 10:26, "Christian Lenz" <christian.l...@gmx.net> wrote: >> >> Peter, >> >> can you tell me which limitations you mean? As I wrote in an other thread, >> the limitations came from GWT. The Problem is that a Java developer doesn’t >> want to write HTML, CSS and JS so they are looking for an alternative. GWT >> or Vaadin or kotlin to js, I can’t understand that, but ok. So please don’t >> compare GWT or Vaadin with native JS. >> >> >> Cheers >> >> Chris >> >> Von: Peter Steele >> Gesendet: Montag, 12. März 2018 17:50 >> An: dev@netbeans.incubator.apache.org >> Betreff: Re: AW: Apache HTML/Java UI instead of ... Oracle will remove >> JavaFXfromOracle JDK >> >> Christian >> >> I am sure electron is good, but my personal preference is to not use a web >> ide. Javascript as a language has a lot of limitations. I have written gwt >> code to export java to html and you are limited a lot in how you design >> your apps. >> >> On 12 Mar 2018 16:40, "Christian Lenz" <christian.l...@gmx.net> wrote: >> >>> Have a look into electron apps. A lot of apps are written with this >>> Framework like VS Code and I think this is a big Player and you can see, >>> that it performs very well and it is performant as hell. Only to say one >> of >>> those apps. >>> >>> >>> Cheers >>> >>> Chris >>> Von: Peter Steele >>> Gesendet: Montag, 12. März 2018 17:37 >>> An: dev@netbeans.incubator.apache.org >>> Betreff: Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX >>> fromOracle JDK >>> >>> What about the eclipse RCP framework which uses swt? This would seem to be >>> a much better solution than having a html front end. >>> >>> On 12 Mar 2018 16:25, "Neil C Smith" <neilcsm...@apache.org> wrote: >>> >>>> On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com> >>>> wrote: >>>> >>>>> Forget about AWT, Swing and JavaFX - the future is HTML. In case you >>>> still >>>>> care about Java, then your future should be Apache HTML/Java API! >>>>> >>>> Generally inclined to agree with you - definitely on forgetting JavaFX, >>> and >>>> probably on forgetting AWT/Swing (intrigued to see what actually happens >>>> there). I don't think HTML is the only game in town, but for a lot of >>>> things it's probably the right way forward. >>>> >>>> But, if we start turning to Apache HTML/Java way, what does it run in? >>>> >>>> Out of interest, I was looking at an example project using Vaadin >> running >>>> inside Electron recently. Have you tried this approach with HTML/Java? >>>> >>>> Best wishes, >>>> >>>> Neil >>>> -- >>>> Neil C Smith >>>> Artist & Technologist >>>> www.neilcsmith.net >>>> >>>> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >>>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
