Yes. I’m dealing with a graphql, urql, Next, Prisma stack at the moment. Something that would be a handful of lines of code in a different stack ends up being hundreds in this one.

The Node ecosystem is full of wrong abstractions.

▲

Rohansi 3 hours ago | parent | next [-]

The problem is self-inflicted. You do not need to keep jumping to the next trendy framework.

▲

christophilus 2 hours ago | parent | next [-]

I inherited this one. My preferred SPA stack these days involves Porsager’s Postgres library, a simple RPC stack with Zod schemas, and Preact.

Even better is an old school MPA with progressive enhancement.

▲

RussianCow 3 hours ago | parent | prev | next [-]

I don't know about you, but I generally don't write code in a vacuum. Other people may have touched it before me. Those other people may have made poor decisions.

Not that I'm immune from choosing the wrong abstraction sometimes. More than once the "other people" was me. We all make mistakes.

▲

Rohansi 3 hours ago | parent [-]

Of course, but we should all be doing our best to push back against unnecessary framework churn.

	▲	em-bee 3 hours ago \| parent \| next [-]
		if the majority of the team agrees, sure. but if i am in the minority then i'll appear uncooperative, and that may not be a position i want to be in.
	▲	Capricorn2481 3 hours ago \| parent \| prev [-]
		Do you want us to call the previous company and explain what their framework choices did?

▲

em-bee 3 hours ago | parent | prev [-]

my paycheck needs me to.

▲

cpursley 2 hours ago | parent | prev [-]

Nextjs in particular is a dumpster fire, it's a shame that it's the default stack many LLMs slop out.