Web Technologies 2026 · BiUH
The idea · the history · where it runs · what travels over it
Four questions, in order
| The idea | why the web is not a technology |
| The history | three eras, one question |
| Where it runs | almost everywhere, including offline |
| What travels | file formats, and what they cost |
What this course is actually about
The web is not a technology.
It is a way of delivering something.
One sentence · true since 1991 · still true in 2031
Something you do not own, running on a machine you do not control, reaches a person through an address, over a network you cannot predict, into a surface you did not choose.
Everything difficult in this course is a consequence of this one sentence.
The history, as one question
Where does the work happen,
and who is allowed to publish?
Three eras. Three different answers. Same question.
Three answers, and what actually happened
~1991–2004
Work: on the server. It makes a file.
Publish: you need a server, an FTP client and nerve.
So almost nobody does.
~2004–2015
Work: moves into the browser.
Publish: everyone can — on someone else's land.
Platform, feed, API, attention as a business.
2001 · 2020
"Web 3.0" semantic web — never arrived.
"Web3" blockchain — real, didn't win.
Neither is the third era.
no version number
Mobile as default. Rendering back to server and edge. Frameworks.
And since ~2023: machines as an audience.
Web 1.0 established URL, HTTP, HTML and the address as the unit of sharing — all four are in this room right now.
Show, don't tell
Legible markup. A tiny file. Renders fine thirty years later, on a device its author could not have imagined.
Name one other kind of file
from 1994 you can still open.
That is the durability argument, and it is more persuasive than anything I could claim.
Name some software you used yesterday that is not a website
"Web" stopped meaning "in a browser tab" years ago — and the last one does not even need a server.
Back to tldraw and Anytype for a moment
If it runs with no server
and no connection —
what made it "the web"?
The URL, the rendering engine and HTTP are separable. These apps keep the engine and the formats, and give up the server.
A choice with consequences: your data stays yours and nobody can withdraw the service — but sharing gets harder.
A format is not a preference.
It is a bet about an unpredictable network and an unknown surface.
Which is the delivery model, in its most concrete possible form.
Choosing a format is a real decision
| For… | Use | The rule |
|---|---|---|
| Photographs | WebP | Far smaller than JPEG at the same quality. Never ship a camera original. |
| Logos, icons | SVG | It is text. Scales to any size. CSS can style it. |
| Transparency | PNG / WebP | PNG works and is large. WebP does it smaller. |
| Animation | MP4 | Not GIF. Ten times the size for worse quality. |
| Fonts | WOFF2 | Every font is a request — and text is invisible until it arrives. |
One photo from a phone · the same picture every time
The biggest win is not the format. It is not sending a 4000px image into a 600px box.
Numbers are illustrative — measure the real ones on your own photo.
The one that always surprises
Ten times the size, worse quality, fewer colours.
GIF was designed in 1987 for 256-colour images over a modem. It is a fossil we kept using because it was easy to share.
Take three things from this