38
NodeJS vs Go
(lemmy.world)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
If you wanted to do both front and backend development TypeScript + JS/Node would make the most sense, no? I say this as someone who works with and enjoys working with Go almost every day, but there's only so much time to learn new stuff.
I mean, I heard that new software engineers are allowed to work on the frontend first before the backend. So if I learnt JS now, I could master it, which would help me in the long run. Am I wrong?
Entirely depends on your skillset and company. That might be true somewhere, but seems strange.
I do recommend you pick up typescript though. It will forcibly teach you some good habits, expectations, and some more base understanding of what you're actually doing.
Yeah, I was thinking of using TS anyways. I saw some video that showed how weird JS handles stuff when you try to add two things and such. I also want to make it a habit to type everything anyways. By the way, do I have to learn some more stuff if I want to use TS or is it just that it forces you to use types?
There's a bit of fiddling with configuration and using npm, but it's not much overhead. There's plenty of tsconfig settings to customize the process for your need, but most the defaults are quite sane.
I see, then it won't be a problem after I learn JS.
Well, TS is just JS with strong typing and type annotations. It's almost the same language, just adding guard-rails and safety checks that the base language doesn't have.