ootachi

17 ms·

121.
by ootachi 15y ago
I'm well aware that, at the moment, the canvas context is restricted to a single thread. But this could be changed. All you have to do is to provide an API to move a canvas context to a different thread/worker. This is quite simple. There's
122.
by ootachi 15y ago
The proposal that roc and smfr put forth is this: Native code could call Web APIs, slightly tweaked for the benefit of native code and to satisfy the security/isolation guarantees that Chrome wants to enforce. These same APIs would have Jav
123.
by ootachi 15y ago
So extend the Web APIs to handle this. You don't have to do synchronous calls. Robert O'Callahan talked in that thread about the potential for extending the capabilities of Web Workers to allow the kind of things you want to do to be done a
124.
by ootachi 15y ago
I think the responses from the other browser manufacturers were pretty convincing. The problem, if you read the thread, was not that NPAPI was sufficient. The problem was that Chrome wanted to reinvent all sorts of APIs that already existed
125.
by ootachi 15y ago
For reference, here are the thoughts of Robert O'Callahan from Mozilla (and those of Simon Fraser from Apple) on Pepper: https://mail.mozilla.org/pipermail/plugin-futures/2010-April... The thread (which continues into May) goes over prett
126.
by ootachi 15y ago
My apologies then. Google does do that with V8, but your practices sound great.
127.
by ootachi 15y ago
As stated in the commit logs, this doesn't improve performance on any of the relevant benchmarks, and V8 is still generally king of those (although V8 has been losing to SpiderMonkey on SunSpider for some time now).
128.
by ootachi 15y ago
It's Apple's (and Google's) modus operandi. They work in secret, and then they make huge code drops every so often.
129.
by ootachi 15y ago
Technologies that are no longer growing tend to result in cost-cutting, leading to engineers in the US and Europe getting laid off for offshoring. So "if it's not growing, it's dead" is actually a rather good approximation of the status quo
130.
by ootachi 15y ago
Are you going to say the same thing about the FileSystem API, Dart, and NaCl? Google is probably the worst browser vendor when it comes to having competing implementations of their proprietary features.
131.
by ootachi 15y ago
Yeah, this is not an excuse at all. You can't argue in defense of Google from an "it's nonstandard" angle, because Google is all about nonstandard Web extensions these days -- to a much larger extent than Microsoft. You can't argue in defen
132.
by ootachi 15y ago
Why are you giving Google, of all companies, a pass because they just "copied from a tutorial"? Google is probably the least deserving company in the entire world of the engineering ignorance defense. Think about it: Google knows enough abo
133.
by ootachi 15y ago
And what happens when Apple starts revoking the code signatures of grey-market apps like emulators, BitTorrent clients, and so on?
134.
by ootachi 15y ago
The other browser vendors have built fast JavaScript engines as well, and they seem to think that Dart is unnecessary.
135.
by ootachi 15y ago
I think you're pretty naïve if you think that "Google doesn't care if Chrome is perceived as faster". That's been the entire thrust of their marketing, quite literally from day one.
136.
by ootachi 15y ago
Amazon, eBay, Craigslist. Especially that last one.
137.
by ootachi 15y ago
Horribly designed sites can dominate old markets too. Amazon is the perfect example of why design doesn't matter. Likewise Craigslist and eBay... the list goes on and on. It's all about marketing and luck.
138.
by ootachi 15y ago
Nope. It's the era of success by marketing and luck, as it always has been and always will be. Engineering is, as usual, pretty much irrelevant to success. That includes UX.
139.
by ootachi 15y ago
Incremental and generational GC.
140.
by ootachi 15y ago
The Firebug code is really scary, for one.
141.
by ootachi 15y ago
Discriminated unions are neither architecture-dependent nor unsafe.
142.
by ootachi 15y ago
Sure, Google is doing the least-bad thing if you take as axiomatic that you're going to have to store your mail in plaintext on the servers of some enormous American corporation. There are, of course, alternatives that don't involve storing
143.
by ootachi 15y ago
In other words, employees should just accept lower pay for the good of the company?
144.
by ootachi 15y ago
You haven't considered optimization -- with closed modules, the compiler can statically know, for instance, that "Math.sin" is actually the sine function and can compile that straight down to the hardware instruction. No speculation or guar
145.
by ootachi 15y ago
Bringing up racism, sexism, and homophobia in a discussion of Web standards is a little bit extreme, don't you think?
146.
by ootachi 15y ago
Native Client is built on Pepper, a proprietary Chrome technology. The NPAPI port for other browsers was abandoned.
147.
by ootachi 15y ago
WebKit has an advantage with WebKit prefixes when the prefixes in question have no spec. As DarkShikari said when criticizing the VP8 spec, code is not a spec.
148.
by ootachi 15y ago
The spec was not released alongside the implementation of animations and transforms. It was released much later.
149.
by ootachi 15y ago
WebKit CSS gradient syntax was pretty explicitly overridden by the standards process in favor of a better one. Thankfully, WebKit changed its syntax to match. Note that in a world where the Web was defined as "whatever WebKit renders", whic
150.
by ootachi 15y ago
It wasn't "any member having a veto over doing anything". Don't attack a straw man. It was every other browser manufacturer unanimously saying Dart is a bad idea , and specifically outlining reasons for doing so. The only possible position

More ›