Why Web3? My Journey with Web3 - Part 1
For those who are new, I am an experienced Software Developer (Backend Engineer) who has decided to pick up and explore a new tech domain, and for this, I have chosen Web3.
Read along as I stumble through this exciting new domain as a beginner and student, familiarizing myself with the various nitty-gritty of this domain and my thoughts and confusions circling the field.
In this article, I explore what Web3 really is and why the need for Web3 arises.
In the end, I state a few problems and concepts I didn’t understand that I hope to explore later. If you have a better understanding, help would be appreciated!
What is Web3
Today, Web3 represents the “next generation” of the internet, set to change how we interact, do transactions, and protect our online identities. But to understand why Web3 is needed let's look at how the web has developed over time.
The Evolution of the Web
Web1 (Read-Only)
Web1, often known as the “information era,” was essentially a read-only web. Back then, websites were static pages primarily designed for sharing information—much like an online library. Users could search for information but had limited interaction with the content or with each other.
Web2 (Read-Write)
The era we know as Web2 introduced the interactive web, where users could not only consume but also create content. This is the “app era,” with platforms like social media, e-commerce, blogs, and streaming services enabling dynamic, two-way interaction. Web2 is the current state of the internet, where people can connect, share, and create—but it comes with certain limitations.
Web3 (Read-Write-Own)
Web3 addresses key limitations of Web2, specifically regarding privacy and ownership of data. In Web2, users often need to create accounts and accept terms of service agreements, which essentially grant permission for platforms to collect, use, and sometimes sell user data. This model of centralized data ownership by a few large entities creates privacy concerns, as data can be monetized or misused.
Web3 is built on decentralization and blockchain technology to counter this centralized control. By shifting to a decentralized architecture, Web3 aims to return control of data to the individual. Here’s how it works:
Blockchain Technology: In Web3, data is distributed across a blockchain, making it secure and resistant to censorship. This shift moves away from a centralized control to a peer-to-peer (P2P) network, allowing users to retain ownership of their data.
Digital Ownership: Blockchain allows digital assets and content to be owned and transferred by individuals in a transparent and secure manner. For instance, cryptocurrencies and NFTs are Web3-native assets that enable unique digital ownership.
Peer-to-Peer Networks: Websites in Web3 are run on a distributed P2P network, involving computers worldwide rather than being hosted on a single server or controlled by one entity.
Tokens and Cryptocurrency: Transactions in Web3 rely on cryptocurrencies, facilitating decentralized finance and asset trading. Popular examples include cryptocurrencies, NFTs, and platforms like Brave, a Web3 browser.
My Personal Thoughts on Web3
Theory vs. Reality: While I understand the theoretical aspects of Web3, I fail to understand how this is practically implemented.
Access Barriers: I don’t see a way to “access web3” applications - from my current research it looks like you need a “Meta Mask Wallet” to do so. (Hopefully I’ll have better understanding in my next article - and will address this)
Decentralized Hosting: How the hosting works on a decentralized network is still a black-box as I don’t really understand (or maybe I am too set in my ways of thinking in a centralized manner) on how the “Dapp” (Decentralized application) can be updated if it is built on the blockchain, which by nature is supposed to be “immutable”
Cost of Interaction (Gas Fees): also have come across the concept of “Gas” which I didn’t understand, but my initial read up shows that a user needs to “pay” to interact with the website, which seems to be A HUGE barrier to entry (if I understood this right)
I hope this article has given you something to think about! And if you do happen to be aware about the solutions of the problems I mention - do reach out, it would be a big help!
Subscribe to my newsletter
Read articles from Yuvraj Singh directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by
Yuvraj Singh
Yuvraj Singh
A Software developer with a passion for building products that users love, with a passion for exploring different technology spaces! Currently exploring: Web3