Alexander Karan

Make the CEO of Adobe try to cancel their Creative Cloud subscription on Instagram Live.

(2/2) If you want a sneak peek, you can see a PDF version in our GitHub repo. See a mistake or an improvement? Raise a PR and get involved.

github.com/e18e/framewo...

(1/2) Benchmarks are only useful if you understand what's being measured. We've added a glossary to the meta-framework tracker — clear definitions for SSR, CSR, hydration, islands, ISR, PPR, streaming, and more. @e18e.dev

Thank you @jschaeferdev.bsky.social for the contribution

Code Review is the bottleneck now? Always has been

This popped up in my feed and all I can think is Blueberries!!!! Is this one of those things where certain fruits taste like s**t in other countries?

bsky.app/profile/alex...

Is REST Dead... Again? API Developers debate the benefits of REST vs JSON-RPC when working with LLMs. Also in this newsletter: the politics of building APIs, FastAPI's continued growth, a comparison of serverless cold star...

REST is dead... again, Hono CLI, the rise of Fast API, and the politics of APIs, all in the latest issue of the @apisyouwonthate.com newsletter.

apisyouwonthate.com/newsletter/r...

Yep and it’s even worse on Mac!!

You don't want to live in the Liquid Glass nightmare with the rest of us?

What!!!!

I am sorry but the few hours I get each month to play videos games is my happy place.... please don't take new versions away from me. I love my Playstation and Nintendo.

Would happly burn down every LLM and data center fitout to fix this.

Keen to help out in the @e18e.dev community and unsure where to start? We have a host of first good issues in our metaframework comparison project and are super keen to see more of you get involved.

github.com/e18e/framewo...

Thought y’all would enjoy.

Yesterday over on x:

They removed dim mode because the overhead of CSS variables was too much

AI will skip coding and write binaries directly by end of year

a screenshot of a discord team called "POWER TEAM" with 5 members

making good things.

(9/8) I know choosing GitHub Actions as the place to run our tests has downsides. However, this is just the first itteration and we wanted to get the project up and running so we can mess around with visualisations. This is not the final place these tests will run.

(8/8) If you want to play around with some of our initial data, you can find links on our GitHub. Please keep in mind that this is not final and is actively being worked on.

github.com/e18e/framewo...

Performance tracker details page for Astro

(7/8) If you want to see the full details from this first test, check out an in-progress screenshot here:

github.com/e18e/framewo...

(6/8) If you are a framework author, we would love you to get involved, so please reach out in our Discord chat.e18e.dev. If you're interested in contributing, reach out — plenty of good first issues to pick up.

(5/8) We currently track Next.js, React Router, TanStack Start, Nuxt, SvelteKit, Astro, and SolidStart with more on the way. We have a monthly catch-up for framework authors/contributors kicking off soon.

(4/8) We will be adding methodology, trade-offs, and intent to every test we do. The idea is not to point to a single meta-framework as better, but to highlight the best fit for each situation and the trade-offs involved. You can see our initial roadmap for stats here:

github.com/e18e/framewo...

(3/8) No data or results here are final; this is all a work in progress. However, this is an interesting project, so we want to show you progress.

(2/8) In this graph, we break down install time, cold build time, and warm build time for a single framework. We use GitHub Actions as a consistent environment and record the minimum, maximum, and average across multiple runs. We want to be clear about how all these stats are collected and tested.

Build and install time tests for Astro

(1/8) An exciting project over at @e18e.dev is our project: how can we measure performance across meta-frameworks? This means going deeper than just bundle size, but looking at all stats across development and runtime. Here is an example of one of our dev build tests. More details in the thread.

Re the recent performance post. We did remove it in the end to rework the image to make it clearer that it isn't a comparison yet.

We will repost it tomorrow 👍

I'm stoked to talk with the lovely folks at e18e about open source, performance, linting, and all sorts of things!

100% I also mention these are subject to change and are in active development.

These stats are to pique interest, not frame any framework as bad.

This is great. Thank you for raising a PR; I'll take a look.

The main point of sharing these snapshots is to help get engagement and contributions like this. The stats are still in active development.

The site is not live yet, and we are currently setting up a monthly framework author catch-up.

100% it is and this makes it hard to convey these in posts. Which is why we're building a site that measures stats across dev and run time. One of the key focuses will be showing the differences between these frameworks, nuances, tradeoffs in testing, what frameworks are best at what extra...

100% agree with you. The website we're putting together will capture and display these nuances.

Have you considered Jira……..

Sustainable APIs A well designed system can provide utility while reducing overall energy use. Also in this newsletter: Clerk's API Keys product, Express 5.0, Ktor, and an illustrative HTTP code cheat sheet.

@apisyouwonthate.com, latest newsletter is out. A jam-packed issue covering a terrible train API, how sustainable APIs lead to performant APIs, the Express 5 migration, and more.

apisyouwonthate.com/newsletter/b...