ootachi

37 ms·

361.
by ootachi 15y ago
Have any evidence that Firefox performance is "atrocious"? Firefox JavaScript is faster than any other browser except Chrome (and beats Chrome on some apps like JSLint), and it has GPU acceleration while Chrome does not.
362.
by ootachi 15y ago
It's actually a GNU C extension to the set of legal identifier characters.
363.
by ootachi 15y ago
Exactly. UI is important, and even if find can be written in terms of other tools, its superior UI justifies its existence. It's sort of like SQL: a declarative interface means that a system administrator doesn't have to think how to do s
364.
by ootachi 15y ago
Doesn't work in Firefox. Note to web developers: CSS animations are supported now in Firefox; please use the -moz prefix as well as -webkit.
365.
by ootachi 15y ago
Exactly. There is not a thing that Firefox does that Chrome doesn't do better.
366.
by ootachi 15y ago
Mozilla is pretty much treading water at this point. It's only a matter of time before the inevitable drowning.
367.
by ootachi 15y ago
Pattern matching isn't just a feature to aid concurrent programming; it's extremely helpful for all sorts of code. However, since Go doesn't have unions (either tagged or unsafe), pattern matching in Go wouldn't be particularly powerful any
368.
by ootachi 15y ago
The complexity of the PDF specification isn't what's relevant here. Even if pdf.js were to implement all of the PDF specification, it would still be more secure than Apple's renderer, because it's written in a memory-safe language. This is
369.
by ootachi 15y ago
The latter doesn't really solve the problem. Folks are still going to see that Firefox is using a lot of memory, even if the OS is now more inclined to swap out pages that are less important.
370.
by ootachi 15y ago
"C'mon guys. When's the last time Firefox put Chrome on the offensive." Panorama and GPU acceleration for Firefox 4 come to mind.
371.
by ootachi 15y ago
Yes, Mozilla source code is huge (5.2 million lines [1]). But keep in mind that all browsers are roughly that big (compare Chrome, at 4.8 million lines [2]). [1]: https://www.ohloh.net/p/firefox/analyses/latest [2]: http://www.ohloh.net/
372.
by ootachi 15y ago
"Simply we're being cut to death by bloat and pure, sheer lazyness." All these memory leaks being fixed are "pure, sheer lazyness"? https://bugzilla.mozilla.org/buglist.cgi?keywords=mlk%2C%20&...
373.
by ootachi 15y ago
See my comment below; Mozilla has been well aware of memory fragmentation for years and has been constantly working to decrease it.
374.
by ootachi 15y ago
Mozilla has been well aware of this problem for years. See this blog post from 2008, 3 years ago, detailing the changes that went into optimizing memory use for Firefox 3, including switching to jemalloc to decrease fragmentation: http://b
375.
by ootachi 15y ago
Firefox is automatically updated these days just like Chrome is, so there isn't much of a difference between the two in this regard anymore.
376.
by ootachi 15y ago
Use the Add-on SDK, formerly known as the Jetpack SDK. It's much easier to use than the old extension system. https://addons.mozilla.org/en-US/developers/builder
377.
by ootachi 15y ago
You can simulate comments this way: { "width": "comment goes here", "width": 50, "height": 30 } Yes, it's a terrible hack, but it works in every JSON parser I've seen.
378.
by ootachi 15y ago
The leverage in this case has nothing to do with the specific employment contract and everything to do with the market for engineers right now. I suspect that having the only engineer who understands the code threaten to leave right before
379.
by ootachi 15y ago
WebGL is OpenGL ES. The deprecated stuff in GL 1.0 is not present. See for yourself: http://www.nihilogic.dk/labs/webgl_cheat_sheet/WebGL_Cheat_S...
380.
by ootachi 15y ago
This is the reason why I think it would be preferable for assert() to use eager evaluation. Any optimizing compiler will optimize away the useless check if debug mode is off, even if function calls obscure it (as long as the compiler can re
381.
by ootachi 15y ago
Tabs on the same domain can communicate synchronously.
382.
by ootachi 15y ago
I've long been a PEG skeptic. All three of these benefits have issues: (1) LL parser generators have had zero-or-more and one-or-more operators for a long time (see ANTLR for example [1], as well as the venerable Parse::RecDescent [2]). The
383.
by ootachi 15y ago
Don't forget Firefox either; while Chrome has taken the lead in many areas, Firefox is still ahead in some (graphics acceleration and JavaScript language features for example), and more importantly, Firefox led the way in terms of innovatio
384.
by ootachi 15y ago
This makes it sound like shares are far too risky from a tax standpoint to be worth it for anyone but founders. Startups are risky enough from a career standpoint without having the threat of personal bankruptcy hanging over employees' he
385.
by ootachi 15y ago
Note that the slowness of Object.create in V8 (it forces objects into hashtable mode) is the reason that Chrome did so poorly on the JSLint benchmark. Given the popularity of that benchmark, I suspect that Chrome will get around to optimizi
386.
by ootachi 15y ago
This is an XSS; it's not something that Facebook put out.
387.
by ootachi 15y ago
PNaCl is more than two years away from mainstream adoption though. The system is huge and complex due to the fact that it stretches LLVM far beyond what it was meant to handle. For example, LLVM was never designed to have platform-indepen
388.
by ootachi 15y ago
Well, you could always buy a Mac. It's just a question of the degree of lock-in. And Apple is a master of lock-in: purchased apps for iOS and Mac OS X don't work anywhere else, FairPlay prevents movies purchased from iTunes from working els
389.
by ootachi 15y ago
Also don't forget Cachegrind. Cachegrind is amazing and runs entirely from user space.
390.
by ootachi 15y ago
"And the typography engine that does kerning so badly that it renders several letter combinations in normally clear fonts literally illegible at smaller sizes used by many web sites." The native OS typography engine, you mean? Firefox uses

More ›