Primary I think is a Django project https://www.youtube.com/watch?v=lx5WQjXLlq8&t=10s

I am straining to hide my lack of being impressed

I understand that if the low salary workers are employed via a subcontractor, that workers salary is irrelevant for the average salary you are paying.

Actually is also a false friend in Spanish.

For non English speakers, English. For English speakers, learn at least a second language.

One possible solution with a bit of little work is to write layouts with grid. And then, as a fallback, query a no supported grid feature for IE 11 and write that layout in flexbox.

The layout in grid can be responsive. But the layout in flexbox for IE 11 only will be mobile, if it's mobile it will work in any display.

> - you can have static methods

IMO create a class in Javascript and adding a static method is the opposite of simplify things.

The simple way of doing it would be create a function in a module.

For me the use of static methods in languages like Java is a workaround. But it Javascript that workarount is not necessary.

This mirrored repo https://github.com/apache/maven says that the last commit was five days ago. So would not say that is no longer maintained.

I wouldn't go so far as rbt to say that it's unmaintained, but the development attitude is that of maintenance (features like Java 9 modules compatibility) rather than active development. Gradle has improved by leaps and bounds very quickly; the Gradle build daemon makes build tasks feel much quicker and powerful in day-to-day practice, and is clearly now the preferred tool for new projects.

I only use Gradle on Android projects, because we are forced to by Google.

Everywhere else all our Java projects are Maven based and there are no plans to change it.

Look, if you have a lot of pre-existing Maven builds then of course the story gets more complicated. Large enterprises usually have higher priorities than spending large $X on any kind of migration that's not absolutely necessary, including the costs for retraining dozens or hundreds or thousands of developers to use a new build tool and to overhaul tooling that was built on top of the old solution (e.g. deployment scripts invoking mvn deploy and Maven reports), and can often result in choosing options that are technically worse but organizationally better.

What I mean is when you have the freedom to choose a new technology stack because it's a new project - because a lot of companies still won't give you that freedom even with new projects.

Unless you have some objection against Gradle itself?

Surely.

Maven doesn't require 2 GB, a SSD, a background daemon and different dependency commands to be fast.

Also Maven has never been four years in a row subject of build performance at multiple conferences.

For those that don't suffer from XML allergy, Maven is quite alright, IDEs can provide completions that actually make sense and nice graphical tooling for dependency management.

But they can not decide the price of their service. I think this is a great difference.

I would call it 'just works as you spected' contrary to 'just works as someone else spected'. Neither is good or bad, it depends of what are you looking for.

For the same reason a lot of people says that the use node as backend. Because they must use javascript in the frontend they use it in the backend. If one is using php as a language for a project and that project has related commands and with php your are capable of doing, why not?