What Is Web3: The Evolution of the Internet You Use Every Day

I remember my first internet experience. 2004, an internet cafe in Palembang. Opened Yahoo, read news, sent email. That was it. No comments, no likes, no sharing. The internet was like a digital newspaper - you just read.

Then came Facebook, Twitter, YouTube, Instagram. You could comment, like, share, upload. The internet became interactive. You weren't just a reader - you became a contributor. But your data became theirs. Every like, every share, every photo you uploaded - became their asset.

Now there's a third phase: Web3. Where you can not only read (Web1) and write (Web2), but also own your data. But is Web2 really that bad? And is Web3 as good as the hype claims? That's what I want to explore - from the perspective of a developer who's watched this evolution up close.

---

Web1: The Read-Only Web (1991-2004)

Web1 was the prehistoric internet. Static HTML pages, simple CSS, GIF images that took 2 minutes to load. Only people who understood HTML could publish. Everyone else? Just read.

Web1 characteristics:
• Static - content doesn't change without manual editing
• Read-only - you read, done. No like buttons, no comment sections
• Self-hosted - your site, your files, your server
• Technically decentralized - no single company controlled the web. But also not practical.

As a developer, Web1 was: create an HTML file, upload via FTP, done. No frameworks, no databases, no APIs. Simple, but primitive.

Web1's downside: only technical people could publish. Want a website? Learn HTML. Want to comment? You couldn't. The internet was for consumption, not participation.

---

Web2: The Read-Write Web (2004-present)

Web2 was born from a need: "how can ordinary people publish content without learning HTML?"

The answer: platforms. Facebook, Twitter, YouTube, Medium, Instagram. Just create an account, upload, publish. No coding needed. Everything handled by the platform.

Web2 characteristics:
• Interactive - comment, like, share, upload
• Platform-centric - everything in one place (Facebook, Twitter, YouTube)
• Data as product - you write it, you upload it, but the platform owns it
• Centralized - Facebook owns the servers, rules, algorithm. You're just renting space.

// Web2 technically - classic client-server
// Frontend (React) → API (Express) → Database (Postgres)
// All data on our server. User just uses it.
app.get('/posts', async (req, res) => {
const posts = await db.query('SELECT * FROM posts')
res.json(posts)
// This data belongs to us (the platform), not the author
})

As a developer, Web2 was a golden age. Frontend, backend, database, API - all became mainstream. Web developer became a legitimate profession.

But there was a price:
• Your data = their product. Facebook knows what you like, what you hate, who your partner is. Sold to advertisers.
• No control. One day Facebook can ban your account. All your posts, photos, connections - gone.
• Algorithm controls what you see. You don't choose your content. The algorithm does.

Nothing "wrong" with Web2. Facebook is free, Twitter is free. They need to make money - and money comes from your data. That's the deal.

But many started realizing: "why does the data I generate belong to them?"

---

Web3: The Read-Write-Own Web (2014-present)

Web3 was born from one simple idea: what if you owned your own data?

The answer: blockchain. Your data isn't stored on Facebook's server. It's stored on a decentralized blockchain. You hold the private key. You control it. No single company can ban you, no single server can cut off your access.

Web3 characteristics:
• Ownership - you own your data via private key (wallet)
• Decentralized - no single server. Data replicated across thousands of nodes
• Trustless - you don't need to trust the platform. You trust the code (smart contract)
• Permissionless - no permission needed to access

// Web3 technically - smart contract on blockchain
contract SocialMedia {
struct Post {
address author;
string content;
uint256 timestamp;
}

Post[] public posts;

function createPost(string memory _content) public {
posts.push( Post(msg.sender, _content, block.timestamp) );
// This data belongs to the user (msg.sender), not the platform
// No one can delete or censor it
// As long as the blockchain runs, the data is safe
}
}

Fundamental difference: in Web2, msg.sender (the user making the request) means "who's logged in on our server." In Web3, msg.sender is the user's wallet address - an identity they control themselves.

---

The Philosophy Behind Web3

Web3 isn't just about technology. There's a deeper philosophy:

1. Data decentralization. Data shouldn't be monopolized by one entity. In Web2, your data lives on Facebook's servers. Facebook can shut down those servers, alter that data, censor that content. In Web3, data lives across thousands of nodes. No single point of failure.

2. Self-sovereign identity. You don't need to "Login with Facebook" or "Login with Google." You log in with your wallet - MetaMask, Phantom, WalletConnect. Your identity doesn't depend on any platform.

// Web2: login via platform
const user = await auth.loginWithGoogle()
// Platform owns your data

// Web3: login via wallet
const address = await provider.send('eth_requestAccounts', [])
// User owns their own identity

3. Trustless execution. You don't need to trust "Facebook will host your data well." You trust a smart contract - code that's transparent, immutable, and auditable by anyone.

4. Token economics. Web3 has incentive models. People who contribute to the network earn tokens. Not "you create free content, platform sells ads." But "you create content, you earn tokens."

These are compelling philosophies. But in reality, the implementation isn't smooth.

---

Critical View: Web3 Today

I don't want to write a pro-Web3 article without criticism. There are serious problems:

1. Decentralization is a spectrum. Many claim "Web3 is decentralized" but the reality: 60% of Ethereum nodes run on AWS. One VPS can be taken down, and part of the network is affected. Also, who controls the protocol? The core Ethereum Foundation team. Not "fully decentralized."

2. UX is still terrible. You need to install MetaMask, save a seed phrase, pay gas fees for every transaction. Compare to Web2: click "Login with Google" - 3 seconds, ready to use. Web3: takes 3 steps and $5 gas fee before you can interact.

3. Most of it is speculation, not utility. 90% of capital in Web3 is for trading, not for real applications. NFT profile pictures worth $100K with no utility? That's speculation. Not Web3.

4. Scams are rampant. Rug pulls, wallet phishing, smart contract exploits - happening weekly. In 2024, over $10 billion was lost from DeFi exploits. About $200 million per month.

As I wrote in previous articles: Web3 isn't about the price of crypto. Web3 is about the philosophy of ownership. But the reality right now is still mostly the speculation layer, not the utility layer.

---

Web1 vs Web2 vs Web3: Comparison

| Aspect | Web1 | Web2 | Web3 |
|---|---|---|---|
| User role | Read only | Read + write | Read + write + own |
| Data | Static HTML files | Platform database | Blockchain + wallet |
| Identity | Anonymous | Platform login | Private key / wallet |
| Control | Your own server | The platform | Smart contract |
| UX | Poor (manual HTML) | Good (platform) | Poor (gas fees, seed phrase) |
| Scalability | Poor | Good | Improving (L2, sharding) |
| Who profits | Hosting provider | Platform (FB, Google) | User (theoretically) |
| Examples | Geocities, Yahoo | Facebook, Twitter | Ethereum, IPFS, Lens |

---

Web3 From a Developer's Perspective

Technically, Web3 is interesting. Not about crypto hype, but about new ways to manage data and identity.

As a developer, you should know:
• Smart contracts - code that runs on blockchain, immutable, transparent
• Wallets - how users authenticate without passwords, using private keys
• IPFS - decentralized file storage, replacing CDNs
• L2 - Layer 2 scalability, making transactions cheap

But don't forget:
• Servers still exist. You need a backend for indexing, caching, APIs. Full on-chain is rarely feasible.
• Gas fees are expensive. Every transaction costs money. For a social app with thousands of posts, fees are not feasible on L1.
• UX is still rough. If your target is non-technical users, Web3 isn't ready.

What I see emerging: hybrid stacks (Web2 frontend + Web3 backend). Use Next.js for frontend, wallet for auth, smart contracts for important data, regular database for caching. Pragmatic.

---

Common Misconceptions

"Web3 = Bitcoin." - Bitcoin is a cryptocurrency. Web3 is the concept of a decentralized internet. Bitcoin is one application of Web3 (decentralized money), but not Web3 itself.

"Web3 will replace all of Web2." - No. Web3 won't replace Facebook tomorrow. Web3 offers alternatives for specific use cases: ownership, decentralization, trustless execution. For other use cases (chat, search, email), Web2 is still better.

"Web3 is just NFTs." - NFTs are one Web3 application. But Web3 is broader: DeFi (decentralized finance), DAOs (decentralized organizations), decentralized identity, decentralized storage (IPFS, Filecoin), etc.

"You need to understand blockchain to use Web3." - No. You use Web3 apps without knowing blockchain. Like you use the internet without knowing TCP/IP. But as a developer, you should understand the infrastructure.

---

An Honest Closing

Web3 isn't a revolution that will happen tomorrow. But it's also not a bubble that will disappear next year. Web3 is an evolution. Just like Web1 to Web2 took 10+ years, Web2 to Web3 also takes time.

What's interesting about Web3 isn't the price (Bitcoin at $100K or $10K - irrelevant). What's interesting is the philosophy: how can users own their data. That's a powerful idea, even if the implementation is still far from perfect.

Personally: I'm still wait-and-see. Read whitepapers, explore dapps, learn smart contracts. But I don't invest big. And I don't sell Web3 to others as a "solution to all problems."

If you're a developer curious about Web3: try deploying a smart contract on a testnet (Sepolia, Goerli). Build a simple dapp: wallet connect + read data from a contract. You don't have to be a crypto maxi. But as a developer, you should understand what's happening at the lower layers of the internet - including Web3.

Because Web3 - hype or not - is already changing how we see data, identity, and ownership. And that change is more important than any token price.

---

Sources
• W3C Decentralized Identifiers (DID)
• IPFS Documentation
• Ethereum Documentation