Swear words aside, the guy does have a point. The vast majority of websites does not need to be this complicated.
I hand-coded the website for my aunt (exhibition curator), then went on and coded a static site generator in C# so that she can edit the site content in a text file and just runs a single command window application. The site does not use cookies, JavaScript, plugins, tracking, etc. We have no cookie banner popup, because we don't need it. The response e-mail to the inquiry about what personal data we collect is one sentence: we don't collect any personal data. Loading the biggest site takes 28 milliseconds raw, 780ms with all images. Every day there's 100+ bots trying to exploit WordPress vulnerabilites, but she doesn't have to worry about maintenance, because the whole website is literally nothing but a bunch of HTML, CSS and JPEG files. It's freaking GLORIOUS!
Finally I felt peace when someone said all these. Because now I know I am not alone.
Hell even fucking Markdown does the job like 85% of time
The creator of C++'s personal page is raw dogged HTML I respect that
This brought me back to 20 years ago when I made my own portfolio website with just HTML and written in a Notepad.
The Space Jam website has been untouched since 1996 and still renders exactly as intended.
I LOVE the simplicity of raw HTML, especially for forms. But the opportunities of fresh powerful HTML standards has been ignored because people are doing stuff with thousands of bolt-on frameworks.
i am a designer and i love this guy, it's honestly infuriating how much nonsense we created that overtime makes so many systems borderline unusable. especially with grid support etc if you can't make something look nice and do it simply it's a pure skill issue. and having to support multi-million dollar salesforce implementations that are fucking terrible (which gives the company a fucking $38B revenue) is what hurt me
Made something with plain html, css and a bit of php not that long ago. Doing that reminded me again of how simple most sites should be
Imagine instead of just writing the HTML for the page, having to create an XML template to add to an XML file that then gets parsed by a third party paid-subscription tool that breaks twice a week into some sort of hybrid XML database of sorts that is then published by a second third party tool that ... creates an HTML file.
If you use assembly to make a web page, your assembly got to output HTML, because HTML is what gets send over the network and HTML is what the browser understands. So your assembly is just another static framework, when you could have written the HTML.
Incomprehensibly based
No but its real. I used to fret so much over which UI framework should I use until I realize all I need is just make my own goddamn button
damn i laughed so hard, the writer of the blog cooked every JS using dev (me included) so hard we got out of the oven well done.
Kenobi : Luke, Use the HTML! Luke : But without the framework, I can't even see! How am I supposed code? Kenobi : "Your eyes can deceive you. Don't trust them!" Kenobi : Remember, a Coder can feel the HTML flowing through him. Luke : You mean it controls your actions? Kenobi : Partially, but it also obeys your commands. [ Luke HTML page doesn't load ] Han Solo Coder : okay, hypertext and ancient webpages are no match for a JS Framework at your side, kid. Luke : You don't believe in the HTML, do you? Han Solo Coder : Kid, I've coded from one side of this galaxy to the other. I've seen a lot of strange stuff, but I've never seen anything to make me believe there's one all-powerful HTML controlling everything.
After years of doing web dev with React and the like, the most joy I've found was writing a simple html+css only site for my partner's presentation at the uni. Absolutely zero worries about it breaking.
He forgot to mention that HTML is responsible and accessible out of the box. Headings provide structure to the document that screen readers can interpret, e.g., quickly jumping to relevant sections; and forms can be filled out and submitted with a screen reader. It's the designers and web developers who destroy accessibility. Having a good understanding of the semantics can improve accessibility with proper landmarks, using aria attributes to link descriptive texts and error messages to the elements they describe. But you have a good baseline out of the box.
I love this. I've been a fullstack web programmer since Netscape days. Like 1999. I've gone from html tables with spliced images to rewriting flash into javascript,css and svgs. I've hacked all kinds of wordpress versions to get every clients' silly request working. I've rewritten/moved ASP to PHP and SQL to MYSQL and vice versa. I've done all kinds of CSV circus. I've dealt with all the encoding issues. I always try to pare everything down to the scope of a specific page load. I've used MANY frameworks. They are all shit except for maybe Vues. I like Vues if I have to make some electron-offline version of an online thing for a client. I avoid composer and node.js like the plague. I don't fear AI, but I know many programmers who should...
@nils4677