Basically every metaframework except Astro, Remix, Qwikcity, and Fresh now has its core being developed by developers under @vercel.com.
Same license, roadmap, and open governance, but now in a joint mission to build the best web.
Basically every metaframework except Astro, Remix, Qwikcity, and Fresh now has its core being developed by developers under @vercel.com.
Ultimately Astro will keep growing faster, addressing way more use cases than docs/blogs
I'm still happy that Docusaurus was able to compete for a while on npm stats as a niche React metaframework
We'll continue to make it a good option
Ultimately Astro will keep growing faster, addressing way more use cases than docs/blogs
I'm still happy that Docusaurus was able to compete for a while on npm stats as a niche React metaframework
We'll continue to make it a good option
New in 1.0:
* Zero-Config Live Views via SSE
* Drizzle Support
* "Native" HTTP support (no tRPC)
* Void Router
* Vite plugin
* Clientside Garbage Collection
* Performance & scalability improvements
fate.technology/posts/fate-1.0
New in 1.0:
* Zero-Config Live Views via SSE
* Drizzle Support
* "Native" HTTP support (no tRPC)
* Void Router
* Vite plugin
* Clientside Garbage Collection
* Performance & scalability improvements
fate.technology/posts/fate-1.0
- React Typescript.
- Tanstack Start (best metaframework imo).
- Chakra (or Panda-css).
- If 3rd party API: Hono.
- No ORM (fuck em).
- Tanstack Query.
- Rarely using state manager (fuck em)
- Zod
- React Typescript.
- Tanstack Start (best metaframework imo).
- Chakra (or Panda-css).
- If 3rd party API: Hono.
- No ORM (fuck em).
- Tanstack Query.
- Rarely using state manager (fuck em)
- Zod
github.com/e18e/framewo...
github.com/e18e/framewo...
also: metaframework when?
also: metaframework when?
youtu.be/4V_Wz_k35C8?...
youtu.be/4V_Wz_k35C8?...
- Dev/prod differences are the devil. Make them not possible.
- Forces you architecture the framework from day 1 to have fast and incremental builds.
- Dev/prod differences are the devil. Make them not possible.
- Forces you architecture the framework from day 1 to have fast and incremental builds.
Number 1 metaframework for interest, retention and positive sentiment for the third year running.
Number 1 metaframework for interest, retention and positive sentiment for the third year running.
Personally, I'm quite against it -- metaframeworks tend to be massive time commitments and produce sub-standard results as they try to hit way too many use cases. For a lib as flexible & open as Preact, a metaframework would only close
Personally, I'm quite against it -- metaframeworks tend to be massive time commitments and produce sub-standard results as they try to hit way too many use cases. For a lib as flexible & open as Preact, a metaframework would only close
Mediaclass media management components for MetaFramework
🔗 https://github.com/aboleon/metaframework-mediaclass
Mediaclass media management components for MetaFramework
🔗 https://github.com/aboleon/metaframework-mediaclass
This week, we look at security topics: from corresponding Arcjet’s best practices for Next.js and Remix, to a recent Vite vulnerability with insightful findings derived, and a sneak peek at the buildless Deno-based framework, Ruck. Stay safe and stay curious!
This week, we look at security topics: from corresponding Arcjet’s best practices for Next.js and Remix, to a recent Vite vulnerability with insightful findings derived, and a sneak peek at the buildless Deno-based framework, Ruck. Stay safe and stay curious!
www.youtube.com/watch?v=gNA8...
www.youtube.com/watch?v=gNA8...
Plus: New Fonts API, CSP support, an experimental new Rust compiler, and more...
astro.build/blog/astro-6...