om2

17 ms·

151.
by om2 7y ago
We sincerely think a text-based language is better for the web. It’s honestly weird that anyone thinks a binary format is a good webby choice. Both our browser engine people and our GPU software people agree. Khronos basically said in that
152.
by om2 7y ago
Maybe I should have said that some tricks are slow to deploy. Sometimes the publisher only embeds an image form the tracker (the famed "tracking pixel"). Getting lots of sites to change that to script is a pain. Sometimes they nee
153.
by om2 7y ago
If Google had any motive besides research and responsible disclosure, it would more likely be to persuade us that ITP is not viable. But I think their issue was fair and submitted in good faith.
154.
by om2 7y ago
We're willing to play the cat and mouse game indefinitely, if that's what it takes. Widely deployed trackers are limited in how fast they can try new tricks. And in practice, we know that ITP is working pretty well to block cross-
155.
Preventing Tracking Prevention Tracking(webkit.org)
212 points by om2 7y ago|74 comments
156.
by om2 7y ago
Contents property itself is not a private API. Quality of docs I can't speak to, but it's a different issue than private API (which is stuff that's not in the public SDK).
157.
by om2 7y ago
CoreAnimation is not a private API. Everything directly mentioned in that post is public API. Firefox may use private API but it’s not mentioned in the post.
158.
by om2 7y ago
These are notes from a live presentation at the WebKit Contributors Meeting. All the items were explained live, there is only so much the notes can convey.
159.
WebGPU and WSL in Web Inspector (WebKit) Has(webkit.org)
2 points by om2 7y ago|0 comments
160.
by om2 7y ago
Preventing exfiltration by a tool that's by definition allowed to affect outgoing network traffic via blocking is an impossible problem.
161.
by om2 7y ago
This model is also a big performance win. The content blocker rules are compiled to an [efficient byte code format]( https://webkit.org/blog/3476/content-blockers-first-look/ ) which can be evaluated insanely
162.
by om2 7y ago
three.js does shader generation at runtime and I expect they don’t want to significantly increase their download size by adding a compiler, so a text-based language is likely better for frameworks like that. The calculus may be different fo
163.
by om2 7y ago
SPIR-V with full web safety rules and translation to native shader formats is not really simpler to implement than WSL with those same properties. People make these claims but the code doesn’t best that out. There’s also a good chance that
164.
by om2 7y ago
> I'm using part of this idea in my prototype tracing JIT for CRuby. With a tracing JIT it's much, much easier to implement basic escape analysis because the control flow is linear. One basically gets Partial Escape Analysis (t
165.
by om2 7y ago
Shipping support for both a text format and a binary format directly in the browser is in some ways the worst of both worlds. If both are implemented natively, you get double the attack surface at the ingestion layer. If the text format is
166.
by om2 7y ago
The set of web safety changes for SPIR-V is kind of new and immature in my opinion. I agree that it's building on a core that is widely deployed in other contexts.
167.
by om2 7y ago
I have followed the WebGPU CG discussions about differences between the APIs and what features one has that the other doesn't. The initial goal of the API is to have a solid core, and not rely on extensions for important functionality.
168.
by om2 7y ago
Browser vendors are a lot better at writing compilers than GPU vendors. Also there are fewer different browser engines than different GPU drivers so that also helps.
169.
by om2 7y ago
> The WebGPU working group does not currently have any participation from AMD or NVIDIA. Khronos and the SPIR-V working group do. I trust them to get these details right. On the other hand, the SPIR-V working group has no participation f
170.
by om2 7y ago
When someone says one option is a nonstarter because it's new and immature, I think its fair to look at different signs of maturity to evaluate that statement. (I personally don't think any option is a "nonstarter" but i
171.
by om2 7y ago
Please do! It's working for me with STP 91 on a Catalina beta build. Could be a hardware-specific issue. A bug report would be useful. Please Cc mjs at apple dot com and I'll make sure the right people see it. For reference, do th
172.
by om2 7y ago
I've reported the video issue to the author. The demo site requires STP 91 or newer with the WebGPU experimental feature enabled.
173.
by om2 7y ago
Turns out that the intersection is already a huge advance over WebGL, and that much of the stuff outside the intersection is of marginal value or even outright regrettable.
174.
by om2 7y ago
Specialization constants don’t seem to cut it for all the use cases. There’s variation beyond plugging in constants. Also some frameworks and engines give their clients the ability to provide shader snippets at runtime.
175.
by om2 7y ago
We (Apple) have privately reached out to quite a few JS frameworks and web game engines. We’re trying to take all their input into account and to share it with the WG.
176.
by om2 7y ago
But no tests for the web safety layer afaik.
177.
by om2 7y ago
That’s reasonable feedback.
178.
by om2 7y ago
Our collaboration with Babylon.js happened after most of the spec proposal work. It was inspired by Google’s similar collaboration with Babylon.js prompting Google’s own SPIR-V based implementation of WebGL. This makes the comparison more a
179.
by om2 7y ago
It strangely hasn’t been seriously considered but it might not be a bad option (though it may need a more rigorous reformilation of the spec).
180.
by om2 7y ago
WebGL 2 is still a work in progress in WebKit, not abandoned.

More ›