How to Make Websites That Will Require Lots of Your Time and Energy - Jim Nielsen’s Blog
- Install Stuff Indiscriminately From npm
- Pick a Framework Before You Know You Need One
- Always, Always Require a Compilation Step
The web historically moves in waves.
Libraries are created to push complex features in an easier way. Then the libraries themselves get complicated, often more so than the benefits they provide.
Eventually, (some of) the core features of those libraries make their way into the browser itself, but the libraries linger like water on the shore, slowly receding.
And before the sand has a chance to fully dry, a new set of libraries washes in to push the web even further.
- Install Stuff Indiscriminately From npm
- Pick a Framework Before You Know You Need One
- Always, Always Require a Compilation Step
Grrr…
Chrome, Edge and Firefox updates usually reach 95% of users within three months. But Safari updates are tied to a new release of the underlying operating system, so they take around 19 months to reach the same usage, and some updates may even need a new device.
This is so shameful. And glad as I am to see new features landing in Safari, as long as they hobble updates like this it’s all just pissing in the wind.
The joy came flooding back to me! It turns out browser APIs are really good now.
A great talk by Matthias on what you can do with web standards today!
I should be using the lh
and rlh
units more enough—they’re supported across the board!
HTML’s new `command` attribute on the `button` element could be a game-changer.
Technically, websites can do just about anything that native apps can do. And yet the actual experience of using the web on mobile is worse than ever.
A redesign with modern CSS.
It’s kind of ridiculous that this functionality doesn’t exist yet.
A genuinely inspiring event.