Hacker News new | past | comments | ask | show | jobs | submit login

I believe KTHML->WebKit has pretty much illustrated that having standards that allow new implementations to be developed is a good, essential thing.

We'd have been in an interesting, and perhaps worse state if Safari and Chrome were both Gecko based instead of competing therewith.




That's an interesting assumption to make: Just because Safari or Chrome hypothetically used Gecko doesn't mean that competition would've halted. Why couldn't it have been any different from when Chrome used WebKit as its basis and absolutely trounced Safari?


I wouldn't say Chrome WebKit trounced Safari WebKit. The browser surrounding the engine was better. This means little wrt. to the engine.


Why would we be in a worse state if Chrome and Safari were Gecko based?


We'd have one less rendering engine.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: