Repeat the same content over and over on top of each other, and you can move each of them just a smidge in 3D space creating the illusion of shape.
You can build your own TypeScript build process, and you might want to if you need true type checking and compatibility with a wider ecosystem of tools. But lots of tools, including now Node itself, just accept TypeScript as if it were JavaScript.
Why can’t we see if a feature is polyfillable or able to be progressively enhanced in the baseline data? There are reasons.
It’s quite fun to have an element react to another element scrolling in an unexpected way!
TanStack Start enhances the TanStack Router by adding a server layer that improves performance through server-side rendering (SSR) and isomorphic loaders.
“… props that match a property on the Custom Element instance will be assigned as properties, otherwise they will be assigned as attributes.”
If it can go in a Docker, Fly can host it, and they’ll help you with that. Adam Rackis takes a look at the platform and shows off all the things he likes about it.
The fourth issue of The HTML Review is out. Wonderful writing framed by entirely different and unusual interactive interfaces, brought to you by the power of web technology. A zine come to life.
Just try to pick a favorite.
Steve Yegge makes the prediction in Revenge of the junior developer that this current wave of AI “agents” that help us code with more capability than just type ahead suggestions and refactorings, like file creation, command line usage, and more, is just the fourth wave of six. The fifth is an individual developer managing multiple agents (a “cluster”) which gives way to “fleets” of agents in the sixth.
The revenge part? Junior developers, less stuck in their ways, will be quicker to adapt to these new ways of working. I think it’s interesting to think about, but my experience, the value of someone who deeply knows how to understand a system and fix and prevent problems, traits that define a senior developer, will remain as valuable as ever.
I enjoyed this blog post from Blake Watson about a simple requirement and then going down the rabbit hole of functional programming to solve it in increasingly reusable, if mind-bending ways. By the end:
Creating a function that returns a function that returns a function can get a little trippy to think about. But what we’ve done is make our work reusable and flexible.
Blake admits he didn’t actually use the fully functional abstracted functional version. I vibe with that. Take it as far as you can without sacrificing clarity.
Chrome 135 (in Beta as I write, probably stable early April?) will have customizable select elements in it. You opt-in to it in CSS, and once you have, you can go ham on styling regular ol’ <select>, <option>, ‘n’ friends elements. Very progressive-enhancement friendly as a select without custom styling is… fine.
It’s interesting and notable that even when it does ship Chrome is prepared to protect the web:
Chrome has the features behind a Finch experiment in case there is an emergency need to turn it off. If things go well, the experiment will end and the code will be shipped permanently into the source.
I’ve seen people playing!
position: sticky;legend (👍)Little boosts of front-end development news, information, and advice — right to your feed reader of choice.
RSSHere's our page on guest writing. It's a win-win-win!
Frontend Masters donates to open source projects through thanks.dev and Open Collective, as well as donates to non-profits like The Last Mile, Annie Canons, and Vets Who Code.