4 ms·

I understand they're annoyed, but "hell"? Chrome put me through a wild goose chase somewhere around version 94 with some non-standard behavior, and Safari 16 ha

by tgv 4y ago

I understand they're annoyed, but "hell"? Chrome put me through a wild goose chase somewhere around version 94 with some non-standard behavior, and Safari 16 has some weird issue with requestAnimationFrame, but "hell"? That's out of proportions.

pier25 4y ago
If you're a game engine or just have a product focused on realtime graphics, issues with requestAnimationFrame can just destroy your product.
tough 4y ago
Man is free to make up their own personal hells
throwayyy479087 4y ago
His complaints are very well outlined. They are a bit niche due to his use case, but they certainly are real, breaking changes out of nowhere. Standards compliance really is the name of the game, and I wish people like GP had more pull to force Apple to make these reasonable changes.
- lucideer 4y ago
  If you think this you haven't read the linked bug reports. His second one in particular is his app relying on unspecified implementation quirks - the Safari devs are responsive due to a desire to be more compatible with Chrome's quirks, not because they've failed to conform to spec. His first bug report is just lazy and devoid of any detail - completely relies on the Safari team to do the work of debugging his app for him.
  - AshleysBrain 4y ago
    I credited the Apple developers with doing a good job in the blog. The point is Apple's policies end up turning what should be a routine bug fix in to a total nightmare. I've filed dozens of issues with Apple and many of them go in to great detail. However when you're pushed for time and dealing with multiple potential emergencies, you can't always manage much more than a "heads up, this looks wrong" type issue. In the case of the first bug, it was indeed a real problem with Safari and it was Apple's responsibility to fix it. Given that Apple are a trillion-dollar company with thousands of employees, and we have a handful of people in an office in south-west London, I think it's reasonable that Apple does more of the heavy lifting investigating Safari issues anyway. Ultimately it's up to Apple to make Safari a high-quality browser, not us, although we still do our bit with bug reports where we can.

by tgv 4y ago

pier25 4y ago

If you're a game engine or just have a product focused on realtime graphics, issues with requestAnimationFrame can just destroy your product.

tough 4y ago

Man is free to make up their own personal hells

throwayyy479087 4y ago

His complaints are very well outlined. They are a bit niche due to his use case, but they certainly are real, breaking changes out of nowhere. Standards compliance really is the name of the game, and I wish people like GP had more pull to force Apple to make these reasonable changes.

lucideer 4y ago
If you think this you haven't read the linked bug reports. His second one in particular is his app relying on unspecified implementation quirks - the Safari devs are responsive due to a desire to be more compatible with Chrome's quirks, not because they've failed to conform to spec. His first bug report is just lazy and devoid of any detail - completely relies on the Safari team to do the work of debugging his app for him.
- AshleysBrain 4y ago
  I credited the Apple developers with doing a good job in the blog. The point is Apple's policies end up turning what should be a routine bug fix in to a total nightmare. I've filed dozens of issues with Apple and many of them go in to great detail. However when you're pushed for time and dealing with multiple potential emergencies, you can't always manage much more than a "heads up, this looks wrong" type issue. In the case of the first bug, it was indeed a real problem with Safari and it was Apple's responsibility to fix it. Given that Apple are a trillion-dollar company with thousands of employees, and we have a handful of people in an office in south-west London, I think it's reasonable that Apple does more of the heavy lifting investigating Safari issues anyway. Ultimately it's up to Apple to make Safari a high-quality browser, not us, although we still do our bit with bug reports where we can.