1. Resource Gathering The browser starts by gathering all the necessary resources, like HTML, CSS, JavaScript, and images from the web. These resources are fetched from the server to start building the webpage. 2. Parse HTML & Create DOM Tree The HTML content is parsed to create a Document Object Model (DOM) tree, which represents the structure of the webpage. Each element in the HTML becomes a node in the DOM tree. 3. Create Render Tree from DOM Tree The browser creates a render tree from the DOM tree. The render tree is a visual representation of the DOM with all the styles applied, ready for layout calculations. 4. Layout The browser determines the exact position and size of each element on the screen based on the render tree. This process is known as layout or reflow, where it calculates where each element will be placed on the screen. 5. Painting Finally, the browser sends everything to the UI backend, which then interacts with the operating system to display the webpage on your monitor. This stage is called painting, where the visual representation of the webpage is rendered on the screen.

LETS GOOOOOOOOOOo your tutorials are so GOATED im so glad u doing good =

You explained this better than my computing teacher 💀

Even though the hardware is very good. But if the software is bad, there is no use of the hardware

recipe is the software and it can be good/bad....and chef is the hardware...if the chef gets a crappy recipe its nothing he could do abt it

our goal is to make processor power more efficient

u can either make the processor strong by giving it more hardware or bring more processors

2:30 I don't know if i agree with him saying web development is not that technically complicated. Sure if you're just building a simple html website or using some website builder tool to host something simple, it's fairly easy. But when it comes to the level of building and managing huge scale websites that millions of people visit everyday, it is just as complicated as rocket science or making microchips.

Very informative video.

THANKS

Dave you need to start making these sort of raw opinionated videos. (opinionated as in a good way)

this is an awesome video, thank you! I’m writing a simple article about what asynchronous programming is, your work helped a lot. things have become clearer!

I'm now an engineer, used to watch your video a lot. Unfortunately, I got put as a hardware test engineer. Not sure if it will lead to anywhere.

Great way of explaining it, thanks for video!

Its like not understanding multiplication when you dont understand addition. Or its luke not understanding how to spell backwards when you dont know how to speck back or wards.

What about if you don't understand what people say or indirectly mean

explosive

you are so good at explaining things！thanks Dave

we call this 7:50 air di£king

Well explained

Im so dumb

nice talking

Thanks Xiang for making this concept super simple.

Failed AWS twice lmao. 2nd one I aced the coding but blew up the behavioural/LEs massively. Interviewer looked really annoyed (since I did so good on the code) and kept drilling on the LEs which I clearly did not prepare for. I think I'm blacklisted now... lmao

What is GCC? I am from mechanical engineering.

Lmao just found this in my old playlist... 3 years of Uni and 5 years working as a SWE later...

Excellent explanation.

Wow…thank you for your life update. You are one of the few KZfaqrs that came back and do a full update on yourself. Like you said, I’m one of the few that used to watch your video about being a software developer long time ago. Much appreciated on your recent update and good luck in your future with your career and your marry life.

you don'e even put likes to the people that comment here and follow you. Is that your personal brand?

You talk about step one - Resource Gathering briefly. Can you explain how Google knows what to gather? It’s obviously not just the entire internet. How does it match the correct html and CSS files?

I just want to thank you for making these videos, especially the ones on soft skills/mindset like dealing with people better than you. It really resonated with me and helped focus my progression as an engineer. The tech scene where I'm from is only 10% the size of whats in America, so it's easy to fall prey to impostor syndrome. I owe a lot of my success to your videos, if I'm ever in NYC area I'll need to buy you a drink as a token of thanks!

a mi me miras a la cara cuando me hablas

Thank you for explaining this so well!

maybe if you can add your opinion about the tech layoffs that are happneing today and how would you approach them if it happened to you? this would really help a lot of people

My answers to the questions. Would love for you to comment your own answers as well. 1. Start with io bound and once they get idle switch to cpu bound to try and do work while the io threads are waiting 2. Just 4 threads - avoiding context switching and using 100% of cpu. 3. If it's a self controlled schedueler like in go - a dependency graph with pre compiled decisions can help. But usually it's the os conteolling the threads so it would probably prioritise according to the threads state and how much idle time the cpu has qhwn the thread is executed. If 50% of the time the thread gets the cpu it just waits for other instrutions like disk/network, it is io bound. 4. When you need to process large amounts of data you can rarely load it all in memory. The solution is usually to read the file in chunks, calculate some of the data, and keep going until all chunks are done. Thw more memory you have, the less chunks you need, ao the the program is faster. If you have less memory, you'll have to load data in more chunks, so the program is usually slower. 5. Take 7 threads to compute the math problem and 1 to write the results of each object. You can't write to a file in parallel anyway, so do what you can fast and then just pass the data to the writing thread. The other 7 threads will be released back to the os when they are done and the writing thread would eventually finish the work last. If you were to use 8 threads to do everyrhing, they would all compete with each other on the shared resource (the disk). Of course modern drives havw the ability to do concurrent writes but that's regardless of the question right now and very tricky to write a program for

I really love your explanation and example.

You explained this topic beautifully, very clear and precise. Thanks Dave.

شكرا Thansk it was very helpful

Understand the foundation!

Great video for the top overview about how browsers works internally. Thanks for the information.

Glad to hear you're doing well! Congrats on the marriage!

may i ask an out of topic content, does a desktop software need a database?

Hey if I were to get a web browser built how can I get it to make money? Because that is my goal. Like from MicroSoft or Google.

Hands down best explanation of static and shared libraries. I much needed this video as I was struggling to understand this concepts.

Hey Dave, glad to hear you're doing well! Your videos were instrumental in helping me learn fundamental computer science, I had never even taken a single CS course in high school and college and your videos helped elucidate so many concepts for me. I'm currently a Software Engineer at Google and I don't know if I would be here without your videos. Hope the married life is treating you well and you're enjoying all that life has to offer, and thank you again!

This video is 7 years old and it aged so well even now

Weak AF

Suckers use Chrome lol. Unless you like each of your actions reported to Google.

thank you for real!

Hello. Thanks for the video. So as I understood sessions are like super cookies, which can store much more info compared with simple cookies?