Skip to main content

The Uselessness of HTML Imports

It is the opinion of this developer that HTML Imports, championed by the Polymer Project and already implemented in the Blink fork of WebKit, are utterly and completely useless.
Beyond this base uselessness, I believe HTML Imports are actively and wildly harmful. I believe the more they are used, the more problems they’re going to cause.

The Case For HTML Imports

Giving the new feature their fair shot, I’ll lay out the case in favor of HTML Imports. I was actually pretty excited about them when I first read the details, and even when I first started using them.
Unique loading of resources without double loading, such as when two imports each themselves import a shared dependency. is really cool! We’re building pretty complicated JS loading systems to solve what, here, is a built-in feature.
The collection of scripts, markup, and styles associated with single units of behavior is really great as a way to conceptualize of how you’re pulling in these web components. It just makes sense to pull in the idea of “Tabbed Pane” and get with it the mark up, behaviors, and default styling for panes of content with tabs to switch between them. No more making sure you have the right scrpt and link tags to match on top of making sure all the places you use the related mark up are correct.

The Case For Not Caring About HTML Imports

You’re already loading Javascript and CSS just fine. Honestly, is it that difficult to include a script and link tag pair? Sure I complained about it above, but let’s be honest, these are small things to complain about.
You already have template loaders if you’re doing any kind of client-side rendering, so HTML imports seem to solve a problem you already have solved. The catch being, they don’t actually solve them because HTML Imports load the documents without actually doing anything with them.

The Case Actively Against HTML Imports

Combining HTML, CSS, and JS into single files isn’t fun to edit or syntax highlight. If you don’t want to hate your editor, your HTML Imports are going to end up being only HTML and they’ll still just use script and link tags to pull in the related JS and CSS.
By introducing these assets externally to keep your sanity, the already asynchronous HTML imports are going to also be waiting on these other assets, and tracking the readiness of these imports gets even more difficult than asset readiness for HTML Imports on their own or CSS/JS loading on their own.
Breaks the value gained from CSS/JS minifiers and preprocessors, because if you’re housing all of these in HTML Imports you aren’t combining them. I’ve seen some proposals that our pipelines learn to extract and combine the JS and CSS from our dependency trees of imports. At that point, what’s the point of HTML imports?
And of course, this increases the number of HTTP requests without clear ways to combine as we would CSS and JS files.

The Case Needed For HTML Imports

Frankly, at this point, I wonder why HTML Imports were introduced at all. What is this really gaining us? What problem did the HTML Import solve? It is really hard to gauge a solution when the problem it aims to help with isn’t even clear in the first place.
If you have an understanding of them that clarifies or counters any of this, please let me know.

Comments

Popular posts from this blog

On Pruning Your Passions [MOVED]

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…