959 karma · joined September 19, 2022
And this mindset + your background just keeps explaining your problems and struggles. Don't blame the tools.
I think this explains pretty well the difficulties you are having.
And also, you’ve been hired for the wrong job.
A company I workerd for has a large nuxt app they won’t be to upgrade any time soon.
Just the way to use react or vue the way it was intended to be used, paired (in a beautiful way) with a real backend framework such as Laravel, Rails, Django or Adonis.
I’m so done with every weeks new “full stack framework” that doesn’t do anything but routing and has an uncertain future.
I’m glad I noticed this early and stopped using Next on time. For me the thing that made me realize this was their “hiding” (for as much as they can) and making it more difficult than intended of the call home metrics system in next. They refuse to add a setting to turn that off, and instead want you to set an env variable or run a npm command.
Just think about they do this and refuse to add a setting.
That’s how you know who you’re dealing with.
Doesn’t sound like a great idea to me.
At some point people will realize there’s some value on full stack batteries included frameworks that have been around for a long time.
Until the next dev comes to the project and doesn’t agree with your opinions, right? I’ve seen this movie far too many times.
The main benefits of these frameworks is that they remove all the bike shedding decisions. And I trust more something used by a lot of people and battle proven even if I don’t 100% agree with everything.
What you think is the best library for validations is just an opinion as theirs, and for example I don’t think Zod is good at all. See? Now on a team of 5 people we have 6 different preferences and we have to schedule 10 meetings to decide what library is best. And next month we will regret using it anyways.
There is a reason Rails, Laravel, Django etc are so popular in their ecosystem.
I honestly don’t believe the “I can do better all of this by myself”. It’s usually an undocumented, unproven, buggy and insecure mess that only the main author knows how it works.
Have a proper backend doing all the backend stuff and just render page components as if they where just the views of the framework.
All this server components nonsense is solving a problem that maybe Facebook has but almost no one else does. But people think they do, so a lot of complexity is added for no real reason.
Most narcissist high on the hill comment I’ve ever read on HN.
GTFO.
Also, react has nothing to do with all of this. This is about backend.
Laravel is a great example of this kind of framework, and with inertia you can use react in a sensible way.
And also, htmx is no way the solution to anything g of this. It’s only useful for the minimal examples, you can build anything slightly advanced with it without everything becoming a mess.
I still miss that “watooo” sound when you received a message.
Good times. Thanks for being part of my first days on the internet. Rest in peace.
That's a very optimistic view of the situation.