Of course. It's just a coincidence that they're placing onerous restrictions on competi- I mean alternative browser engines. Restrictions which, of course, they're not obliged to follow themselves.
I am sure that Apple will make no other efforts to impede others from unwalling the garden. That would be completely ridiculous, and frankly, un-Apple-esque.
Both Chrome and Firefox are already compliant, so I don't see it as onerous, but the full context of the list is indeed an extremely loud and clear "FUCK YOU, WE OWN YOU" to regulators and other browser vendors.
Theres C++ in military airplanes, they just cut out 90% of the features: https://www.stroustrup.com/JSF-AV-rules.pdf
And heres a nice video about it: https://youtu.be/Gv4sDL9Ljww?si=Z4riPMKAKcIKaU0s
Yes, in WebKit, SaferCPP guidelines are enforced by a static analysis tool.
My work bans raw new and delete, so we only use unique_ptr. It's not as memory safe as Rust's borrow checker but I've never seen a segfault.
Yes, they do this, and it's really not an unreasonable requirement.
Of course. It's just a coincidence that they're placing onerous restrictions on competi- I mean alternative browser engines. Restrictions which, of course, they're not obliged to follow themselves.
I am sure that Apple will make no other efforts to impede others from unwalling the garden. That would be completely ridiculous, and frankly, un-Apple-esque.
Both Chrome and Firefox are already compliant, so I don't see it as onerous, but the full context of the list is indeed an extremely loud and clear "FUCK YOU, WE OWN YOU" to regulators and other browser vendors.
Which of the restrictions do you feel they don’t abide by? It looks like they meet all their own restrictions
10 replies →