> Sounds to me like a FAR nicer environment for > programming a GUI than swing, though not quite as nice as JavaFX.
Really? I mean web UI's are fine and dandy for what they are, but what they aren't are easy to develop rich desktop applications. You can create a stupidly beautiful HTML5 UI that looks amazing, but how many people can write at that level, and how many of them are there? If you just want forms and images, fine, but when you want real desktop integration and feel a web page is not the way. Lets not even talk about the painful performance penalty of using interpreted Chrome/HTML/JavaScript/Java vs. Swing/Java I see this is clearly a technique for the Java UI ignorant who have no idea or interest in learning Swing. If you're lazy to learn something new or you want to write HTML/CSS/JavaScript/bindings without learning a better way of doing it, by all means write this blasphemy. The sad thing is that Swing really isn't that bad when you get used to it. Yes its verbose, and you always need to learn grid bag and its 600 properties, but once you're off the training wheels, programming for it becomes very straight-forward. This just reminds me of the bug tracking 'web' app that one of my companies used. It was a giant set of ActiveX components that filled an IE window completely, and you couldn't use any of the browsers buttons, because what they were really doing was just wrapping their paradigm of development (Rich windows client development) and shoe- horned it into a 'web application'. If that wasn't bazaar enough for you, there was an installation for a rich application who's sole purpose was to display a window with the web page (hosting the ActiveX apps) within an MSHTML container... very depressing. > Close though. If you are assured you can use all the latest and > greatest HTML features because of a guaranteed updated webkit running > your webapp, programming in vanilla HTML+CSS+JavaScript is great. For > macs it could include a JVM :0 Macs still couldn't release through the app store since they aren't allowed to self-update outside of the store itself (both in Webkit & in JVM unless you're using dynamic library linking maybe). you will also run into the problem of major/minor releases breaking some stupid little thing in your code that makes your application a steaming pile of useless. JNLP (love it or hate it) gives you the ability (as a dev) of choosing the specific JVM you want to use. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
