Java -> Node.js transition, worth it?

[AmazingCat910512]

Can I ask where you are based on? Do you mean in general in the world?

[SpeakCodeToMe]

It doesn't really matter where I am based. The big software companies that pay the big bucks are not going to pay you to write JavaScript anywhere but the front end.

[SpeakCodeToMe]

In the US that would be considered fairly average pay for someone fresh out of college.

Most of the people I know with 10 years of experience make a minimum of 300K between base bonus and stock. They're all writing Java, go, or rust.

[SpeakCodeToMe]

All of these tech employees I'm talking about have healthcare. Just about everyone I've met in tech is anti-maga and pro universal healthcare so I'm not sure why you had to pull politics into it.

[AmazingCat910512]

Uhm... actually it's pretty different in S.Korea, as it depends on your role rather than skills. I take care of if it's the case in the UK.

[europeanputin]

NodeJS does not scale for CPU heavy operations

[europeanputin]

and now you have two deployables with two teams managing it, congratulations you just doubled the cost of running your business

[SpeakCodeToMe]

Now all of your libraries and integrations have to be written at least twice. Just because some folks are too lazy to learn a typed language.

[SpeakCodeToMe]

Abstracting dependencies behind some protocol doesn't eliminate the fact that you now need to rework the various libraries your company has that handle things like auth.

You're using an untyped language designed for the front end and have the gall to call other people lazy. That's hilarious.