Version 4 is now open-source! While it is still under development 🚧, feel free to explore the codebase, try it in your Nuxt app, or even deploy a test instance to Cloudflare Workers.
@murisceman Just saying hi and thanks for your work on @pruvious! It has been 🤯🤯🤯 so far! Fast website development and easy to explain to my colleagues!
We have been made aware that the Advanced Custom Fields plugin on the WordPress directory has been taken over by WordPress dot org.
A plugin under active development has never been unilaterally and forcibly taken away from its creator without consent in the 21 year history of WordPress.
I don't know why I don't use infer more often. Just learned a cool way to deal with types of "computed" values in a dynamic object with callbacks (needed this for some database model options).
The todo application with @pruvious and @nuxt_js. The dashboard is just a "side effect" that is automatically created from the code 🙃
https://t.co/XUhCcaFnlq
The todo application. 😅
But, seriously, here's the thing...
When Laravel and Rails developers say "full stack", they mean something totally different than when Next or Remix (React Router?) developers say "full stack".
In Laravel and Rails, it means there are built-in, opinionated solutions to things like validation, interacting with a database, authenticating users, scheduling background work, sending an email.
In Next and Remix, it seems to mean that there is simply the bare ability to run code on the server at all and an advertisement for Clerk. 🙃
From my perspective, Next and others are really, really great at the GET part of web development. Get data from some backend, show it on the page quickly. 👌
They are not mature for POST, PUT, and DELETE, especially when things start getting non-trivial.
And, I don't think this is really unique to Next or a single framework. It's something that seems to pervade current JavaScript as a whole - note the current proliferation of "starter kits" that try to bring some sanity to the full-stack story.
I think this has had actual consequences in the JavaScript ecosystem...
Rails and Laravel were built with the express purpose of allowing a single developer to build the next GitHub... or the next AirBnb... or the next Shopify. Prototyped from beginning to end.
That's what I'm passionate about. Empowering a single developer or small team to build something amazing.
I built the 1.0 of Laravel Forge, Envoyer, Vapor, Spark, and the backend of Nova by myself.
$40M in revenue over 10 years from my home office. That's an empowering tool for a solo founder.
I don't see a full-stack story in JavaScript yet that would allow me to realistically sit down and build something like Forge or Vapor from start to finish. Maybe I'm missing it. 🤷♂️
The MVP start-ups I do see fully built on current JS meta frameworks are much thinner. The stereotypical API call to an AI service. Not much meat on the bones.
Laravel / Rails have been building their modern front end story with Hotwire, Livewire, Inertia, and more... Next and others are building their modern back end story.
Smart people on both sides working on these problems, so I'm confident we'll both get to where we want to go. 💪
@danielcroe SquirreLLC love eating those acorns, and they bury a portion of them in places the little oak could not reach, helping it spread even further.