Modern web development. How did we come to this?

The modern world of web development has become one big crutch. Moreover, a crutch, which, in order to somehow work, needs a couple more thousand crutches glued with adhesive tape.

Crutches await us everywhere: starting from server headers designed to ensure application security (CSP), headers that provide cross-origin resource sharing, and ending with build tools.

Solving one problem, we create a couple of new ones and they already rush like an avalanche, demolishing everything in its path. If in doubt, you can see the statistics of questions on stackoverflow, where the javascript is already the undisputed leader.

Are there people in the audience who, for example, tried to write a project in Angular 2 and build it using Webpack? This is hell.

For example, you decide to use the ES6 syntax, but Typescript says that it cannot use your Map as an array until you set target = es6 (more precisely, it tells you Google). Expose, but now Typescript swears on duplicate ads in es6-shim.d.ts. Remove these ads, but now uglify swears that he can’t understand what let is (more precisely, it tells Google, because there is something inaudible in the error and not related to let at all) ... Screw the babel. But now Ulgify has renamed [ngClass] to [ngclass] and Angular swears that he does not know such a property of an element ...

As a result, you get an assembly of 2 MB in size (after minification 760Kb)! And you begin to write a webpack crutch that will delay the loading of some modules until the right moment. Moreover, it is all terribly solved through the regular season.

And this nightmare repeats itself over and over.

The situation with frameworks and libraries is already reminiscent of the modern world of mobile phones. It makes no sense to learn something longer than a week, because after a year it is already morally obsolete.

Grunt, Gulp, Broccoli ...
R.js, Browserify, SystemJS Builder, Webpack ...
Flux, Redux, ... put your own

And this also continues indefinitely. Some projects do not even have time to get out of beta, as they already hopelessly become obsolete or do not take off (Polymer, for example). Some projects appear unclear why and duplicate what is already there (WebRX).

Webpack, as for me, is generally the ideal of crutch building. Thanks at least for collecting many crutches in one place. (The truth is now npm is full of modules with ambiguous names like raw-loader, base64-loader, it was hard to prefix your loaders).

Apparently, writing documentation was no longer fashionable. What for? Openors same. A person can open the source, and there, you see, he will figure it out and copy it.

Only registered users can participate in the survey. Please come in.

Do you think the situation will change in the near future?


Also popular now: