Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I would say it depends.
Are you going to build complex sites or very high performance, take look at go.
If you are doing simpler sites or do not need extreme performance node should do just fine and in the short run node will give more results, all relearning takes time.
And node is still good enough for pretty large sites unless your doing something very heavy.
But for a longer perspective I believe in looking into other platforms to broaden your knowledge, you will have use for it even if staying on node. -
@Voxera very well said. I have little knowledge of Go, and would not consider Node for server side unless it was absolutely necessary, but I really dig the tools and environment for Node
Guys .... What you say about this when YOUR SENIOR do this....
Curious what you guys think about the creator of Node.js saying that he does not think Node is the best tool for servers and that Go is a much better option.
For me at least, I think it is great that people like him become aware of the shortcommings of the technology they devised, but wonder if it is such a good move to say such things (even tho apparently he is not the head of the Node.js project anymore)
I have always been fascinated by Node and the whole JS ecosystem. I think it did wonders for JS developers and it pushed the whole JS experience to a whole new level, but I am also aware of the shortcommings of it just as I am of the other environments that I use.
So, what do you guys think about his statements? Would you consider investing time in Go as a Node developer? Do you think that it will be possible to do a switch or would you rather stay in and advance the state ot Node development?
rant
asking for points of view
just curious