News for hackers. Stuff that matters.
Re:The baseline for web development in 2022 by rimliu on Friday January 28, 2022 @04:55AM (#30112660)
There is nothing easy about XHTML. Or rather it is only easy if you ignore the essential parts of it.
Re:The baseline for web development in 2022 by smorgusofborg on Friday January 28, 2022 @05:48AM (#30113028)
The sell of the time to jQuery webmasters was:

XHTML's complexity is too much to deal with and the WHATWG is going to keep all this unnecessary stuff out so you won't lose control to generalized tools like an IDE and systems that favors formally educated language/tool writers, i.e. schema validators and, as we see now, transpilers.

The end result is still everyone using an IDE perhaps due to more irregular features after WHATWG encouraging a framework, but at any rate demonstrating XHTML was not the real source of webmaster stress and future angst.

So now you have more complexity, a still pointlessly irregular format that needs to identify it's magical elements, and, (to get back on topic,) features that must be implemented first in 2 browsers to become standard.

All of this is brought to you by employees of Apple and the other vendors. If WebKit isn't one of the 2 implementations most people choose to work with when pushing a standard then Safari is the dead implementation due to a constellation of choices all made with Apple's support and approval.

Re:The baseline for web development in 2022 by pjmlp on Friday January 28, 2022 @05:02AM (#30112709)
Only if one insists in writing it using vi.
Re:The baseline for web development in 2022 by jacquesm on Friday January 28, 2022 @01:07PM (#30118250)
Let's not go there.
Re:The baseline for web development in 2022 by pjmlp on Saturday January 29, 2022 @02:57AM (#30124627)
Show us a vi plugin that can do as well as IDEs and UI designers for edit XML, including validation and XSLT debugging.

I wasn't going there, but then with such an interesting reply I might.