|
|
|
|
|
by jokethrowaway
963 days ago
|
|
Absolutely agree, I did a fair bit of both and I really regret using the framework du jour. I have a lot of websites (maybe more than 20) and they're a mix of old version of next.js, hand rolled websites and some solid.js websites. The solid.js sites are fairly easy to update - but it's also very new (the oldest being 3 years) and I'm not sure it will stay that way forever. You just need one wrong decision from the fun guys at ECMA and frankly I've been burned already by commonjs vs esm. The handcrafted sites from 10 years ago have some old and simple dependencies and they work fine.
The next.js stuff is a horrible nightmare of different errors. Everytime I need to do a one-line change I get to do a nice debugging session.
This is also a combination of the providers I'm using not having a fixed node version, but I've also found some dependencies breaking compat from one patch to another. I guess the key takeaway is: use as little deps as possible. |
|