Alexander Vassbotn Røyne-Helgesen PRO
Lover of life, technologist at heart
The Early Internet set the foundation for everything that followed. What began as academic and government experiments with networking quickly turned into a global communication system. Standards like TCP/IP and HTML created the conditions for the web to flourish, while the invention of browsers and scripting languages gave ordinary people a way to interact with information digitally.
This period also saw the first commercial transactions, proving that the web could be more than just an academic or military tool. Online shopping, payments, and even digital media sales hinted at the massive economic shift that would follow.
Together, these innovations established the internet not only as a new medium of communication, but as a platform for commerce, entertainment, and community building - foundations that still underpin frontend development today.
ARPANET goes live, the precursor to the modern internet.
TCP/IP becomes the standard protocol, enabling a truly connected internet.
Larry Wall created Perl, originally as a text-processing language.
IRC was invented by Jarkko Oikarinen.
Tim Berners-Lee proposes the World Wide Web (WWW) at CERN.
James Gosling created Oak for Sun Microsystems, later named Java.
Tim Berners-Lee creates the first web browser (WorldWideWeb) and the first website.
The first image is uploaded to the web (a parody band photo of CERN staff).
Mosaic browser launches, bringing images inline with text - a huge leap in UX.
CGI was introduced. It was the very first way to make dynamic websites.
Netscape Navigator dominates; Yahoo! and Amazon launch.
First online credit card transaction and first album sold online via encrypted card: Sting's Ten Summoner's Tales.
Pizza Hut introduced the first online pizza ordering.
JavaScript is created by Brendan Eich in 10 days; Netscape 2 ships with it. Originally Mocha → LiveScript → JavaScript.
Coincidentally, Java was called Oak until 1995.
The adult industry widely adopts online credit card payments, helping normalize e-commerce.
Rasmus Lerdorf created "Personal Home Page Tools," later renamed PHP: Hypertext Preprocessor.
The 1.0 version of Internet Explorer is released.
ASP/IIS introduced.
This democratized web publishing. Millions of users experimented with HTML, CSS, and JavaScript - popularizing animated GIFs, guestbooks, counters, and "under construction" banners - while blogging platforms made the social web possible.
GeoCities launches, letting anyone host personal webpages in themed "neighbourhoods."
Tripod starts as a student community and grows into a homepage builder.
Angelfire offers free homepage hosting, later acquired by Lycos.
Xoom provides free unlimited hosting with banner ads, pioneering ad-supported hosting.
FortuneCity emerges with a virtual "city" theme for personal sites.
MSN HomePages and AOL Hometown bring homepage creation to mainstream internet users.
WYSIWYG tools like Microsoft FrontPage and Macromedia Dreamweaver let non-coders build websites with drag-and-drop editors.
These platforms mainstreamed professional web presence without custom coding, shaping user expectations for customizable, performant, and mobile-friendly frontends.
Open-source CMS rise: Drupal, Joomla, Magento.
Shopify launches, democratizing online stores for small businesses.
Squarespace and Wix popularize drag-and-drop site builders for non-developers.
The Styling & Interactivity era transformed the web from static pages into something richer and more engaging... (see original for full nuance). CSS enabled design as its own discipline; browser wars spurred innovation and fragmentation; alternative browsers pushed standards and usability; media and culture experimented heavily online, foreshadowing today's streaming-driven web.
Opera browser launches in Norway; known for speed and innovation (tabbed browsing, pop-up blocking, mouse gestures, integrated search).
CSS is introduced by Håkon Wium Lie, separating content from presentation.
Browser wars between Netscape and Internet Explorer; IE wins dominance by bundling with Windows.
HTML 4.0 standardizes markup.
First online crowdfunding - Marillion, to finance a tour.
First major artist to release an album digitally - David Bowie.
Flash gains traction for animations, video, and interactivity.
Napster popularizes peer-to-peer music sharing.
Sun Microsystems launched JSP.
LAMP Stack rises in popularity.
Adult sites were early adopters of embedded video players (RealPlayer, WMP, QuickTime, later Flash).
Phoenix browser (later Firefox) is released, focusing on speed, standards, and extensions.
Apple Safari is introduced as default for macOS, replacing Internet Explorer for Mac.
Firefox 1.0 launches, gaining market share as an open, standards-compliant IE alternative.
Motion became a core part of UX. With JS + CSS animation and WebGL abstractions, the web evolved from static documents to expressive, immersive interfaces without plugins.
GSAP (GreenSock) becomes a pro-grade JS animation toolkit.
Three.js brings developer-friendly 3D on top of WebGL.
CSS3 animations/transforms replace many Flash-era effects natively.
Forums shaped the culture of the interactive web long before Facebook or Twitter. They normalized persistent identity, threaded discussions, reputation systems, and community moderation - conventions that live on in Reddit, Stack Overflow, and Discourse.
Text-based BBS (Bulletin Board Systems) popular in the 1980s and early 1990s via dial-up.
As the web grew, forums moved online with WWWBoard and early CGI-driven scripts.
UBB.classic, vBulletin, phpBB (2000), and SMF (2003) standardize features like threads, avatars, moderation, themes.
Forums become central hubs (gaming, coding, fandoms) with signatures, PMs, polls, stickies, skins - proto-social networks.
Search engines became the primary gateway to the web, shaping how frontends are built and discovered... Google's dominance pushed standards, semantics, speed, and mobile-first design. AI-driven search continues to influence content structure and delivery.
Advertising changed frontend priorities. Pop-ups and banners degraded UX but fuelled massive growth in the web economy. SEO spam and ad-driven content farms distorted search until algorithm updates (e.g., Google Panda, 2011) forced better practices.
On the positive side, monetization funded free content and tools, but also required frontend developers to balance performance, design, privacy, and revenue. Today, responsive ad units, privacy banners, and consent flows are unavoidable parts of frontend design.
Archie becomes the first search engine, indexing FTP sites.
Early web search tools: ALIWEB, WebCrawler, Lycos, Infoseek, Excite.
Yahoo! Directory launches, initially human-curated.
Ask Jeeves introduces natural language queries.
AltaVista and HotBot push full-text search; niche engines like Astalavista.box.sk index cracks/warez.
Google launches with PageRank, revolutionizing relevance.
SEO emerges: tweaking HTML, metadata, content structure for rankings.
Google AdWords launches, introducing keyword-based advertising
Black-hat practices like keyword stuffing and link farms rise (later penalized).
Monetization drives frontend changes: popup wars, intrusive banners, auto-playing media, and SEO spam (content farms).
Google AdSense follows, letting site owners embed contextual ads, monetizing content at scale.
Bing launches, giving Microsoft a foothold in search.
Mobile-first indexing, Schema.org, and Core Web Vitals elevate performance/accessibility.
The ad ecosystem pushes responsive design (adaptive ad units) and regulations like GDPR/CCPA introduce cookie consent banners.
AI-powered search and voice assistants shift from links to direct answers.
Privacy reshaped the frontend in visible ways. Developers had to implement cookie banners, consent flows, and tracking opt-outs, making privacy UX a standard part of web design.
It also forced technical changes: fewer third-party scripts, stricter data handling, and performance trade-offs. Regulations like GDPR turned privacy from a backend legal issue into a core frontend concern, directly affecting layout, design, and interactivity.
Today, frontend development must balance personalization, analytics, and advertising with compliance, trust, and user control.
Cookies are introduced by Netscape, enabling session state, shopping carts, and later ad tracking.
Third-party cookies fuel the rise of targeted ads, analytics, and retargeting, shaping how frontends load external scripts.
Do Not Track (DNT) is proposed as a browser feature, though adoption is limited.
Growing privacy concerns lead to stricter regulations and browser features:
Chrome announces the phase-out of third-party cookies (ongoing), pushing new standards like Privacy Sandbox.
A decisive shift from documents to applications. AJAX set expectations for instant interactivity; libraries like jQuery smoothed browser differences; platforms like Gmail and YouTube proved the web's app potential; Chrome's V8 raised performance bars and enabled modern frameworks.
Adult industry helped popularize Flash video (FLV); early Adaptive Streaming and DRM experimentation.
P2P platforms arise: Gnutella, Kazaa, BitTorrent.
Internet Explorer 6 launches, notorious for lack of standards support.
Gatas Parlaments releases the first free online release in Norway or in general: "Holdning over underholdning".
Gmail shows power of AJAX for dynamic apps.
Early JS libraries/frameworks emerge: Prototype.js, script.aculo.us, jQuery (2006), Blueprint CSS.
YouTube launches, bringing video mainstream.
Google Chrome launches with the fast V8 JavaScript engine.
Marillion, first band in the world to legally release their album on peer-to-peer (P2P) networks.
Web Workers introduced for background threads.
Node.js created by Ryan Dahl, bringing JavaScript to the server and powering modern tooling.
Though many proprietary approaches faded, they pressured the open web to deliver rich app capabilities, accelerating standards and the shift to component-based frontends.
Silverlight (Microsoft) and Adobe Flex attempt rich, enterprise web apps beyond Flash.
Enterprise platforms (e.g., Salesforce Visualforce) push component-driven UI in business apps.
Web 2.0 emphasized participation, UGC, and interactivity; it birthed "social design." Later Web 3.0 discussions focused on semantics and decentralization - still evolving but influential.
"Web 2.0" describes the shift to interactive, user-driven platforms (AJAX, UGC, blogs, wikis, tagging/sharing).
Blogger launches; LiveJournal gains traction.
WordPress is released, becoming the most popular open-source blogging/CMS platform.
Flickr, Facebook, YouTube, Wikipedia, and Gmail become Web 2.0 archetypes.
"Web 3.0" discussions: linked data, decentralization, blockchain, P2P.
Smartphones forced a rethink of layout, performance, and input models. Responsive design and progressive enhancement became standard; mobile-first shaped frameworks and business strategy.
Apple releases the iPhone with a full browser (Safari) and multitouch.
Google Android launches, accelerating adoption.
Mobile browsers rapidly evolve with modern rendering and full CSS/JS support.
App Store and Google Play shift expectations to app-like experiences.
Ethan Marcotte coins Responsive Web Design (RWD).
Bootstrap popularizes mobile-first design with ready-made components.
Opera Mini extended web reach to feature phones; iPhone and Android reset expectations to touch-first, app-like, and fast.
Opera Mini brings compressed web browsing to feature phones.
iPhone redefines mobile web with a full browser and multitouch UX.
Android accelerates global smartphone adoption.
Component-based frameworks, TypeScript adoption, and GitHub-fueled open source defined modern frontend engineering.
AngularJS popularizes declarative, data-driven UIs.
Backbone.js introduces MVC patterns in the browser.
Knockout.js introduces MVVM-style two-way data binding and observables in the browser, influencing later framework ergonomics.
Bootstrap brings responsive design with ready-made CSS components.
WebRTC standardizes real-time audio, video, and data channels.
WebGL enables hardware-accelerated 2D/3D graphics without plugins.
Web Components offer a framework-agnostic component model, underpinning many design systems and cross-framework integrations.
React introduces component-based UI with a virtual DOM.
Service Workers enable offline caching, background sync, push (PWA foundations).
TypeScript grows as a typed superset enabling safer large-scale apps.
Vue.js and Svelte appear as lighter alternatives.
GitHub becomes central for collaboration, open source, and developer culture.
Task runners and early package managers industrialized frontend workflows, paving the way for bundlers and today's npm-first ecosystem; ESLint set the bar for code quality.
Grunt popularizes JavaScript task automation (minify, concat, watch).
Gulp introduces a faster, streaming-based build pipeline.
Bower becomes the first mainstream frontend package manager (pre-npm dominance).
ESLint launches, setting the standard for JavaScript linting and code quality.
Editors and DevTools evolved from simple text editors and WYSIWYG tools to powerful, extensible environments (VS Code, Chrome DevTools). Online playgrounds made learning/prototyping social and fast.
Plain text editors like Notepad, vi, Emacs, BBEdit used for early coding.
WYSIWYG tools like Microsoft FrontPage and Macromedia Dreamweaver enabled drag-and-drop site creation.
TextMate and Sublime Text gain popularity for speed and plugins.
Firebug launches, introducing live DOM/CSS/JS debugging in the browser.
Chrome DevTools becomes a game-changer with profiling, network inspection, responsive testing.
JSFiddle launches as an online playground for HTML/CSS/JS.
WebStorm offers a professional IDE experience tailored to JavaScript/frontend.
CodePen adds a social layer for sharing and exploring UI concepts.
Atom (GitHub) markets itself as a "hackable" editor; influences modern extensibility.
VS Code releases; becomes the most widely used editor for frontend devs.
StackBlitz introduces a full in-browser dev environment powered by WebAssembly.
Version control transformed collaboration; Git + GitHub made open source mainstream, and npm (plus Yarn/pnpm) sustains the modern JavaScript ecosystem.
Source Code Control System (SCCS). Closed source, free with UNIX
Revision Control System (RCS), open source.
CVS emerges as an early widely adopted version control system.
Subversion (SVN) released as a replacement for CVS.
Git created by Linus Torvalds, introducing distributed version control.
Mercurial (Hg) released as a simpler alternative, used by Mozilla/Python before migrations to Git.
GitHub launches with social features (PRs, issues, stars).
npm released, creating a central registry for JavaScript packages.
Testing frameworks professionalized frontend development - unit, integration, and E2E testing enabling reliable continuous delivery.
QUnit (jQuery team) introduces unit testing for browser JS.
Jasmine and Mocha popularize BDD/TDD patterns.
Jest becomes the de-facto test runner for React and beyond.
Cypress streamlines end-to-end testing; Selenium remains a cross-browser staple.
ECMAScript standardization evolved JavaScript into a robust general-purpose language; HTML as a living standard accelerated delivery of modern web APIs.
ECMAScript 3 formalizes core JavaScript features.
ES5 adds JSON, strict mode, getters/setters.
ES6 (ES2015) introduces classes, modules, arrow functions, promises, let/const.
Annual updates add async/await, import/export, optional chaining, Intl, etc.
W3C/WHATWG split leads to HTML5 as a living standard.
Frontend design matured from table layouts to responsive, systematized design with tokens and components; tools like Figma bridged design and development.
Table-based layouts and spacer GIFs used before CSS matured.
CSS3 adds animations, rounded corners, gradients, shadows.
Responsive Web Design (RWD) coined by Ethan Marcotte.
Flat design (Metro, iOS7) shifts aesthetics toward minimalism and clarity.
Design Systems emerge: Material, Lightning, Carbon with reusable tokens and components.
Sketch, Figma, Adobe XD integrate design and development workflows.
CSS-in-JS began with dynamic, runtime styling co-located with components, then evolved toward compile-time extraction and SSR/SSG for performance and determinism—echoing server-first eras. Token-driven systems and static extraction (e.g., Panda CSS) bridge DX with predictable CSS output.
CSS Modules popularize locally-scoped class names and build-time composition, reducing global CSS collisions.
styled-components brings CSS-in-JS with tagged template literals and runtime styling co-located with React components.
Emotion offers high-performance CSS-in-JS with strong DX and theming; widely adopted across React apps.
Linaria pioneers zero-runtime CSS-in-JS via compile-time extraction, cutting client-side style cost.
Next.js mainstreams SSR/SSG in React, pushing pre-rendered HTML and critical CSS—an echo of server-first "PHP-days".
Stitches focuses on design tokens, atomic CSS output, and runtime performance with partial static extraction.
vanilla-extract delivers type-safe, compile-time CSS with CSS Variables; no client runtime.
Panda CSS (from the Chakra team) adopts static extraction + design tokens/recipes, marrying utility ergonomics with predictable, tree-shakeable CSS.
React Server Components (RSC) and modern SSR pipelines reduce client JS and runtime styling costs, accelerating shift to compiled styles.
DevOps, CI/CD, cloud, and bundlers brought operational discipline and performance focus, blurring lines between frontend and backend while enabling globally distributed architectures.
Rise of DevOps and CI/CD (Jenkins, Travis CI, GitHub Actions).
Cloud platforms and Netlify/Vercel simplify frontend deployment.
Bundlers/compilers: Webpack, Babel, Parcel, Rollup.
WebAssembly (Wasm) released for near-native performance in the browser.
Jamstack, SSGs like Gatsby, Next.js, Nuxt.js flourish.
Accessibility standards made inclusivity a requirement; performance metrics ensured focus on speed and UX - especially on mobile.
Section 508 amended, requiring accessibility for U.S. federal agencies.
WCAG 1.0 published as the first international web accessibility standard.
WAI-ARIA specs begin, improving accessibility semantics.
Accessibility becomes core in frameworks/design systems with ARIA and contrast tooling.
YSlow and PageSpeed Insights introduce performance best practices.
Google Lighthouse and Core Web Vitals provide measurable UX metrics.
APIs turned the frontend into a client of complex distributed systems; REST/JSON made integration universal; GraphQL improved precision.
REST APIs replace SOAP/XML-heavy approaches.
JSON becomes the lightweight data format of choice.
GraphQL released, offering flexible queries.
Frontends consume microservices and edge APIs for real-time, global apps.
A counter-trend to SPA-heavy stacks: send HTML fragments from the server and progressively enhance at the edge. This reduces client JS, improves TTI, and revisits hypermedia principles with modern ergonomics.
Turbolinks (Rails) speeds navigation by swapping HTML over the wire without full page reloads.
Stimulus introduces lightweight controllers for progressive enhancement, complementing server-rendered HTML.
Phoenix LiveView streams server-rendered HTML over websockets for interactive apps without heavy client JS.
Hotwire (Turbo + Stimulus) formalizes the HTML-over-the-wire approach for Rails and beyond.
htmx enables hypermedia-driven UIs with HTML attributes—requesting, swapping, and animating HTML fragments with minimal JS.
Laravel Livewire brings server-driven component interactivity to PHP, echoing classic server-first patterns with modern DX.
Realtime APIs shifted frontends from request/response to live, stateful experiences across chat, collaboration, trading, and multiplayer.
WebSockets standardize persistent, bidirectional communication.
WebRTC enables real-time audio, video, and P2P data channels.
Realtime experiences go mainstream in web apps.
Web skills now target desktop and mobile via Electron and React Native; PWAs show the web can compete with native app capabilities.
PhoneGap / Apache Cordova enable web apps inside native wrappers on iOS/Android.
Electron allows packaging web apps as cross-platform desktop applications.
React Native brings React's component model to mobile with native APIs.
Progressive Web Apps (PWAs) emerge with installability and offline support.
Capacitor, Expo, and Tauri continue to blur lines between web, mobile, and desktop.
Frontend evolved into a specialized engineering discipline responsible for performance, accessibility, and product quality - far beyond markup and styling.
Today, frontend engineering integrates frameworks, TypeScript, utility-first CSS, WebAssembly, AI assistants, DevOps, micro frontends, and design systems - driving UX and business value.
By Alexander Vassbotn Røyne-Helgesen