1,143 karma · joined August 4, 2013
Most in this trade work on a layer near the top (closer to the end-user) coding just a bit of logic and gluing together building blocks in order to provide a solution to real needs.
The trade seems trivial because the hard work (millions of lines of code) is already done. And that right there is the brilliance of the whole thing: take any layer apart and it will be done of smaller pieces which have been debugged to the point of being practically flawless (yes, we still find bugs in code that is out there for years, but that is the exception not the rule).
On the other hand, if you want accountability and guaranteed results, you have them already: formal software development processes used by the likes of NASA or the military.
You can wait a couple of decades to realize, or accept, that social media is bad for your health and everyone else around you.
Or you can quit now.
React makes sense for FB's bloated, complex web app. Your CRUD app will do fine with far simpler dev tools. Even vanilla JS does the job in most cases.
99% developer feels compelled to learn and adopt what is trendy because that is what the client/market/boss demands; but it is you the 'engineer' who has to tell the client/boss how that bridge is to be built. When was the last time you went to a doctor and said: hey doc I have this, give me that medicine.
Not sure how these percentages will move if adjusted for purchasing power. Maybe half the world isn't poor anymore? Or maybe 90% still is?
Convince me that I am wrong.
Is this the endgame for all social nets?
So, is it bs? No, it is not. If you are a developer, you can go now and build a dapp (a web3 application or distributed app).
So far so good, but:
A simple dapp will cost cents to host/run (even better: will cost only once!) but, can it scale? How easy/cheap would be to run a big, very big, social net? An online store such as Amazon? Uber?
No "password-reset" mechanism. That just sucks.
Keeping the current web safe for your uncle is a pain, yes, that uncle that clicks on every link sent from the rich African prince. Imagine keeping it safe once you help him install a chrome-ext crypto wallet so he can login and consume content from a dapp social net?
It is not really decentralized: you public facing dapp cannot be directly served from the nodes of a blockchain, you need a gateway, that is a centralized web server (good luck making SSL work for your registered domain!).
It would take many years for businesses to migrate/adopt web 3.0 standards. We are barely finishing moving tech to "online versions" from traditional client-server apps.
Miners are businesses, running nodes costs money, they ought to make more of what they spend otherwise they will just disconnect the node. Your data/code may be distributed but its persistence/availability depends on the economic success of whatever project you choose to trust. Early adopters of web 2.0 server-less apps experienced this first hand when they had to port their projects from Parse to something else when FB bought it and shut it down.
Professional miners are needed. You are not going to build your banking dapp on the spare capacities of our laptop's hard drives and CPUs, or are you? Might as well trust the engineers at Google or AWS who have it already figured out and are charging reasonably for it, no?
In sum: web 3.0 tech is here, it is interesting, but it is not a hammer for every nail.
Eventhough we had these tools I still preferred to code from scratch, simply I could not stand the output code, it was messy, full of unused stuff, excesively commented, etc.
I like to look under the hood and understand what's going on. This is not for me.
greatastic greatas·tic of the greatest quality; Great. "the greatastic works of the Socratic philosopher"