Lets talk metaframeworks
My interest in full-stack hybrid rendering and the corresponding tools was sparked by Rich Harris’ talk at Jamstack Conf 2021 titled “Transitional Apps” (you can find the transcription here, thanks to Geoff Rich). At the time, I was in the middle of my personal JavaScript fatigue (and SPA fatigue) escalation, and the ideas expressed by Rich resonated deeply with me. There wasn’t a sticky name for this approach yet, so “transitional apps” was a kind of first attempt at naming it.
Several years later, this idea is ubiquitous and is more or less consistently called “metaframeworks.”
As the name implies, a metaframework is something that’s built on top of a framework, yet it also represents the intrinsic essence underlying the conventional framework entity. Yes, I see you yawning already. Practically, it’s a set of tools that complement a UI framework (like React, Angular, Vue, or whatnot) with server-side functionality and deployment adapters. Sometimes, there are many more features included, but that’s the gist of it.
There are lots of tools in this category, and I’m pretty sure you’ve heard of them — if not used them already (or on a day-to-day basis, like myself).
There are also lots of opinions about them, with complexity and developer experience often sitting on opposite sides of the scale. The only objective truth is that metaframeworks are something we need to live with, whether we want to or not, and they are, in most cases, a great example of good engineering, with many open-source contributors participating.
What I personally love about the metaframework movement and its rise in popularity is the emphasis on progressive enhancement and the flexibility that new technologies bring, including the possibilities of building your own bespoke systems using battle-tested tools and templates.
I want to dig deeper into this whole metaframeworks story, and that’s why I’d like to humbly share with you two things I’ve just started to give myself a good kick into 2025.
The first is the open-source Encyclopedia of Metaframeworks in the form of an awesome-list, familiar to everyone. I’ve gathered the tools and links accumulated in my closet throughout the years, and I invite you to check it out and join the ride.
fyodorio
/
awesome-metaframeworks
A curated list of awesome resources related to software development with metaframeworks
Encyclopedia of Metaframeworks
A curated list of awesome resources related to software development with metaframeworks.
Table of contents
- Metaframeworks
- Metaframework-like tools
- Meta-metaframeworks
- Building parts
- AI tools
- Auxiliary tools
- Metaframework heroes
- Comparisons and benchmarks
- Metaframework PROs
- Metaframework CONs
- Construction site
- OSS examples built with metaframeworks
- Newsletters
- Podcasts
Metaframeworks
- Next.js. React-based framework for building full-stack web applications.
- Remix / React Router. Web standards focused React metaframework.
- Nuxt. Vue-based framework for performant and production-grade full-stack web apps.
- Quasar. The enterprise-ready cross-platform Vue framework.
- SvelteKit. A framework for rapidly developing robust, performant web applications using Svelte.
- SolidStart. Fine-grained reactivity goes fullstack.
- TanStack Start. Full-stack React framework powered by TanStack Router.
- Analog. The fullstack Angular metaframework.
- Qwik City. Qwik-based set of tooling for building extremely performant full-stack applications.
- RedwoodJS. Batteries-included React- and RSC-based full-stack web framework for startups.
- Fresh. Deno-based full-stack web framework using…
The second is the Metaframeworks Weekly newsletter. This will be a regular, focused dive into the world of metaframeworks and the ecosystem around them — tools, news, releases, people, and so on. You’ll hardly find pompous odes to metaframeworks there; rather, you’ll find an unbiased view of the topic and objective, multifaceted opinions.
All in all, I hope some of these resources might be of use to you, and maybe you’ll even be willing to contribute to them — whether by providing insightful submissions for the encyclopedia or by dropping me interesting relevant findings from around the web via email.
With that, remember that the truth is always somewhere in the middle, and it tastes not like shiny Twitter influencer tarts but rather like your home-cooked, granny-recipe cakes.
Happy new year ?
The cover photo by Carter Yocham from Unsplash
The above is the detailed content of Lets talk metaframeworks. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Different JavaScript engines have different effects when parsing and executing JavaScript code, because the implementation principles and optimization strategies of each engine differ. 1. Lexical analysis: convert source code into lexical unit. 2. Grammar analysis: Generate an abstract syntax tree. 3. Optimization and compilation: Generate machine code through the JIT compiler. 4. Execute: Run the machine code. V8 engine optimizes through instant compilation and hidden class, SpiderMonkey uses a type inference system, resulting in different performance performance on the same code.

Python is more suitable for beginners, with a smooth learning curve and concise syntax; JavaScript is suitable for front-end development, with a steep learning curve and flexible syntax. 1. Python syntax is intuitive and suitable for data science and back-end development. 2. JavaScript is flexible and widely used in front-end and server-side programming.

The shift from C/C to JavaScript requires adapting to dynamic typing, garbage collection and asynchronous programming. 1) C/C is a statically typed language that requires manual memory management, while JavaScript is dynamically typed and garbage collection is automatically processed. 2) C/C needs to be compiled into machine code, while JavaScript is an interpreted language. 3) JavaScript introduces concepts such as closures, prototype chains and Promise, which enhances flexibility and asynchronous programming capabilities.

The main uses of JavaScript in web development include client interaction, form verification and asynchronous communication. 1) Dynamic content update and user interaction through DOM operations; 2) Client verification is carried out before the user submits data to improve the user experience; 3) Refreshless communication with the server is achieved through AJAX technology.

JavaScript's application in the real world includes front-end and back-end development. 1) Display front-end applications by building a TODO list application, involving DOM operations and event processing. 2) Build RESTfulAPI through Node.js and Express to demonstrate back-end applications.

Understanding how JavaScript engine works internally is important to developers because it helps write more efficient code and understand performance bottlenecks and optimization strategies. 1) The engine's workflow includes three stages: parsing, compiling and execution; 2) During the execution process, the engine will perform dynamic optimization, such as inline cache and hidden classes; 3) Best practices include avoiding global variables, optimizing loops, using const and lets, and avoiding excessive use of closures.

Python and JavaScript have their own advantages and disadvantages in terms of community, libraries and resources. 1) The Python community is friendly and suitable for beginners, but the front-end development resources are not as rich as JavaScript. 2) Python is powerful in data science and machine learning libraries, while JavaScript is better in front-end development libraries and frameworks. 3) Both have rich learning resources, but Python is suitable for starting with official documents, while JavaScript is better with MDNWebDocs. The choice should be based on project needs and personal interests.

Both Python and JavaScript's choices in development environments are important. 1) Python's development environment includes PyCharm, JupyterNotebook and Anaconda, which are suitable for data science and rapid prototyping. 2) The development environment of JavaScript includes Node.js, VSCode and Webpack, which are suitable for front-end and back-end development. Choosing the right tools according to project needs can improve development efficiency and project success rate.
