|
|
|
|
|
by slightlyoff
282 days ago
|
|
I'm simply pointing out that Apple declined to try to constructively solve the problems developers expressed, demurred from engaging in design work in many areas, and did not ship alternatives instead (as it could have, and did in the past when Safari/WebKit were not on a starvation budget). The downsides to this are not lost on me. Why do you think I'm making an issue of it publicly now? We tried literally everything else. This is last resort stuff. The goal is always more collaboration, and through it, better, better-funded, and more capable browsers. Apple is the unique obstacle to all of that today. |
|
Sometimes, the right response to a feature proposal is simply "no". But you're seemingly unwilling to accept that as a valid answer. The alternative you're not seeing is that of not having the dubious features in the browser.