Tony Sullivan

The hidden costs of JS metaframeworks

There are some really important implications of building your web product with a metaframework. These don't get talked about enough.

If “fullstack dev” wasn’t a thing, would tools like Tailwind and NextJS still be popular?

If a new hire dev needs to manage everything from the database to CSS, of course they’ll reach for magic solutions that promise to do everything.

I can’t help but think these tools were reactions to the industry abandoning specialization.

Web 3.0 is officially here

And no, it isn't git masquerading as a monetary policy. The web is moving from an ad platform to an AI training platform.

Using the latest frameworks & libraries can absolutely help you ship faster

Once it’s shipped though, you have much less tech debt if you stuck with “boring” tech

I’ve got a hunch there’s a strong correlation between # of dependencies and faith in the product-market fit

To the end, if love to see a “feature complete” flag similar to deprecation warnings

Would be handy to know a dependency is still actively maintained and the API won’t break on me later

The existential risk of AI isn’t bad actors, it’s our own arrogance.

Assuming that intent matters depends on being able to first predict the outcome.

We still can’t even say how or why existing AI do what they do, we definitely can’t predict the outcome of new changes.