A text-mode web browser with AI help, inspired by Lynx, plus TextFirst.css for text-first websites.

0 downloads

dbbasic-textbrowser/IT-JUST-WORKS.md
Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic-textbrowser.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic-textbrowser.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic-textbrowser.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 Add Gateway Architecture documentation 2693936 1 year ago History
IT-JUST-WORKS.md · 6.6 KB · 324 lines

It Just Works™

The Irony of Modern Web Development

The Observation

Basic HTML + Basic CSS = Works on Safari and Firefox

Funny how that works, right?

The Modern Web Promise

"Build once, run anywhere!"*

<small>* Requires:</small>

  • Babel to transpile your JavaScript
  • PostCSS to process your CSS
  • Webpack to bundle everything
  • Polyfills for browser compatibility
  • Testing in 5 browsers
  • "Best viewed in Chrome" disclaimer
  • Build process that takes 30 seconds
  • 500 npm dependencies
  • Node version manager
  • Environment-specific configs

The TextFirst.css Reality

"Write HTML, works everywhere."

Requirements:

  • Text editor
  • Browser

That's it.

The Timeline

1995

<font color="red">Error</font>

✅ Works in Netscape ✅ Works in IE ✅ Works in Mosaic ✅ Works in Lynx

2005

<span class="error">Error</span>

.error { color: red; }

✅ Works in Firefox ✅ Works in Safari ✅ Works in IE6* <small>* With hacks</small>

2015

<div className="error">Error</div>

// Requires: React, Webpack, Babel, PostCSS

⚠️ Works in Chrome ⚠️ Mostly works in Firefox ❌ Broken in IE11 ❌ "Please upgrade your browser"

2025 (Modern)

<Alert severity="error">Error</Alert>

// Requires: React, Material-UI, Emotion, Webpack, Babel

⚠️ Works in Chrome ⚠️ Works in Firefox if you're lucky ❌ Breaks on updates ❌ "This site requires JavaScript" ❌ Bundle size: 500 KB

2025 (TextFirst.css)

<color name="error">Error</color>

✅ Works in Safari ✅ Works in Firefox ✅ Works in Chrome ✅ Works in Edge ✅ Works in text browsers ✅ Works in curl ✅ Works in screen readers ✅ File size: 15 KB

The Questions

Q: Why does basic HTML/CSS work everywhere?

A: Because it's based on standards that browsers implement.

Q: Why do modern frameworks break across browsers?

A: Because they're based on abstractions built on top of standards, compiled by tools, with dependencies that change.

Q: Which is more reliable?

A: The thing that's been working for 30 years.

The Compatibility Matrix

TextFirst.css

BrowserWorks?Notes
Safari✅Perfectly
Firefox✅Perfectly
Chrome✅Perfectly
Edge✅Perfectly
Opera✅Perfectly
Lynx✅Text mode
w3m✅Text mode
curl✅Raw HTML
Screen readers✅Semantic
IE 11✅Probably!
Netscape 4✅Maybe!

Testing required: Open browser, look at page Issues found: Zero

Modern React App

BrowserWorks?Notes
Chrome latest✅Usually
Firefox latest⚠️Sometimes
Safari latest⚠️Sometimes
Safari iOS❌Broken scroll
Edge⚠️Sometimes
Anything else❌"Unsupported"

Testing required: Cross-browser testing suite, BrowserStack subscription Issues found: Constantly

The Build Process Comparison

TextFirst.css

# Build process:
# (There is none)

# Deploy:
cp index.html /var/www/

Time: 1 second Things that can break: 0

Modern Framework

npm install          # 5 minutes, 500 packages
npm run build        # 30 seconds
# Wait for webpack
# Wait for babel
# Wait for terser
# Wait for optimization
# Build complete!

Time: 5 minutes 30 seconds Things that can break:

  • npm version
  • Node version
  • Package conflicts
  • Peer dependency issues
  • Build tool updates
  • Plugin incompatibility
  • Out of memory errors
  • Infinite loop in webpack config

The "Works On My Machine" Problem

Modern Development

Developer: "Works on my machine!"
Browser: Chrome Version 120.0.1234.56
Node: v18.17.0
npm: 9.6.7

User: "Doesn't work for me!"
Browser: Firefox Version 119.0
(Site is broken)

TextFirst.css

Developer: "Works!"
Browser: Any

User: "Works!"
Browser: Any

No "my machine" vs "your machine." Just works.

The Real Kicker

The browsers we target with modern frameworks?

  • They all support HTML
  • They all support CSS
  • They all support the same standards

So why do we need build tools to make it work?

We don't. We chose complexity.

The Test

Try this experiment:

  1. Create a React app:
npx create-react-app my-app
cd my-app
npm start

Time: 5 minutes Files created: 20,000+ node_modules size: 200 MB Browsers: Modern only

  1. Create a TextFirst.css page:
<!DOCTYPE html>
<html>
<head>
  <link rel="stylesheet" href="textfirst.css">
</head>
<body>
  <h1>Hello World</h1>
</body>
</html>

Time: 30 seconds Files created: 2 Total size: 16 KB Browsers: All of them

Which is more impressive?

The one that works everywhere with zero dependencies.

The Wake-Up Call

We've been solving the wrong problem.

We spent years solving:

  • "How do we make frameworks work across browsers?"
  • "How do we optimize bundle sizes?"
  • "How do we speed up build times?"

We should have been asking:

  • "Why do we need frameworks for static content?"
  • "Why did we abandon HTML that just works?"
  • "Why are we making things complicated?"

The TextFirst.css Revelation

Basic HTML + CSS = Works everywhere

It's not funny. It's sad that this is surprising in 2025.

It SHOULD be obvious. It SHOULD be normal.

The fact that "it just works" is remarkable shows how far we've strayed.

The Return to Sanity

1995 Developer: "I write HTML, it works." 2015 Developer: "I configure webpack, babel, postcss, wait for build, test in 5 browsers, fix bugs, deploy, hope it works." 2025 TextFirst Developer: "I write HTML, it works."

We've completed the circle.

But now we know:

  • Responsive design (CSS media queries)
  • Semantic HTML5
  • Accessibility standards
  • Progressive enhancement

We're not going backwards. We're going forwards by taking the good parts and leaving the bad.

The Moral

Simple things that work everywhere will always beat complex things that work sometimes.

Standards > Frameworks HTML > Divs CSS > CSS-in-JS Zero dependencies > 500 dependencies Works everywhere > "Best viewed in Chrome"


It just works. Funny how that works.

P.S. - The Real Test

Want to know if your website is well-built?

  1. Open it in Safari
  2. Open it in Firefox
  3. Open it in a text browser
  4. Turn off JavaScript
  5. Run it through a screen reader

If it works in all of those? You built it right.

If it only works with JavaScript enabled in Chrome? You built a Chrome app, not a website.


"Simplicity is the ultimate sophistication." - Leonardo da Vinci

"Basic HTML and CSS works on Safari and Firefox. Funny." - User discovering TextFirst.css, 2025