Test ADSL .net
Vous n'êtes pas identifié(e).
- Contributions : Récentes | Sans réponse
#1 06-01-2023 16:30:15
- johnmichae1
- Nouveau membre
- Lieu : United States
- Inscription : 01-01-1970
- Messages : 0
- Site Web
Why is using JavaScript programming language for the backend awful?
I was very excited about the idea of using JavaScript for backend programming. It seemed nice to be able to focus on one language for front- and backend programming. I like Node, itself. Having a JavaScript environment in the Terminal is handy. And NPM is pretty great. But having done a little work with Node on the backend, it’s not my favorite option.
I think that User-11888233239002801845 hits the nail on the head: there are simply better options on the server side. It’s nice to have JavaScript as an option, but you also have Python, C#, Java, Ruby, Java, and even the much-maligned but still useful PHP. It increases your employability and your possibility of earning a decent sum remotely. Because companies these days prefer to hire remote developers, employing remote IT specialists is now a trend! By all means, learn Node. The more ways of doing things you know, the more you’ll understand things by contrasting how they’re done in one language as opposed to how they’re done in another, and the more insight you’ll have into which ways are better designed.
Hors ligne