If you don't want to be misinterpreted you might want to limit the amount of sarcasm and hyperbole in your statements and instead focus on clearly defined criticism of these tools.

You can chalk all the issues that you've had to growing pains.

In the last 5 years the web browser has changed immensely. It is now capable of running incredibly complex applications. These kinds of applications need sane module and build systems. Once you're familiar with these tools they do not get in the way even when building simple weekend projects.

The jQuery way of handling DOM manipulation comes from an era where the majority of HTML was being processed on the back-end and Javascript was used for light-weight modification of state.

Using jQuery for building complex interactive web applications is a difficult task because state becomes incredibly hard to reason about.

There are a number of declarative front-end frameworks but I feel that React is the clear winner.

One big issue with Angular and Ember is when it comes to rendering HTML on the server. They're also very slow especially on mobile.

Yeah, the last 2 years have been a mess. We're not out of the clear yet. State and identity management is gearing up to have it's foundations rattled to the core by cryptographic systems that introduce PKI. Because React is just a view layer it'll remain agile enough to work with any sort of upside-down state and data management. Clients keep getting more and more power.

Within the node community the foundations for a decentralized package management system are being built. One that will be just as capable of publishing, loading and building modules from WebRTC as it is from a centralized server.

Yeoman, Bower, Gulp or Grunt don't really solve anything that isn't solved better by other tools.

I urge you to take another look at this stuff. I understand your frustrations but the solution should not be to give up and just go back to jQuery.

No. I’m sorry, but the issues aren’t that simple and you can’t just hand-wave them away like that.

The discovery and maintenance overheads, when libraries get so fine-grained that you wind up spending a lot of time just trying to find decent ones that will be compatible and then keeping an eye on them for updates or replacing them when they are no longer sufficiently supported, can be substantial. This has been an issue with general software development since forever. I sometimes call it the “max problem”: if you need a function to return the maximum of two values and it isn’t part of your language’s standard library, then it is almost certainly going to be faster to implement the one-liner function again on the spot than to search for an existing implementation, but this can easily lead to duplicated code, which is undesirable. The increasing reliance on powerful package managers in front-end web development is just a symptom of these problems.

The downsides of using a framework, meaning code that controls the overall architecture of your system into which you plug your own code as a subservient part, are also real. I’ve written about these on HN before, too[1]. Given that a lot of frameworks implement some sort of plug-in system to try to give back part of the flexibility they inherently take away, it is common to run into the excessive discovery and maintenance overheads I mentioned before on the same projects.

[1] https://news.ycombinator.com/item?id=8070050

In the last 5 years the web browser has changed immensely. It is now capable of running incredibly complex applications.

But they aren’t!

Browsers are now capable of running non-trivial UI applications written in JS, and it’s true that those JS code bases are significantly more complicated than what we worked with a few years ago. However, developers have been building substantial front-end UIs using the likes of Flash or Java to overcome the performance and scalability problems with JS for a long time, and even the largest of these front-ends are only medium-sized projects on the scale of “all software”. There are no magic barriers being discovered in the front-end web development world that haven’t long since been encountered and overcome in other parts of the software industry.

In any case, as I said in my previous post, I am absolutely not suggesting that for these larger JS projects you shouldn’t adopt good tools to automate the development process. Of course you should. I’m just saying that most web sites are nowhere near that scale or complexity, and many don’t need to incur the overheads of adding heavyweight tooling, which is the point I originally objected to. Most sites are not SPAs or CMSes that need to scale up to hundreds or thousands of different types of content.

I think it is also worth keeping in mind that quite a few of the problems these heavy tools solve are only problems in the first place because of other poor tools. As Exhibit A, I cite the use of tools like RequireJS or Browserify to do basic modular design, which is necessary only because JS is a terrible language for developing larger projects and lacks even a basic module system of its own. But again, I’m not disputing that for large web apps by today’s standards a systematic module system is useful, I’m just saying you can go a long way with a one-liner to run Uglify and a one-liner to run SASS, and for many projects that sort of level is all they need.

Using jQuery for building complex interactive web applications is a difficult task because state becomes incredibly hard to reason about.

People keep telling me this, but I have never found it so, and among other things I maintain some substantial code that was built that way and has already successfully outlasted plenty of projects written in trendy web frameworks.

Sure, it’s prohibitively difficult to scale up if you start from the premise that you keep your state embedded in the HTML or the current values of form fields. Toy UIs can get away with this, but it quickly becomes impractical and more structure is needed.

Would I choose to use different tools for a similar project today? Yes, absolutely, there are things we implemented manually a few years ago where it does make sense to use a tried and tested library today.

But there has never been any rule that said you have to rely on bad design and keeping state in odd places, with jQuery or any other library. I was writing web front-end code that did things like separating state from presentation, bundling state changes into a single UI update because rerendering was slow, and implementing what we might now call two-way data binding, long before any of these modern JS frameworks existed. I very much doubt I was the only one. We have a lot of web developers today who have done little if any work on software in other contexts, but these ideas are widespread in other software development contexts and they have been for a very long time.

Likewise, every few years, someone comes along and suggests that a more declarative approach to building UIs is the way forward, and yes, it does have some advantages, but it also has disadvantages. For example, as those using Angular and the like have discovered to their cost, a strategy based on declarative templates doesn’t always scale well when the dominant bottleneck happens when you render changes. This was entirely predictable, I’m afraid, and plenty of people were questioning the Angular hype a year or two back and whether projects locked into using Angular would be difficult to maintain later on. That was before we knew about the whole Angular 2 split, of course.

So, the next logical step is something like React, which is essentially reimplementing a substantial chunk of a web browser on its own terms as an optimisation to overcome the performance limitations of today’s actual web browsers. This is certainly an impressive technical achievement, but will React still be as valuable if a couple of years from now Web Components are ubiquitous and browsers have better logic for avoiding expensive reflows in these kinds of applications? Those both seem like reasonable assumptions, give or take the exact timing.

I urge you to take another look at this stuff. I understand your frustrations but the solution should not be to give up and just go back to jQuery.

As I said before, please don’t read things into my posts that aren’t there. For one thing, I do this for a living, and I keep an eye on this stuff all the time. For another, at no point in this discussion have I suggested that we should just stick with jQuery for everything and not use new tools; in fact, I have explicitly stated otherwise more than once. I challenged one specific post you made, which was a general suggestion that projects should be using tools like Browserify, React and a bunch of NPM-managed modules, even if jQuery was perfectly sufficient to do the necessary job.

Anyway, these posts are getting very long now, and I’ve drifted a long way from my original point so I should probably stop here. Thanks for the discussion.