There are quite a few “gotchas,” developers face when getting into the new @function syntax of CSS. Some are getting addressed!
I think it’s fun to take stock of the tools we use as developers. You know, so we can look back and laugh at our primitive setups. And actually, to inspire you to share yours so I can steal all your better tools. Here’s a rundown of stuff I use, focused mostly on literal apps […]
All sorts of great stuff coming up for all our members. Intermediate React, Complete Go, CSS Basics, TypeScript Monorepos, and so much more.
There is some low-hanging web performance fruit with images. Serving them in the right format, from a CDN, with the right HTML can be a big perf win.
The & is a powerful addition to CSS, allowing us to craft selectors without repetition and helping organization and understanding.
The typical approach for these inputs is using multiple HTML inputs, one for each character. But is that a good idea?
There are A LOT of options these days for getting AI help right in your code editor. What seemed to begin with plugins has morphed into a lot of VS Code forks.
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 (👍)Developer 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.