Comment Re:Why not html forms? (Score 1) 216
1. It's W3C not WC3.
2. Why should a non-geek care about W3C standards? They can still code in any broken HTML they feel like if the browser displays it properly. The only reason they'd care is if they're trying to pass it off as professional or paid work. In which case they should work to the quality their client requires or stop lying about their skills
All UI programming is complicated and tricky, this is well known. As languages become more and more abstracted from the nitty-gritty details of interacting with the OS, they become more and more focused on abstract concepts such as objects and their interactions. HTML defines objects (nodes, their attributes, types), CSS and JS define how they interact. If you are so narrow-minded in regards to the tools you use to define or implement your solution then I'm afraid you don't have a very bright future in this field.
Try your hand at some real UI programming for local applications for a while and you'll realise that HTML/CSS/JS is really the UI toolkit you wish you always had. See how long it takes you to write a UI engine to achieve custom behaviour it would have taken an hour or two to achieve using HTML/CSS/JS.