I… don’t think there are approximately any bugs of this type that would have much of anything to do with Vercel. And furthermore I am very confident that if you check out the Github repository from 1-2 years ago that you will find many more not many fewer bugs and glitches and inconsistencies.
Happy to take bets on this with almost any operationalization if evaluated by a third party. My guess is you are having some preconceptions here that are causing you to do some confused cause analyses.
I believe there’s been a local increase in bugs since switching to Vercel. It would be shocking if that weren’t true! It was a major website port. That said, I think the general bugginess of the website has been trending down over time, and this local increase is only equivalent to 1-3 years of regression.
I appreciate the assumption of preconceptions, but I began having a poor experience and then discovered the post discussing the move. It was while trying to figure out why things were acting up that I found the announcement of migration.
Most of the time they can’t be replicated, but I figure most people using this site know what I’m talking about.
This is not my experience of using the site. We’re happy to have bugs reported to us, even if they’re difficult to reproduce; we don’t have the bandwidth to fix all of them on any given timeline, but do try to triage those that are high-impact (which will often by true for bugs introduced during such a migration, since those are more likely to affect a large number of users).
Not sure if you’re intending to disagree, but I do sometimes have like a post-list or the quick-takes fail to load, with a red error message instead, and then if I refresh it goes away.
(I can’t recall it happening very often, mostly I see it when I run a dev instance.)
I… don’t think there are approximately any bugs of this type that would have much of anything to do with Vercel. And furthermore I am very confident that if you check out the Github repository from 1-2 years ago that you will find many more not many fewer bugs and glitches and inconsistencies.
Happy to take bets on this with almost any operationalization if evaluated by a third party. My guess is you are having some preconceptions here that are causing you to do some confused cause analyses.
I believe there’s been a local increase in bugs since switching to Vercel. It would be shocking if that weren’t true! It was a major website port. That said, I think the general bugginess of the website has been trending down over time, and this local increase is only equivalent to 1-3 years of regression.
I appreciate the assumption of preconceptions, but I began having a poor experience and then discovered the post discussing the move. It was while trying to figure out why things were acting up that I found the announcement of migration.
This is not my experience of using the site. We’re happy to have bugs reported to us, even if they’re difficult to reproduce; we don’t have the bandwidth to fix all of them on any given timeline, but do try to triage those that are high-impact (which will often by true for bugs introduced during such a migration, since those are more likely to affect a large number of users).
Not sure if you’re intending to disagree, but I do sometimes have like a post-list or the quick-takes fail to load, with a red error message instead, and then if I refresh it goes away.
(I can’t recall it happening very often, mostly I see it when I run a dev instance.)