randomuxx

...the boy who cried wolf. You know how the story ends.

Another little fun project from the creator of NitroJs, UnJS ecosystem etc

I’ve worked with Next.js professionally for the past 3 years, and it’s been torture. (hosted on Vercel, and the company used almost every single service Vercel sold. Worst vendor locked-in ever)

I replied to Dan’s previous HN post about RSC, sharing how I had a terrible experience and he was right to highlight: "I think RSC itself is pretty solid by this point but frameworks around it (primarily Next.js) are still somewhat rough."

React is fairly mid overall, and Next.js is only accelerating its bad reputation. Stay away!

what's that '.bn' extension? Banana Republic?

Cool app though

Fair Dan, and I appreciate your response.

I also hope you understand I wrote this based on my experience with it. ♥

Maybe I'm slow, but after countless posts about RSC, I still don't get the appeal.

Is it really worth the headache and extra complexity?

Caveat: I've used Vue more than any other FE library/framework, but for the last 3 years I worked exclusively with React (via Next—app router). The company I worked (I left in Jan) for jumped on this RSC train as soon as it was released and boy,oh boy was it a mess! We ofteb got direct support from Vercel when our shit will break or not work as expected...

To say the app was slow and behaved unexpected would be an understatement.

Eventually, they had to rewrite everything back as a SPA.

SSO is horrible. AMA

Kudos to the new faker.js 'team'

On the other hand, this further proofs exactly how replaceable one can be... especially those who want to `sacrifice` themselves for opensource work.

Get a job to sustain yourself and your family; then contribute to open source when you are bored or for fun...