News for hackers. Stuff that matters.
Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @01:44AM (#14926595)
XHTML hyper here.

Had the browsers properly adopted XHTML and the accompanying standards, and today we could already enjoy something like XAML on the browser instead of having only Chrome supporting WebComponents with workarounds like ShadowDOM to preserve local changes.

Re:Languages Which Almost Became CSS by icebraining on Friday August 04, 2017 @03:43AM (#14927053)
I also liked XHTML, but why do you see it as a transition path to something like XAML? Isn't it basically well-structured HTML?

I mean, I get that it's extensible thanks to XML, but that doesn't mean browsers would actually have an incentive to create and implement such extensions.

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @04:50AM (#14927276)
The XAML like parts were the set of XHTML components standards.

https://www.w3.org/standards/xml/components

Basically Events, Modularization, Fragments, XForms, XQuery and possibly other parts that were still being worked on when the HTML 5 hype started.

And were we are, yet to have a Web UI designer that can match Blend, Qt Creator, Netbeans Matisse, Scene Builder, Glade, Delphi, C++ Builder,....

When I do web development I always feel like I am stuck with something not better than Notepad for GUI programming.

Re:Languages Which Almost Became CSS by tannhaeuser on Friday August 04, 2017 @08:07AM (#14928052)
Ok I have to disagree here. I believe the failure of XHTML was to cram everything into XML; I found XForms especially pointless. Now don't get me wrong, and as you know from my other posts here I'm as much of a markup geek as can be, but IMO markup is first and foremost for representing and authoring text. Just that browser content is mostly text, however, doesn't mean everything has to be markup. To the contrary, I believe XHTML (and XML in mainstream apps) fell out of favor because the spec authors tried to anchor each and everything on XML, rather than on something that makes sense for the task at hand (a phenomenon not unheard of for JSON and YAML as well). In XForms, for example, XML was used as a programming language which just never made sense. You know you're doing it wrong IMHO when you have to discuss whether you want to store your data in attributes or element content, a distinction that only makes sense for text data.

It's sad and surprising how much time and energy was wasted on XHTML. Back in february I met Steven Pemberton (XHTML spec lead back then, and of ABC/Python fame). He's just such an inspiring guy to talk to, but unfortunately, there was no time for recapitulating the XHTML situation.

Re:Languages Which Almost Became CSS by allover on Friday August 04, 2017 @05:21AM (#14927379)
> And were we are, yet to have a Web UI designer that can match Blend, Qt Creator, Netbeans Matisse, Scene Builder, Glade, Delphi, C++ Builder,....

Huh, my experience was all those things are terrible (spent some time with Qt and researching Glade, also inherited a Delphi codebase full of spaghetti code at one point).

Visual UI tools are great for prototyping, awful for maintainable code. Anyone I know who's spent any time with them ends up wanting to go back to the code.

There certainly are good Web UI designers [1], it just seems no-one wants them. There are successful visual Web UI prototyping tools tho.

[1] http://macaw.co/

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @05:35AM (#14927418)
Those tools are wonderful and make my life on native frontend projects enjoyable, versus the pain having to deal with of Web design, which I happen to have experience since the early days (first coded web apps were C based cgis in 1997).

Trying to manually hack GUI generated code is an anti-pattern.

One has to leave the code generated by the tools to the tools, everything else should live in other code files.

Sadly I never heard of Macaw, specially on the enterprise circles I move on, in any case they seem to be gone now.

Re:Languages Which Almost Became CSS by tannhaeuser on Friday August 04, 2017 @04:46AM (#14927266)
You don't need XML for that. HTML can be parsed using SGML precisely and elegantly [1] (if I may say so for a project of mine).

If you see value in XML, you really should look into XML's big sister SGML. It gives you downward compat with XML, tag inference, type-aware (injection-free) variable and macro expansion, custom Wiki syntaxes (markdown and others), an integrated stylesheet language without new ad-hoc syntax, full HTML 5 parsing with short forms for attributes etc., and more. You might actually like it.

[1]: http://sgmljs.net/blog/blog1701.html

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @04:57AM (#14927303)
I was a big fan of Docbook, back when SGML was more well known, thanks for the heads up.

However this is meaningless if the browsers keep being a document engine, full of workarounds to translate a mix of document tags, coupled with some generic <div> and <span> into some kind of general purpose GUI layout engine.

Having to find the proper incantation of CSS3 transforms to portably trigger GUI acceleration is a good example of such hacks.

Even if it is yet another hack, webcomponents + shadowdom looked it would be the solution, even if a bit hackish, but it is Chrome only.