Remember when building a website meant writing HTML, adding a little JavaScript, connecting your PHP backend, and getting on with your life? Apparently, we've reached a point where even displaying a text box requires a software engineering committee meeting. 😂

Let me explain something that's been bothering me about modern web development. Why has writing a simple website become so unnecessarily complicated?

I'm talking about React, JSX, hooks, components, state management, and all these additional layers people have decided we need just to build an interface.

Sometimes I just want to write the HTML!

When Did HTML Become Something We Needed to Abandon?

Back in the day, you could write:

<input type="text" id="search">

<div id="results"></div>

Then use jQuery to listen for a keyup event, send the search term through AJAX, let PHP query the database, and return the results.

That's it. The browser understands HTML. jQuery handles the interaction. PHP handles the backend. Everybody has a job, and nobody needs a therapy session.

Now, with React, you might need to declare a component, establish state with useState(), create functions to update that state, manage event handlers, and return JSX just to accomplish something that used to take a few lines of code.

And before somebody gets offended, yes, I understand why React exists. It can be useful when you're building large applications with complex interfaces that need to stay synchronized. But not every website is a massive application.

Why Does Everything Need to Be a Component?

One of the things I dislike is the feeling that the developer has to organize the entire application around the framework before even getting to the actual work.

Want to change a value? State.

Want to update the interface? State change.

Want to pass information somewhere? Props.

Want to reuse something? Components.

Meanwhile, I'm sitting here thinking: I could have written the HTML, assigned an ID, grabbed the element with jQuery, and moved on to the next feature.

There's a difference between building an organized application and introducing unnecessary complexity into a simple task.

I'm Not Against New Technology. I'm Against Unnecessary Complexity.

I've been building websites with PHP, MySQL, JavaScript, jQuery, AJAX, and CSS for years. I like knowing exactly what happens when somebody clicks a button, submits a form, or searches a database.

I can write a PHP endpoint, send it a POST request, return the response, and put that response exactly where I want it. I don't need an entire frontend ecosystem to make that happen.

And that's the part people sometimes overlook: frameworks are tools, not mandatory upgrades to every developer's workflow.

The Industry Has a Habit of Making Simple Things Complicated

There's a strange culture in software development where complexity can sometimes be mistaken for sophistication. If a solution has more dependencies, more abstractions, and more configuration, people assume it must be more advanced.

But a good developer should also know how to simplify things.

If I can accomplish the same task with ten readable lines of code instead of fifty lines of framework-specific setup, I'm going to at least question why I need the extra forty lines.

Of course, the right choice depends on the project. React can be excellent for applications that genuinely benefit from its architecture. But if I'm building a basic search box, a form, a dashboard table, or a page that communicates with a PHP backend, I'm perfectly comfortable keeping things simple.

My Philosophy: Let Me Build the Website, Not Fight the Framework.

Technology is supposed to make development easier, not convince developers that they need to learn an entirely new way of thinking every time they want to display a button.

Maybe I'm old-school. Maybe I'm spoiled by being able to write HTML directly and make it work. But there's something beautiful about opening a PHP file, seeing the actual markup, understanding the SQL, and knowing exactly where the response is going.

Not everything needs React. Not everything needs Node. Not everything needs a framework.

Sometimes a little HTML, some jQuery, a PHP script, and a MySQL database are all you need.

If writing a search box requires more effort than building the search engine behind it, maybe it's time to ask whether we're solving problems or just creating new ones. 😂

And yes, I'll continue writing my HTML the way I like it. The framework police can come get me.