3 ms·
> Regressions tend to be high priority for the devs though so this will be fixed eventually. "eventually" is right... This seems to be a failure on the part o
by web007 9y ago
> Regressions tend to be high priority for the devs though so this will be fixed eventually.
"eventually" is right...
This seems to be a failure on the part of the devs to prioritize. AFAIK code that causes a regression should be reverted and fixed properly, not left affecting the product for FIVE YEARS before finding a fix. The burden can not be on every use case to work around a bug that was introduced, the core "fix" is clearly a half-fix and should have been reverted on identification.
- uhhhhhhh 9y agoI mostly agree, but if we want to be pedantic, this didn't regress something so much as fix horrible performance for 90% of apps and introduced a previous non-existent bug into certain applications due to a non-thread safe bug. The solution itself turned out to be simple enough, and the time it took to fix is definitely not excusable considering the effort vs impact IMO.