re: Hey, thank you for your advices! I think I like programming, really, but I don't know, i'm going to the gym 4 times per week and the other days I'...

I agree with Perry, about the passion. I always find something interesting to do or at least to read about.

As for JS, I've avoided it until now (59 y/o and counting... being a programmer since I was 20).

The approach I took with JS is to use it as a compilation target and focus on Typescript instead. I read so many praises about the language, so I started learning it. It's amazing.

A few more points on JS:

  • Modern JS is fricking fast, sometimes even more so than compiled C++
  • Node.js and npm (i.e. like PHP and Composer) are such a great, complete platform. I guess you won't miss a thing from Composer).
  • JS is "the new assembler". And typed arrays gives the language stellar performance, there's even a CPU emulator running Linux, right on your browser tab.

Ok calling JavaScript "fricking fast" or "the new assembler" is simply dishonest and I can't not call you out on this.

Yes, JavaScript is a lot faster than it used to be. Yes, you can do many neat things with it. And yes it is definitely fast enough for a lot of common uses.

However many things are NOT that fast in JavaScript and the single-threaded nature prevents JavaScript from solving a lot of performance problems easily. Additionally MANY languages are much faster than JavaScript and are much more suitable for writing performance critical software.

In my experience for most common use-cases nowadays the performance limitations come from I/O, network, and other such things and the absolute performance of the language (as long as it's fast enough) does not matter much. This means you can write perfectly fine programs in JavaScript, Python, Go, as well as Java (and others) and mostly personal preference and the fit of e.g. various frameworks and libraries available for your needs matters much more than pure performance in benchmarks.

code of conduct - report abuse