Jens Oliver Meiert

Use my latest work: latest tech book · latest non-tech book · latest optimization tool · latest defense tool

JavaScript

Compressor.js Next

Optimizing the JavaScript image compressor and converter.

#15 · · tools, development, performance, optimization

HTML Minifier Next: Even Faster, JavaScript Minification With SWC, SVG Minification

On making HMN better and better.

#14 · · tools, development, html, performance, optimization

Testing 10 JavaScript Frameworks on Their HTML Defaults

When you validate the demo and starter projects of popular frameworks like React, Vue, Angular, Svelte, Astro, &c., what do you find? On challenging the idea that JavaScript frameworks could fuel the HTML crisis.

#13 · · development, frameworks, html, conformance

JS Frameworks, in Their Own Words (by Word Cloud)

Handing the microphone to React, Vue.js, Angular, Svelte, Express, Meteor, and Next.js.

#12 · · development, frameworks

April 24 Is JS Naked Day

Every year on April 9 we, a part of our field, do without CSS; from this year on, on April 24, there’s an opportunity to temporarily swear off JavaScript.

#11 · · development

In Critical Defense of Frontend Development

The field of frontend development is in another crisis, largely due to an incomplete, misinterpreted definition and a bizarre mess created by “web development as a commodity” and “web development as software development.” How frontend development is more than development, and what we can (and should) do.

#10 · · development, html, css, quality, design

The 4 Pillars of Good Embed Code

Embed code is third-party code to be integrated on websites and apps, like ads or social media widgets. There have been many problems with embed code for a very long time. This post covers the essence of what makes for good embed code.

#9 · · development, quality, html

On the Responsibility That Comes With Good JavaScript Support

According to our data, the classic idea of making sure websites and apps work without JavaScript being enabled is dead; when we look only at support requirements, this was the end of the story. It’s not, however, when we employ a broader look at JavaScript and its misuses.

#8 · · development

“Must Work Without JavaScript”

That websites should work without JavaScript has a long professional tradition, and for apps much the same has been asked for. Yet with the success and ubiquity of scripting, how relevant is it to make sure sites and apps “work without JavaScript”?

#7 · · development

The Problem With Web Development Checklists, or: The Frontend Checklist, Revised

Checklists are a great way to make sure nothing gets forgotten, yet they are problematic when they contain items that aren’t important. A few general thoughts and a very specific review of The Frontend Checklist—of which 33 guidelines appear useful, and 41 not (yet).

#6 · · development, html, css

The Compact Guide to Web Maintainability: 200 Tips and Resources

The result of reviewing, normalizing, rephrasing, sorting, and testing 134 responses to a maintainability survey that yielded more than 500 data points, to form a new guide, a new and more definite guide to web maintainability.

#5 · · development, html, css, maintainability

Two Paradigms of Web Development

On a sunny Tuesday in Düsseldorf a few weeks back, at Beyond Tellerrand, I had a pleasant recorded conversation with the team of Working Draft. In our discussion we briefly touched on the idea of web development paradigms…

#4 · · development, html, css

Maintainable Social Script Integration

In my book, a website embeds all those third-party “share” and “like” and “+1” scripts like: this.

#3 · · tools, development, maintainability

HTML and Non-Script Styling

If you are to style a document differently based on whether certain technology is available, you should keep two things in mind: HTML itself is static and separation of concerns is important for maintainability…

#2 · · development, html, maintainability

“window.scrollTo()” or: When to Stay Clear of User Agents

If you were to ask me whether you as a web designer or developer should do anything about user agent issues, my answer was a clear “no.” It’s not your responsibility. You may lack important insight into decisions made on the user agent side…

#1 · · development