Hey, it's Irene here 👩💻
Welcome to 2022! We're kicking off the year with a hot topic on everyone's lips.. Web3. In this newsletter edition I'm going to break down the difference between Web2 and Web3 in a way that even your grandmother would understand.
Know someone that would like this newsletter? Share it with your friends by forwarding them this email!
Become more technical without learning to code
Learning how to code is the least effective way to become more technical.
Being technical means having a broad knowledge of available technologies, understanding technical trade-offs, being able to communicate using technical jargon, and understanding the software development process. Taking a coding class won't teach you these skills!
Enroll in the Skiplevel program instead. The Skiplevel Program is combines a community and on-demand video lessons, readings, and hands-on exercises to teach you the fundamental technical software skills and knowledge you need to succeed in tech.. without ever taking a coding class. Preview the curriculum here.
Welcome to a World where Web3 is now a thing
It seems like everyone and their mother has the word Web3 on their lips recently.. so it might be a good idea to have some idea of what it is.
What the heck is Web3?
In every day conversations, Web3 is used as an umbrella term for the blockchain, cryptocurrency, and NFTs.. but Web3 really refers to the next iteration of the world wide web (www) where the internet is "decentralized via blockchains".
I know, I know, that definition doesn't say a whole lot. So to help you understand Web3 better, let's compare it to the current inter-web era: Web2.
What's the difference between Web2 and Web3?
The main difference between Web2 and Web3 comes down to who owns the content (data and apps).
In the Infrastructure & Apps module of the Skiplevel program, we learn about the client and server architecture. The client and server relationship is the basic architecture of Web2 where we (aka the "clients") access data hosted on servers owned by companies (mainly "Big Tech"). In current Web2, we build apps by writing some backend code and deploying it onto a server, usually hosted by cloud computing services like AWS or Google Cloud. The companies that own the apps and/or cloud computing services allow access in exchange for our data and can block access based on internal and/or political governance.
But in Web3, we, the clients, can become shareholders of an app and its data by helping develop and maintain the services. An app built on the Web3 network is called a "dapp" or a decentralized app. In Web3, backend code are contained in a "smart contract", which is an application living on the blockchain. The blockchain is then stored and shared on a peer-to-peer network of computers not owned by any single entity.
You can compare Web3 to Napster back when decentralized peer-to-peer file sharing was popular. Like Napster, Web3 stores and shares a copy of data on many servers within a peer-to-peer network that users can access. This peer-to-peer method completely decentralizes the web since more than one entity owns (has a copy of) an app and its data. This means dapps built on Web3 are not gated behind a single middleman and there are many sources from which to get access to a dapp and its data.
Ok, how does Web3 really affect me versus Web2 today?
Here's a great comparison of real-world consequences from Ethereum:
Will Web3 be the new norm?
While Web3 is gaining popularity, it's still a long ways away from mainstream adoption for many reasons. Here are just a few:
- Energy resources - We simply don't have the energy resources to support blockchain technology on a grand scale. One bitcoin transaction consumes the amount of power the typical American home needs for six weeks.
- Scalability - Transactions are slower on Web3 since data needs to be processed on many computers on the decentralized network instead of just one server. This means you'll see payment transactions happening at slower rates.
- Accessibility - Web3 requires special software and education in order to access its peer-to-peer network. It's lack of integration with modern web browsers means Web3 is inaccessible to most users.
Due to these limitations, you won't see Web2 going away any time soon. The more likely scenario is Web2 and Web3 will exist in parallel and we can access either networks. This means companies won't be entirely pivoting to Web3 though they will likely start building dapp products for Web3.