1. add library javascript
2. add app javascript
3. …oh no, this is too much javascript
4. let’s add more javascript for client-side navigation so that we don’t have to re-run the other javascript
5. …oh no

the toilet paper industry will sell you a hyper-localized drone delivery solution to ensure that you will never run out of toilet paper during business time when all you really needed was a bidet

in this essay about the JavaScript industrial complex I will…

✅ Use the latest version of an ESM dependency: fine.
✅ Use the latest version of a CJS dependency: also fine.
❌ Pinning to a previous CJS major release that worked without issues after they bumped a major release for nothing other than ESM: ew, what? no—gross

Suspense (sə-spĕns′)

> Anxiety or apprehension resulting from an uncertain, undecided, or mysterious situation.
> The state or quality of being undecided, uncertain, or indecisive.

…in hindsight maybe not the best branding choice.

It strikes me that it might be useful to have a comprehensive web performance analysis tool with similar flame graph output that reports a holistic view of the performance of a web site (showing how every asset on the site influences the performance, not just JavaScript execution).

Does this exist?

when my dog gets eye boogies and I know she doesn’t have the anatomical equipment required to even have a chance at removing them—imma get those out immediately every time. I’ll chase her around the house, I’m getting those boogies out

A build step is great for front-end developers because it’s forgiving to code outside the specialty of front-end.

We can write slow and inefficient back-end code 😅 and pair it with what we’re good at: high quality, efficient, high-performance front end code.

@eleventy Don’t get me wrong, I’m all in on Mastodon and this is my home base moving forward—but I really pushed hard to set an example and cut-off Twitter 100% across-the-board.

I’m learning that this was not entirely tenable for a Brand Account—especially when folks with large follower counts weren’t willing to do the same.

I think @eleventy is going to have to return to at least broadcast content to Twitter, unfortunately. Given that a large portion of JavaScript folks have really dug in over there—it is doing harm to the project to not exist in those spaces.

Having some real feelings about it—mostly disappointment that folks didn’t make a bigger push to get off of the site.