om2

9 ms·

61.
by om2 5y ago
Note that the rules limit has now been increased from 50k to 150k. Sorry if we failed to publicize this sufficiently.
62.
by om2 5y ago
What specifically is wrong with a comp model of one-year vesting (instead of 4-year) and no cliff? Whether it's better or worse for employees depends on how they size the grant and in general is very situational. If the company goes up
63.
by om2 5y ago
VP9 has hardware decode support on newer Macs.
64.
by om2 5y ago
Tracking is used pervasively by the ad ecosystem today, but that doesn’t mean tracking is needed for ads to exist. Contextual ads are a thing. FLoC isn’t even replacing the most important use of tracking, which is measurement, not targeting
65.
by om2 5y ago
Apple is doing just fine on greatly reducing tracking, and we don’t think FLoC or anything much like it is necessary. Safari already blocks 3P cookies by default and has done so for a year.
66.
by om2 5y ago
OAuth sometimes is done using an iframe and a pop-up window instead of by navigating to the federated auth provider and back. That version often needs third party cookies.
67.
by om2 5y ago
Safari does actually block all third party cookies by default, not just a subset. And has been doing so for about a year now.
68.
by om2 5y ago
Despite the extended verbal slap down, it's likely Google will ignore most of this feedback and ship anyway. That way, youtube.com, google.com, and double-click.net will be able to freely share third party cookies amongst themselves in
69.
by om2 5y ago
If the proposal was limited to opting into strict origin scope (instead of eTLD+1/registerable domain scope) for cookies and other privacy-related things, it would be an improvement. But it also allows things like specifying that lapto
70.
by om2 5y ago
Right now Google does not feel the need to get any other browser vendors or really any other party besides Google to agree. They ship things that they don't even agree on internally! Their process has review points but actually acting
71.
by om2 5y ago
Even when multiple domains are controlled by the same party, there is often no good way for users to be aware that seemingly unrelated sites with unrelated-looking brands are the same, and therefore (under this proposal) you can be tracked
72.
by om2 5y ago
Chrome has running code, but generally skips the "rough consensus" step.
73.
by om2 6y ago
This post shows that some very simplistic algorithms can’t unambiguously determine a key. But I don’t think it establishes that a more sophisticated algorithm could not. Key center is not just based on chords and notes in a scale. It’s base
74.
by om2 6y ago
Accomplishments on their page include: * Purchased ridehailing app code and completed customizations for NYC launch I wonder who sold them the code and who did the customizations. Do they have software engineers on staff? Do they own and op
75.
by om2 6y ago
The Safe Browsing protocol does have a theoretical vulnerability whereby a malicious provider could create hash buckets on demand with the intent of guessing user URLs. This change would protect users from this theoretical risk. Also, it pr
76.
by om2 6y ago
Wow, that’s a lot of memory use. Would you be willing to file a Feedback Assistant report with a sysdiagnose? Would like to see what’s up here. How many tabs is this?
77.
by om2 6y ago
Could you share which specific ones? In Safari 14 we changed our WebGL to be fully based on ANGLE, and that fixed more compact issues than it caused, but there may still be some bug tail which we are trying to clean up in updates.
78.
by om2 6y ago
There were many reasons for the split, but as far as I know this was not one of them. There was no patch backlog, and there were many reviewers on the Chrome team. I think it was a combo of desire for control and debates over various archit
79.
by om2 6y ago
The biggest source of Google search traffic is doubtless Chrome, and Google doesn’t have to make a deal for that.
80.
by om2 6y ago
I don’t think anyone exhibited a version that got to acceptable binary size and startup/execution time. Might be that it would have been possible with way more effort.
81.
by om2 6y ago
Google folks who have been primary designers of the new shader language have been deeply involved in SPIR-V; and Apple has made its own shading language, Metal. Apple also produces GPUs that ship in very high volume via A-series SoCs. I’m n
82.
by om2 6y ago
> Safety, maybe not 100%, but this could be fixed with extensions, and transformations. The same transformations that WGSL compilers will apply. What I’m telling you is that defining these checks and transformations is the hard part, not
83.
by om2 6y ago
SPIR-V by itself does not have the needed safety or interoperability properties for the web, or the advantages of text formats that the web has benefitted from. These are the more important factors, not IPR considerations. Fortunately, we l
84.
by om2 6y ago
We are aware of the interest and I think we're generally in favor of it, but nothing specific to announce about timing.
85.
by om2 6y ago
It would be easier to swap JS engines than other browser engine components probably, but yeah, not trivial. The patches to make WebKit support choice of JSC or V8 were janky in the first place and constrained what we could do.
86.
by om2 6y ago
OK, this is the part where I have to admit I know a lot less about React than about browser engines. :-)
87.
by om2 6y ago
We removed support for non-JSC engines immediately after the Blink form.
88.
by om2 6y ago
This is a slightly weird example because it's adding an empty <div>, so you can imagine it could be optimized if it provably has no effect on layout. But let's imagine instead that the node added to parent was a div with a t
89.
by om2 6y ago
If the code is hot, there is no perf difference in modern JavaScript engines. They will speculate and both your var access and length property access turn into just simple a memory read or a constant.
90.
by om2 6y ago
All browsers have used a dirty bit for layout for at least the past 2 decades (source: I have worked on browser engines for 2 decades). This is not some new Chrome thing. And all browsers continue to have that same hazard that querying layo

More ›