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

Depends on what you mean by "browsers". Take the V8 JavaScript engine for example, it's used in Chrome but can also run stand-alone (I think node.js uses it).

I'm not involved in this space at all but I would guess that the main problem with writing browsers isn't that they're all obfuscated monoliths, but that the amount of work to create an entire browser composed of solidly interconnected parts is still a huge amount of work, because of exactly what you said, it's almost an operating system, at least when you look like fully featured browsers like Firefox and Chrome.




Bellard’s QuickJS is a good example. It’s 100kb vs V8’s 40mb and for open source purposes plenty fast for a web browser.

We need more QuickJS and libcss and rendering backends, not “browsers”.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: