Offler

Just work on making Ghost better if you have a problem with it, why would we need yet another version of it? Because it's written in PHP?

Good news as you can now use ES6 generators in Node.js and when combined with another ES6 feature, Promises it can result in much nicer async code e.g. http://taskjs.org/

ES6 is looking very nice indeed, great thing is that with Node you won't have to worry about old browser support.

Wages go up.

I think Firefox has been Metro optimized.

You need to URL encode it for it to work in Firefox.

data:text/html, <style type%3D"text%2Fcss">%23e{position%3Aabsolute%3Btop%3A0%3Bright%3A0%3Bbottom%3A0%3Bleft%3A0%3B}<%2Fstyle><div id%3D"e"><%2Fdiv><script src%3D"http%3A%2F%2Fd1n0x3qji82z53.cloudfront.net%2Fsrc-min-noconflict%2Face.js" type%3D"text%2Fjavascript" charset%3D"utf-8"><%2Fscript><script>var e%3Dace.edit("e")%3Be.setTheme("ace%2Ftheme%2Fmonokai")%3Be.getSession().setMode("ace%2Fmode%2Fruby")%3B<%2Fscript>

The Guardian.

Some of those things are improving in ES6 with block scoping and modules.

Chrome is a big black window for me, literally you see nothing at all. So I use Fx.

Both browsers have issues.

Mozilla aren't able to ship a full Firefox on iOS though.

Within a year ES6 will be shipping and available, already generators have been implemented in V8. Combine them with http://taskjs.org/ and you have callback hell relegated to a distant memory.

Did it stop being relevant? It's just a reminder of the risks you run when running a and developing for a closed garden. It's a good point, always worth underlining it I guess.

FF 20 does lack the asm.js integration.

If it was inspected more regularly I'd imagine the chances of it exploding would have been reduced.

Everyone should be shimming ES5 array methods so your good example could quite happily run on older browsers too.

I've found memory leaks in long running single pages apps that were down to jQuery UI components so I wouldn't dismiss jQuery performance doubts so quickly.

There is also the problem of upgrading third party libraries as they may drop APIs or change their behavior leading to so many bugs that you spend more time fixing these issues then if you had written native code in the first place.

Drop support for old IE browsers, why are people still trying to fight to support them. I agree with the blog post, one day people will finally drop support for non-HTML5 browsers (IE8 and below) and they will see how easy it is to write clear, short native code that works fine in all browsers.

It will take time though as many people aren't even familiar with the native APIs.

"Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger."

This is huge for me, it makes debugging impossible when loading.

They eventually want to be competitive against C++ code and it seems they won't support TCO as that would harm their performance target.

Because they want it to die.

No harm in putting it back up on the front page again, I never saw it the first time.

The browser will eat everything.

And Rust, linked to that Servo seems very interesting.

The sooner we get Generator support everywhere the better so we can start using http://taskjs.org/ and stop talking about these issues.

Mozilla have limited resources and a large number of more important projects that could do with those limited resources.

V8 was new and WebKit was still a newer codebase than Gecko.

The security restrictions regarding add-ons make sense, I believe Chrome has just recently adopted them due to the browser being owned by hacked websites.

Thunderbird was a silly waste of resources and should have been shelved well before they did.

In balance I'm quite happy Mozilla exist and have been generally positive.

V8 doesn't support Asm.js.

Presumably to squeeze out maximum performance from multi-core machines. Current engines are all single thread per page instance.

Could you not just fix it? Or drop support for IE6/7/8 and only support the newer IE browsers?