Maybe, I don't know, I have a hard time believing the hype. Vibe coding doesn't even seem like a real thing to me

@mayank.co You deserve some credit here. You really helped me out with that Template component.

github.com/jonathandewi...

Having been a huge Next.js fan for 5+ years, I have been over it for a while now. They get worse with every new update. It's to the point now that I consider it nearly unusable.

AI is decent, just not nearly as great as executives claim. Also I want to not be harassed with surveys about it.

No problem! And yeah that's not a jab at maintainers at all, it's just the nature of the beast, it can't be helped. But yeah, something like this definitely makes it easier to wrestle with.

Granted, if everyone is just fixing things, you might get less feedback. Maybe, not really sure.

I might reframe the question a bit - I find it more valuable to own the bugs so I can fix them myself. In one scenario, you open a GitHub issue and wait months for it to get picked up and worked into a stable release. In the other, you can just fix it in the same day.

Well, personally I tend to just one-and-done generate them, then they belong to me to maintain from that point forward.

But there are ways though, like with shadcn: github.com/shadcn-ui/ui...

Hmm, I think maybe folks are complaining about the wrong thing. It's not that it's less maintainable, it's that it's more to maintain. IME, owning the code you use is almost always better.

Maybe this shift has yet to take hold in the WC community, but it's taking React by storm.

IMHO, the best UX of design systems is a CLI that generates components directly into the user's project.

See: ShadCN

I'm planning a similar approach but with WCs, but if you get to it first I can't complain

Internet people say snide tactless things, but nothing OVERTLY insulting, baiting you into retaliating so it looks like YOU'RE the aggressor. Then they frame every defense as progressively crazier, until they rally a whole crowd to hate you.

Isn't the internet great?

I know I always talk about being a FC fan, but I do agree FCs should not be repeatedly called nor have stateful side effects.

But then again, no components should imho. Render once, bind directly to nodes, avoid complicated lifecycles and hooks.

Even in Sass, I've always felt that nesting encouraged bad patterns that result in specificity issues.

Guess you did mention compiler and IDE tooling, haha. But now I wonder how far you can take TypeScript

Type checking would have to be an IDE extension, wouldn't it? Not sure TypeScript is smart enough by itself, but I also haven't thought long about it.