Search Results
6/26/2025, 8:49:18 AM
> electricity drives millions of semiconductor “valves” (transistors) that switch on (1) or off (0)
> bits (1/0) combine into bytes (8 bits) standardized tables map each byte to a character (e.g. 01101000 “h”)
> when you press “h,” the keyboard’s firmware sends a scancode the OS converts it into byte 104
> the CPU stores that byte in RAM (fast, temporary memory)
> your browser formats those bytes into an HTTP request (a defined web message)
>the network card wraps this request into Ethernet frames and transmits voltage pulses over the cable
>(The internet is a giant web of computers and servers connected by cables, most of which are undersea fiber optic cables running across oceans.)
> the server’s network card receives the frames, extracts the HTTP request, stores your post, then assembles an HTTP response (HTML/CSS)
> that response is sent back in frames, your network card hands the bytes to your browser
> the browser parses the HTML/CSS, builds a render tree of page elements, and instructs the GPU/CPU to light up pixels accordingly
> voilà, your "Help me to understand how 1's and 0's make up everything on the internet please." appears on the screen on the other side of the world
and
>inb4 "what's with the black boxes?" or "you didn't explain shit"
You can only go so deep before you're neck deep in electrical engineering, compilers, and networking protocols. whatever the fuck
> bits (1/0) combine into bytes (8 bits) standardized tables map each byte to a character (e.g. 01101000 “h”)
> when you press “h,” the keyboard’s firmware sends a scancode the OS converts it into byte 104
> the CPU stores that byte in RAM (fast, temporary memory)
> your browser formats those bytes into an HTTP request (a defined web message)
>the network card wraps this request into Ethernet frames and transmits voltage pulses over the cable
>(The internet is a giant web of computers and servers connected by cables, most of which are undersea fiber optic cables running across oceans.)
> the server’s network card receives the frames, extracts the HTTP request, stores your post, then assembles an HTTP response (HTML/CSS)
> that response is sent back in frames, your network card hands the bytes to your browser
> the browser parses the HTML/CSS, builds a render tree of page elements, and instructs the GPU/CPU to light up pixels accordingly
> voilà, your "Help me to understand how 1's and 0's make up everything on the internet please." appears on the screen on the other side of the world
and
>inb4 "what's with the black boxes?" or "you didn't explain shit"
You can only go so deep before you're neck deep in electrical engineering, compilers, and networking protocols. whatever the fuck
Page 1