> I try out servo EVERY day

Cool, thanks for helping out! I hope you're helping them by reporting bugs when you find them.

> it will take a long time until this will be stable

Sure, it's a WIP. That's to be expected. Expecting otherwise is unrealistic.

> It's not ACID1, ACID2, ACID3 compliant

https://blog.mozilla.org/research/2014/04/17/another-big-mil...

> and JavaScript feature's

Maybe DOM bindings, but Servo ships with bindings to SpiderMonkey, the JS VM used in Gecko, so all of the Language JavaScript should be there.

> I just think that it should have more people so that the Innovation could be faster

Check out the top story on proggit: https://www.reddit.com/r/programming/comments/3rqqvu/mozilla...

Currently we are not testing against our application always, but I sometime try it out and its working aweful.

also on acid2 i get different results every day/week. sometimes i'm good somtimes not.

Yeah servo gets more support, i still think it takes at least another year (or more) to ship it.

> It's not ACID1, ACID2, ACID3 compliant

Huh? Servo has passed Acid1 and Acid2 for, like, a year now. Servo doesn't pass Acid3, of course (although neither does Firefox anymore!).

I mean, I'm not going to claim that Servo is by any means Web compatible yet, primarily due to a long list of bugs and incompletely-implemented features. In terms of feature checklists, though, there's a lot done.

It's not, passing most of the times.

It's unstable. That doesn't mean thats bad.

And Firefox is passing Acid3. And always did.

I mean ACID1 and ACID2 failures are mostly regression that getting fixed a day after but still its not roughly stable.

> It's not, passing most of the times.

Acid1 and Acid2 are reftests. The CI system ensures they continue to pass on every commit. Commits are not merged if they break the Acid tests.

> And Firefox is passing Acid3. And always did.

No, it didn't always pass it. Acid3 didn't even exist when Firefox first came on the scene.

Firefox scores 99/100 for me.