Alright folks: I opened up zine shipping to Canada, but I regret to inform you that shipping is like seventeen goddamned dollars just to get something up there.
sure could get this done quicker if I got a few “letters” with questions or opinions about HTML for the letters page, along with how the authors would like to be attributed, if at all, in response to this post
In case you missed it*, the JavaScript course I wrote for the Chrome dev team launched a few weeks back.
Whether you’re just starting to figure out where the semicolons go, or want a microscopic view of the objects that make up the objects that make up the objects that prototype the {} you just typed, Learn JavaScript has something for you. https://web.dev/learn/javascript/
If you’ve been wondering about the Core Web Vitals change from “First Input Delay” to “Interaction to Next Paint”—or wondering what FID was all about in the first place—I wrote it up on the Frontend Masters blog for you:
Learn JavaScript is a brisk 30,000 words on everything from “what’s an expression” to “wait, is it really called the ‘temporal dead zone’” to the difference between seeing @@match and match in documentation to using static initialization blocks in your classes.
Now, if this autocomplete were instead making use of today’s advanced AI technologies, it would suggest that I am asking about the weather at one specific Forever 21 store, yes, BUT it would do so with the environmental impact of pushing a 1997 Eagle Talon TSi full of nine-volt batteries into the Charles River.
Sure, AMP sucked, and everyone hated it, and it served no practical purpose outside of being a vehicle for algorithmic “nice placement, sure would be a shame if something happened to it” extortion, but I think we can all agree on the main issue: it simply did not do enough to humiliate publishers, who could still try to push good, meaningful writing through the set of janky pipes they were forced to lease under threat.
I’m making some zines about HTML. The first one is gonna be about headings, I am accepting contributions, and buddy, you better believe it contains ten-pound cusses.
can’t have a zine without a page or two for letters, so send in your Big Web Thoughts, nerds: editor@multipa.ge
keep it short-ish, include the name you’d want it published under (or anonymous), and if it’s the kind of thing that expects a reply from Me, The Editor, you’d get it on paper—no promises on what will end up getting used, though
Genuinely curious: what’s the point in developer advocacy or developer relations work if the parent company requires radio silence during periods of extreme criticism, facing backlash for the company’s direction and decisions?
Shouldn’t this be the moment in which your team are most useful?