“Why is it that people keep inventing so-called “revolutionary new ways” of doing the same old thing? And they do that by adding more and more unnecessary complexity on top of existing technologies.” ⤴️
“requires about 3 times as much electrical power even though you’re only serving text and perhaps a few images.” ⤴️
“Why in the world has this idiotic trend of abstracting everything away by layers upon layers of unimpressive complexity gained such a strong foothold in the industry?” ⤴️
“It is irresponsible to keep throwing more hardware at a problem that doesn’t need to exist in the first place.” ⤴️
“Everyone is experiencing the pain of using the web daily.” ⤴️
“Simple websites that contain nothing more that text and images takes forever to load, they only work in a few major browsers, and they are suffering from a flood of almost daily security issues. Turn off JavaScript and nothing gets displayed even though no is JavaScript is needed for anything.” ⤴️
“yes you can get something running quickly, but they always pay a heavy price in the long run.” ⤴️
“because friends and family complain about how bad this or that website has become, but mainly because I, as an independent contractor, am faced with clients who, as a result of this mess, have suffered greatly at the hands of so-called modern web developers.” ⤴️
""Modern” web development has standardized in tool stacks which are insanely complicated, far beyond anything that is warranted in most cases. We have forgotten how to make simple things in simple ways.” ⤴️
“At a minimum you need node, npm, webpack, babel, an spa framework, a frontend router, a css transpiler, a css framework, a test runner, a testing functions library, and a bunch of smaller things, and that’s just what is “needed” to build a static website with a bit of interaction. We’re not even talking about the dockerized insanity that happens as soon as you want to slide an API under that beast.” ⤴️

The Web Didn't Change; You Did

“framework fatigue. That is, the cognitive overload from not only being told that you’re using the wrong framework but that even if you are using the right one, there’s a new version that adds some brand new programming paradigm.” ⤴️
“Take React and GraphQL for instance. They solved Facebook’s specific problems with respect to their web site and the disproportionate amount of information they glean from their unsuspecting users. Somewhere along the line Facebook devs realised that this tech could be used in much simpler situations and thus open sourced the code.” ⤴️
“Framework fatigue definitely exists. It’s also known as innovation in this particular area of software development. Which is also not a mandatory part of web development.” ⤴️
“Asko Nõmm wrote:

Starting a new project? Make sure to write your project idea down because by the time you are finished setting up the vast boilerplate you have probably forgotten it.” ⤴️
“Dear reader - let me ask you this, and I hope you ask your colleagues the same: what’s stopping you from using exactly method today?. I say: nothing. jQuery is still there. PHP and HTML (though I don’t think I ever saw a time where those were treated as two things rather than one weird mash of the two in a single file) and regular old JavaScript is still there.” ⤴️
“what you learnt in the mid-2000s still works” ⤴️
“Browsers bend over backwards to maintain backward compatibility.” ⤴️
“We are not, however, beholden to complexity.” ⤴️
""We’re using React (or whatever framework) so we can easily hire devs!” Then, devs say, “I gotta learn React so I get hired!"" ⤴️
“framework fatigue. That is, the cognitive overload from not only being told that you’re using the wrong framework but that even if you are using the right one, there’s a new version that adds some brand new programming paradigm.” ⤴️
“Take React and GraphQL for instance. They solved Facebook’s specific problems with respect to their web site and the disproportionate amount of information they glean from their unsuspecting users. Somewhere along the line Facebook devs realised that this tech could be used in much simpler situations and thus open sourced the code.” ⤴️
“Framework fatigue definitely exists. It’s also known as innovation in this particular area of software development. Which is also not a mandatory part of web development.” ⤴️
“Asko Nõmm wrote:

Starting a new project? Make sure to write your project idea down because by the time you are finished setting up the vast boilerplate you have probably forgotten it.” ⤴️
“Dear reader - let me ask you this, and I hope you ask your colleagues the same: what’s stopping you from using exactly method today?. I say: nothing. jQuery is still there. PHP and HTML (though I don’t think I ever saw a time where those were treated as two things rather than one weird mash of the two in a single file) and regular old JavaScript is still there.” ⤴️
“what you learnt in the mid-2000s still works” ⤴️
“Browsers bend over backwards to maintain backward compatibility.” ⤴️
“We are not, however, beholden to complexity.” ⤴️
""We’re using React (or whatever framework) so we can easily hire devs!” Then, devs say, “I gotta learn React so I get hired!"" ⤴️