om2

31 ms·

331.
by om2 9y ago
Safari's sandbox is weaker in some ways and stronger in others. Saying which is overall stronger would be a judgment call. I wouldn't make a claim like that without spelling out at least some of the details. This subthread is abou
332.
by om2 9y ago
Most trackers use cookies or other client-side state to track you across the web. There's also various fingerprinting techniques but they are less reliable.
333.
by om2 9y ago
They do. Breaking out of the sandbox is not trivial though over time people have found ways to do it.
334.
by om2 9y ago
Safari sandbox isn't identical to Chrome's but it's pretty effective. I don't think your statement is a fair one without qualification. ETA: we'd appreciate info about specific info wrong with Safari's sandboxi
335.
by om2 9y ago
In current iOS Safari, webpage scrolling is inconsistent from all other scrolling on the system. This was an intentional decision made long ago. In addition, overflow areas are consistent with the rest of the system, and thus inconsistent
336.
by om2 10y ago
WebAssembly has solved the problem of validating for memory-safety and other requirements of web safety and security. SPIR-V has not. SPIR-V is known usable as a shader format and can be used directly with some APIs (which then translate in
337.
by om2 10y ago
JavaScriptCore (WebKit's JS engine) also optimized for Octane. But we additionally optimized for Speedometer, Sunspider (the not totally broken subset that made it into Jetstream) and JSBench. While Octane isn't the single answer
338.
by om2 10y ago
WebGPU is designed to support use of the GPU for graphics as well as computation in a way that aligns with modern GPU APIs such as Metal, Vulkan and DirectX 12. It will provide more efficient graphics as well as GPU compute.
339.
by om2 10y ago
We'll probably look at existing cross-platform binary shader formats like SPIR-V, or alternately consider something based on Web Assembly.
340.
by om2 10y ago
A WebKit contributor just added Compute support: https://trac.webkit.org/changeset/215131/webkit We're planning to post new Compute demos as soon as this makes it into Safari Technology Preview.
341.
by om2 10y ago
We have all major browser vendors on board with discussing these things in the W3C's GPU for the Web Community Group, and we expect to end up with a final result based on multiple prototypes as inputs. Submissions so far include: Apple
342.
by om2 10y ago
> When people claim to cure cancer it's sort of an oxymoron. What about animal species that get cancer much more rarely, or never? Are naked mole rats an oxymoron?
343.
by om2 10y ago
All debates are bravery debates. https://slatestarcodex.com/2013/06/09/all-debates-are-braver...
344.
by om2 10y ago
Music has a different history and context. The music publishers started to use DRM-free music as a competitive wedge between sellers of digital music, mostly as a wedge against Apple. Then Apple decided to also go DRM-free. Unfortunately mu
345.
by om2 10y ago
Let's say the W3C had the power to stop EME from existing, and not just to refuse to give its implied blessing. Would the result be no DRM on "premium" video? I doubt it. The de fact approach before EME existed was to use plu
346.
by om2 10y ago
Serious question, have you ever written any nontrivial code using Vulkan? Everyone I know who's ever coded using Vulkan has found it unpleasant, and even Khronos is considering a higher level API (more along the lines of Metal) because
347.
by om2 10y ago
In the case of web standards, the null hypothesis is "no new API" rather than "make something that works only on top of this specific native API". For the web, the latter is not even the default assumption once you'
348.
by om2 10y ago
I'm being a little generous to myselff with saying "we". I'm on the WebKit team and I followed this project but I wasn't personally involved in implementing it.
349.
by om2 10y ago
It's Metal-inspired, but we tried to use JS API design idioms where possible. It does help that Metal is already an object-oriented design instead of bare functions passing around primitive values and structs.
350.
by om2 10y ago
I don't think passing command buffers or structures in memory will be an obstacle to security. The main security issues will likely be: * Avoiding out of bounds memory reads * Avoiding threadsafety issues * Figuring out lifetime for ev
351.
by om2 10y ago
It's really hard to make the example complex enough for experts without completely losing most people. This is deliberately a simple example. The string thing is the way enums tend to be done in modern JS APIs. It's not really a b
352.
by om2 10y ago
We are working on many of the things you list. We are able to work on more than one thing at a time though.
353.
by om2 10y ago
I appreciate this comment. We did indeed discuss this widely. No one thought that an API which only works on top of Vulkan was right, everyone in the relevant sector thinks it has to support the big three. Very few thought modeling the API
354.
by om2 10y ago
I appreciate the list of issues affecting home screen web apps on iOS. We're looking into improving how they work. I can't promise any specific set of improvements or timeline but we are aware of the issues you mention.
355.
by om2 10y ago
We did actually build a standard tied deeply OpenGL, it's called WebGL. And indeed, we foresee the need to move beyond it (though WebGL is still plenty good and not a dead end yet.) Worth noting also that Khronos is considering a sligh
356.
by om2 10y ago
Thoroughly solving the security problems will require more eyes on it than just ours. Which is why we're proposing a starting point for a standard, and a process to work on it, not an endpoint.
357.
by om2 10y ago
WebAssembly doesn't currently have a way to expose APIs to it directly. It only has an interface to call JavaScript. Maybe that will change, but blocking on a major new WebAssembly feature did not seem wise.
358.
by om2 10y ago
I think rough consensus and running code will end up more convincing than the things you suggest. So that's what we're working towards.
359.
by om2 10y ago
It's likely there will be a need for a C++-level meta-API that can work on top of Vulkan, D3D and Metal. There's already been discussion of making such a thing. It would be nice if that could be exposed to WebAssembly via Emscript
360.
by om2 10y ago
Making a new standard is inevitable. That's not really a choice. Even if the web platform directly replicated one of the existing APIs, you still have to explain how it binds to JavaScript, as well as memory and GPU resource management

More ›