ootachi

35 ms·

331.
by ootachi 15y ago
Weren't the VCs right in this case, though? The regulatory issues were exactly the problem.
332.
by ootachi 15y ago
That only eliminates the first two outside forces (investors, angels) in the list. You still have to deal with customers and employees - in other words, the market.
333.
by ootachi 15y ago
So does Microsoft, but that didn't stop them from not innovating between IE6 and IE7, for example.
334.
by ootachi 15y ago
And they execute within the context of the page you're currently viewing, which prevents malicious cross-site behavior like that of this extension.
335.
by ootachi 15y ago
That's a bad idea. People will always click through warning and permission screens; increasing the complexity of warning screens simply increases the likelihood that people will click through it without reading it.
336.
Number One Plus(daringfireball.net)
3 points by ootachi 15y ago|0 comments
337.
by ootachi 15y ago
Both San Francisco and San Jose are near the bottom in job growth. This surprises me, given the hiring market for engineers in the Bay Area. What gives?
338.
by ootachi 15y ago
Then you'd be breaking the rules of JS1K, because JS1K demos have to work in Firefox, and Firefox doesn't support this feature (except in quirks mode, which you can't turn on in JS1K).
339.
IonMonkey overview(wiki.mozilla.org)
2 points by ootachi 15y ago|0 comments
340.
Introducing Scratchpad(blog.mozilla.com)
6 points by ootachi 15y ago|0 comments
341.
by ootachi 15y ago
Ahead-of-time compilation of a dynamic language with LLVM will scarcely be faster than an interpreter. This is a very common misconception. Good performance for dynamic languages requires dynamic techniques -- polymorphic inline caches, tra
342.
by ootachi 15y ago
Which doesn't require NaCl. https://bugzilla.mozilla.org/show_bug.cgi?id=644389
343.
by ootachi 15y ago
Those insisting that there's no way this will be another ActiveX would be wise to notice this. We're not even one day into the release and already there's a browser-crashing bug.
344.
by ootachi 15y ago
Yes. Good riddance IMO. Firefox has become a bloated beast over the years, Mozilla is nothing but obstructionist these days, and the sooner the entire web moves to WebKit the better.
345.
by ootachi 15y ago
You don't want JavaScript VMs to be running NaCl's verifier on all the code that they generate. That would be a significant performance loss. Remember that JavaScript engines are fundamentally built around self-modifying code, so the verifi
346.
by ootachi 15y ago
I don't know the particulars of how this is implemented, but you would either have to compile your code for ARM (adding an enormous burden to web development), or have all mobile browsers ship an x86 emulator (which is a massive step backwa
347.
by ootachi 15y ago
You really want every web page to be shipping their own JIT (or forcing users to grab it from a CDN)? JavaScript JITs are huge . Also, the idea that you can just ship a JIT in Native Client and have the performance not hugely regress is
348.
by ootachi 15y ago
You assume wrong. Modern tracing or type-inferring JITs are heavily optimized for the kinds of tight loops you see in image processing.
349.
by ootachi 15y ago
Why not just say "WebKit is the HTML5 spec", then? It'd be less work than coming up with an HTML5 spec from scratch.
350.
by ootachi 15y ago
Real hash tables are coming in ECMAScript Harmony: http://wiki.ecmascript.org/doku.php?id=harmony:simple_maps_a...
351.
by ootachi 15y ago
Shipping LLVM bitcode is a bad idea. The bitcode format is constantly changing from revision to revision, its JIT is huge and slow so you'd have to rewrite a lot of it, .bc files are enormous, the bitcode format is non-portable, the type sy
352.
by ootachi 15y ago
The ethical issues don't bother you?
353.
by ootachi 15y ago
Yeah, the title is really ridiculous here. Chrome won one metric; Firefox won the other. Mozilla has every right to cry foul.
354.
by ootachi 15y ago
The primary function of the Windows key has been to open the Start menu since the day it was introduced. The modifier key aspect of it was always secondary.
355.
by ootachi 15y ago
Are we talking about compile-time or runtime errors here? I can accept that manifest typing leads to more compile-time errors, but the idea that it leads to more runtime errors is nonsense. Types constrain, statically, the set of values tha
356.
by ootachi 15y ago
It's not a "bizarre hack", it's a very common implementation strategy known as integer tagging. You see it everywhere from OCaml to the V8 JavaScript engine.
357.
by ootachi 15y ago
Would you honestly prefer it if browser manufacturers compared pre-release versions to shipping versions? Seems to me that would be far worse.
358.
by ootachi 15y ago
Er... there is no synchronous XHR in the snippet you pasted. All calls to open() pass true for the third parameter.
359.
by ootachi 15y ago
This gives me a warning telling me to switch to Chrome, but when I open it in Chrome it runs slower than in Firefox. That's obnoxious.
360.
by ootachi 15y ago
You admit to not having used Firefox in recent years, so how do you know that Firefox "doesn't compete"?

More ›