> I have a hard time reconciling the claim—that a feature implemented in the same year wasn’t for many years after—as a good faith opening of the conversation.
I think you're vastly over-ascribing a lot of malice to what has been a pretty harsh & specific tragic trauma that I/some others may not specifically remember, over this.
I missed some basically pointless details? So what? I remember Safari rejecting something that seemed elemental & necessary, & rebuffing essentials. I failed to see a small, short-lived specific, before the inner anti-web Safari beast took back over & re-asserted control. You seem to have vast sympathy for the 10 year absence of this feature, based off of 25 months of availability, before being snuffed out for- literally- the excuse of cheapness. 'We don't want to maintain it.'
> I didn’t know the history of this particular API when I saw the comment,
Bro, I thought it did. But you are agitating for a lot of scorn & anger my way for having missed a detail. It's an interesting footnote. But I fail to see how it impacts the pent-up frustration that's developed over the intervening decade since. What's the relevance here?
I don’t know what trauma you’ve experienced, but if you have and it’s presenting itself in missing browser functionality I hope you’ll take some time off to rest, you surely deserve it and very likely need it. And I apologize for the aggressive way I framed my comment.
Many are burnt out from Safari being a boat anchor being held in place by app-store control. We want to be be able to leave this spot & move on. But we are all anchored here. There is no rest from this, no remedy is coming, we can only drown ourselves in temprary forgetting of the pervasive unjust suppression.
SharedWorkers was but one (particularly salty) place crucial to the enterprise where Safari took an anti- stand.
I think you're vastly over-ascribing a lot of malice to what has been a pretty harsh & specific tragic trauma that I/some others may not specifically remember, over this.
I missed some basically pointless details? So what? I remember Safari rejecting something that seemed elemental & necessary, & rebuffing essentials. I failed to see a small, short-lived specific, before the inner anti-web Safari beast took back over & re-asserted control. You seem to have vast sympathy for the 10 year absence of this feature, based off of 25 months of availability, before being snuffed out for- literally- the excuse of cheapness. 'We don't want to maintain it.'
> I didn’t know the history of this particular API when I saw the comment,
Bro, I thought it did. But you are agitating for a lot of scorn & anger my way for having missed a detail. It's an interesting footnote. But I fail to see how it impacts the pent-up frustration that's developed over the intervening decade since. What's the relevance here?