5 ms·

We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta. First, we've had a problem wit

We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta. First, we've had a problem with nextjs not caching the response code for 404 pages, so 404 pages would have a 200 status code. Now they've fixed this they have a bug where they are caching the 304 response code, responding with 304 to every request and completely breaking the site. This has been open for a month now and has affected a lot of people but it seems like Vercel just doesn't care. https://github.com/vercel/next.js/issues/56018 https://github.com/vercel/next.js/issues/56018

lwhi 3y ago
This is my big problem with proprietary software; and why open source pragmatically makes more sense. Fixing bugs is down to priority and incentives of the parent company.
- lucasmerlin 3y ago
  I mean it is open source and someone even made a PR to fix the bug in question and I guess I could use their fork until it's fixed.
  - lwhi 3y ago
    Hmm, doesn't seem as much of an issue now.
  - chasd00 3y ago
    I was about to say, just fox the bug submit a pull request and use your fork until it’s merged. Isn’t that the point of all these fancy source control tools?
ervine 3y ago
Yep their github management is atrocious. I understand it's a popular product so you get a lot of low quality issues opened, but there tons of real problems where no developer ever appears, and then are closed by the bot because of inactivity. Infuriating. The longer I do this, the more that issue management responsiveness becomes a real consideration when choosing a dependency.
- chasd00 3y ago
  I’m not trying to victim blame but why not fork and fix the bug? Isn’t that the point of open source? If you’re not paying for support then I feel you should set expectations accordingly. Do they offer any kind of sla or some other guarantee on responding to an issue? (I work in enterprise stacks where there’s a hard contract that defines these things so maybe biased)
  - ervine 3y ago
    Yep absolutely, I agree and understand how much we're getting for free. On the other hand, their marketing and hype machine has gotten the industry at large to buy into their product. So when you promise enough to get companies to move to your (free, open source) tech stack, but then are MIA when there are issues... I am of two minds. But yes at the end of the day you're right.

lwhi 3y ago

This is my big problem with proprietary software; and why open source pragmatically makes more sense. Fixing bugs is down to priority and incentives of the parent company.

lucasmerlin 3y ago
I mean it is open source and someone even made a PR to fix the bug in question and I guess I could use their fork until it's fixed.
- lwhi 3y ago
  Hmm, doesn't seem as much of an issue now.
- chasd00 3y ago
  I was about to say, just fox the bug submit a pull request and use your fork until it’s merged. Isn’t that the point of all these fancy source control tools?

ervine 3y ago

Yep their github management is atrocious. I understand it's a popular product so you get a lot of low quality issues opened, but there tons of real problems where no developer ever appears, and then are closed by the bot because of inactivity. Infuriating. The longer I do this, the more that issue management responsiveness becomes a real consideration when choosing a dependency.

chasd00 3y ago
I’m not trying to victim blame but why not fork and fix the bug? Isn’t that the point of open source? If you’re not paying for support then I feel you should set expectations accordingly. Do they offer any kind of sla or some other guarantee on responding to an issue? (I work in enterprise stacks where there’s a hard contract that defines these things so maybe biased)
- ervine 3y ago
  Yep absolutely, I agree and understand how much we're getting for free. On the other hand, their marketing and hype machine has gotten the industry at large to buy into their product. So when you promise enough to get companies to move to your (free, open source) tech stack, but then are MIA when there are issues... I am of two minds. But yes at the end of the day you're right.