#SOLVE ANY PROBLEM WITH INDIRECTION UPGRADE#

Even the LISPy projects behave more like “data as code” rather than “code as data”. We opened the box, and moved stuff from data (“dumb” HTML) to code (“smart” JS), and once we saw how much control code gave us, we were never going to go back to just writing data again.

I remember a (since deleted?) comment from Guillermo Rauch, observing that JS build tools (which do many jobs, as I’ve documented) are a Pandora’s Box - once opened, it cannot be closed. The lack of the Web Platform having approachable, friendly, non-judgemental-or-yelly-graybeard teachers/advocatesĪnalysing the causes of a problem (if this can be called a problem - it is in the small, but not in the large, and yet may be a problem in the very large - there is a more complex trinomial here than either side would have you believe) is a different matter than solving the problem.Employers severely overindexing on interviewing for JS skills over HTML, leading bootcamps/other professional prep institutions to respond in kind.

#SOLVE ANY PROBLEM WITH INDIRECTION UPGRADE#

The failure of Web Components to server-side-render and progressively upgrade compared to $FRAMEWORK.

The failure of HTML imports to offer sufficient componentization compared to $FRAMEWORK.

The perennial debate between gatekeeping vs emphasis on fundamentals aside, I was reflecting that the whole situation with vs The Web Platform™ arose out of multiple constraints:

My recent End of Localhost piece on Hacker News came with the usual dash of HN criticism devolving into blaming beginners for not knowing the same parts of the stack that they consider mandatory:

Solve any problem with indirection