I enjoyed this article on #vim #minimalism, even though it's a bit too extreme for my taste. I too try to keep my setup as lean and use as much built-in functionality as possible. But I still think syntax highlighting and LSPs are genuinely useful. #LSP feedback should be entirely on-demand of course. And compiling commits with #fugitive is just so much faster and more flexible than with the #git #cli. But apart from that… right on!

https://yobibyte.github.io/vim.html

I've recently found that many confuse attributes and properties in web components and javascript. Here's a quick explainer with some opinions and life advice:

https://jschof.dev/posts/2025/4/attributes-are-not-properties/

Shift+Cmd+P in #chrome #devtools and search for "CSS overview", pretty nice tool which also shows you unused CSS lingering around.
Best of course, if there is none ;)

#browser #webdev #useThePlatform
#development

TIL: an <input list="mylist"> can be an input and select, in native HTML

<datalist id="mylist">
<option value="one"></option>
<option value="two"></option>
</datalist>

See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/email#providing_default_options

#useThePlatform #HTML
one more reason for #noFramework

You think you need an SPA?
Try this and you feel no difference (often):
1) extremely fast loading page
2) onunload: store scroll offset e.g. in localStorage
3) at the bottom of the HTML restore scroll offset
4) make slow JS inside the page async and use nice spinners

And voilà a page load feels like an inline content update, just like an SPA.

If you want you can also add
@view-transition {
navigation: auto;
}
which makes it even smoother in browsers that support it

One of the teams I've been working with to climb the performance management maturity ladder is...Edge!?!

We build a *lot* of the browser out of web "stuff" these days (think bookmarks, history, downloads, settings, new-tab-page, etc.), and moving away from React to a modern Web Components + HTML-first architecture has had a *huge* benefit for users, particularly folks on low-end hardware:

https://blogs.windows.com/msedgedev/2024/05/28/an-even-faster-microsoft-edge/

Still lots of js packages out there for copy to clipboard functionality, feels like these are relics that should all be marked as obsolete, but that is work that is often not bothered with I guess.

https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/writeText

navigator.clipboard.writeText('whatever');

There is a lot of talk about how #webDev is more complicated than ever, but in all these ways it is also simpler than ever with increasingly powerful and well adopted standards

In an earlier post, I shared a (surprisingly) uncontroversial CSS hot take. I also cross-posted on LinkedIn and received generally amenable responses.

Yesterday evening, I threw together a proof of concept to convert valid JSON into namespaced CSS variables.

https://host.sonspring.com/json-to-css-var

^ Presupposing style values in a JSON format, it is pretty straightforward to output the flattened hierarchy as CSS variables.

CSS hot take: I'm beginning to think any design system that exposes style values via anything other than CSS variables — ex: Sass, JavaScript, TypeScript — is essentially doing it wrong.

I am of the opinion that publishing a standalone file with all the CSS variables used in a project is probably the most widely compatible future-facing approach.

#css #designsystems #usetheplatform

https://www.freecodecamp.org/news/what-are-css-variables-and-how-to-use-them/

Today opened a PR to use native CSS nesting in prod on a real application. Working with CSS has never been so easy and so good.

> You can't get faster than No Build

"The state of the art is no longer in finding more sophisticated ways to build JavaScript or CSS. It's not to build at all. To lean on HTTP/2 and the now universal support for import maps to avoid bundling."

https://world.hey.com/dhh/you-can-t-get-faster-than-no-build-7a44131c

Funny how I was drumming about JSDoc two years ago in meetups and got plenty weird looks and now it's trendy again.

Going to launch the talk again and tell everybody about #usetheplatform

One thing I will say: Rust on the web is overkill. I know, it's tempting to have something like leptos and have a single language on both frontend and backend.

What you should be doing is using the web platform. Most work should be done on the server anyways, your front end code should only be used for progressive enhancement. The user shouldn't have to run JavaScript in order to use your site. Plain and simple.

#rustlang #usetheplatform #webdev #webdevelopment

Spent bit of time today replacing a React + Emotion ProgressBar <div> party with a #html <progress> element. #CSS for these is still a little tricky, definitely doable, but documentation seems somewhat lacking. My simple example.

https://codepen.io/aeischeid/pen/qBQVQmm

This was used inside of a table cells for a large many row MUI DataGrid so just getting the Emotion styles out of the cell render was a noticeable performance bump, but reducing nodes also helped probably.

<Input type="date" > is well supported now, and all the browser implementations I have tried so far work at least as well as, if not better than, the vast majority of js datepickers I have used through the years.

The only hard part left is convincing designers...