3 ms·
JS apps nowadays have so many layers that often something breaks over time or if you run it with the wrong version of node. Frontend post react is an absolute
by jokethrowaway 4y ago
JS apps nowadays have so many layers that often something breaks over time or if you run it with the wrong version of node.
Frontend post react is an absolute nightmare:
My experience with a fleet of semi abandoned next.js static websites is pretty terrible: just in months something stops working in my pipeline on vercel and I need to spend time to debug it. Running things locally is even worse, I just change the code, push and hope for the best.
Python is a downright nightmare: between 2vs3 and pip, egg, venv, I usually just salvage the code I need and try to make it work or convert it to something saner (eg. I did that with an opencv algorithm I found - I just transposed it to rust + the same opencv api calls). My favourite story happened literally 2 days ago. I was trying to install a dependency (keras_ocr) and I kept failing on some dependency; I tried installing that dependency manually and it worked but no success on installing keras_ocr. Eventually I updated pip and it started working.
I had huge problems running old Go software, I think I succeeded once after a lot of pain and gave up the other times.
I had fairly good results with ancient C, C++, Java and Haskell.
Probably because they started before we had cool and glamorous developers on twitter selling you a course and not maintaining his 200 leftpad libraries.
I'm curious to see where Rust will sit in a few years.
- Rauchg 4y agoHey jokethrowaway. I'd love to get more color on your experience upgrading your Next.js sites: feel free to email rauchg@vercel.com. - On local: `npm i && next dev` is guaranteed to be stable. - On remote: your pipeline is guaranteed to be stable. If you have an example where this is not the case, please let me know.