3 ms·
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 h
by christophilus 4mo ago
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 4mo agoThe problem is self-inflicted. You do not need to keep jumping to the next trendy framework.
- RussianCow 4mo agoI 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 4mo agoOf course, but we should all be doing our best to push back against unnecessary framework churn.
- Capricorn2481 4mo agoDo you want us to call the previous company and explain what their framework choices did?
- em-bee 4mo agoif 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.
- em-bee 4mo agomy paycheck needs me to.
- christophilus 4mo agoI 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.
- cpursley 4mo agoNextjs in particular is a dumpster fire, it's a shame that it's the default stack many LLMs slop out.