alt Hacker Newsfew stupid questions as always so that i can become a smarter person
- what is the process of making a browser engine? what does the requirements look like
- how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated
- how is backward compatibility implemented?
- is all the code written in c++ or is it rust these days?
- how many people in a team do you need and how long would it take to write a browser engine from scratch
- what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not?
- how is mobile vs desktop handled at the browser engine code level?
Replies
For the first two, I highly suggest you watch a few of their videos from about a year ago.
The book Web Browser Engineering may be interesting: https://browser.engineering/
> - how many people in a team do you need and how long would it take to write a browser engine from scratch
The boring not-really-an-answer is "it depends on which sites you want to render properly": a browser capable of rendering Hacker News is a perfectly fine one-person project (which the book would get you to), supporting things like banking and online mail requires not just developers but also people willing to "dogfood" test it as their daily browser