[bgribble]

> But it's a bit disappointing to see that it's still pretty much a one-man project.

I don't know much about this project and I have never used it. But in my experience as a developer and user of software I couldn't disagree more.

The longer something can stay a one-person project, the better! Nothing kills creativity, innovation, and velocity faster than having to make every decision by committee.

Big communities are great when a project is in its maturity and mostly needs tending and slow evolution. They mitigate the risk of a single developer getting bored and walking away, or turning into a murderous wacko, or attempting to monetize the project to death. Not naming any names.

But when something is being built from scratch? Give me a single developer with a fat internet connection, alone in a cabin in the woods with a shed out back full of Red Bull :)

[The_Colonel]

> The longer something can stay a one-person project, the better! Nothing kills creativity, innovation, and velocity faster than having to make every decision by committee.

One person can get surprisingly far, but there's a limit beyond which no single human will scale. Getting to the v8 performance is IMHO such an example. You might be OK with a browser which has a noticeably subpar performance, but it will likely stifle mainstream adoption (which again, might be OK for you and that's fine).

[tredre3]

> Getting to the v8 performance is IMHO such an example.

There's no doubt in my mind that Andreas could achieve that by himself. He's worked professionally on webkit, and implemented a JS interpreter, a JS bytecode interpreter, and a JS JIT all by himself after all. Also let's not forget that V8 is open-source, all their optimizations are available for others to see and implement.

But to be clear this isn't a one man project, he hired a few contributors to work full time on it. Sure, it's a small team, but as said in sibling comments a small team has much more velocity.

[materielle]

Andreas isn’t targeting V8’s JIT performance. The goal is to be roughly in line with WebKit’s performance with the JIT turned off.

The theory is that JS JIT compilers don’t actually improve real world performance on the majority of websites. This was apparently per the advice of the authors of Chrome’s and Safari’s JITs.

[shiroiushi]

>or turning into a murderous wacko

A good example of truth being stranger than fiction.