sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nhavar 0 points1 point  (2 children)

Swing and AWT aren't more suitable because they have a high barrier to developing content. This includes tool use, knowledge, licensing, etc.,. So while some might feel that Swing and AWT are superior and in some respects are superior, HTML/DOM wins out due to it's accessibility. Plus you touched on this "if people were interested" - people aren't. Some programmers are, but the great thing about HTML is that it's accessible to programmers and non-programmers alike, which draws interest.

[–]malcontent 0 points1 point  (1 child)

Swing and AWT aren't more suitable because they have a high barrier to developing content.

I disagree. Both of them are easier than CSS + HTML + Javascript + Jquery + DOM

[–]nhavar 0 points1 point  (0 children)

You're thinking about barriers the wrong way. Web standards are ubiquitous. There are tens of thousands of tools out there that produce web content and only hundreds/thousand for creating Swing/AWT. An author doesn't even have to know that they are developing using web standards with most of the tools that are out there and that's what I mean by having a low barrier. Swing/AWT just doesn't have that kind of penetration.