re: The most important lesson that the success of JavaScript has taught us VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION

people who do use nodejs are one the most sophisticated programmers out there.

That is fanboy talk.
NodeJS is crushing nothing.
It is not used in most of the tech companies.

Please know that I saw your comment part questioning my programming capabilities before you erase it.

I doubt your credibility as a programmer as you use typescript when you have es6

I contributed to numerous open source projects among them Hibernate, Chrome, Spring and Maven.
PTAL github.com/pulls?utf8=%E2%9C%93&q=...
But maybe you googled me after posting your comment.
So I think I am entitled give an opinion on the subject.

Whatever the context, we should try to question the hype.

Last week, while every hipster was crying on the roof that Gradle >>> Maven, we discovered that Gradle was not so great.
Gradle support of Java 9 (started in 2016) is still experimental and buggy. By default, Gradle log output give zero information in case of failure. You cannot debug your Gradle script from IntelliJ.

Docker is another type. I think Docker is great, but not being able to start a container as the current user without scripting it is just lame.

I tried node as backend on little projects.
I think node is way behind JVM in the backend land because:

  • The ecosystem is not mature
  • Monitoring/profiling is not mature
  • The single threaded aspect is just an issue more than anything else
  • javascript (can be fixed with TS)
  • if you want to go all async, you can use Vert.x

But I enjoy building node CLI tools. With TS. I use it to build frontends. With TS.

At work, our main soft is a Java project made of 19 Millions lines of code. Can you imagine that with a weak typed langage like Python, Javascript or Ruby? You may answer microservices. But even a microservice have a few thousands lines of code.

IMO, weak typed langage are good for prototyping and other disposable projects.

code of conduct - report abuse