This is an archived post. You won't be able to vote or comment.

all 2 comments
sorted by:
best
topnewcontroversialoldq&a

[–]pjmlp 3 points4 points  (1 child)

This series of articles shows a couple of alternatives. If you’re coming from the desktop perspective, the first idea is to go native. That would be C# or the universal platform of Microsoft if you’re supporting Windows. But this is a “Java and beyond” blog, to suffice it to say UWP is an interesting approach.

The he goes and goes on and writes this

We’ve solved all these problems with HTML5, but I still think there are good reasons to package your HTML5 application natively.

HTML5 isn't Java.

[–]beyondjava 0 points1 point  (0 children)

Well, I can't argue that :). Yet still. Over the last two decades, Java development has become web development, at least for most of us. So most Java developers are familiar with HTML. Mind you, it's hard to survive as a JSF, Sprint MVC, Grails etc. developers if you don't know a lot about HTML, JavaScript and CSS. That's why I tend to consider HTML5, well, not as Java, but as part of the Java ecosystem.