Why I’m staying with Node
medium.com
Why I’m staying with Node
1–10 of 46 posts
Re: Why I’m staying with Node
#2I dont find this blogpost very interesting.
The point of TJ's post was that concurrency in Nodejs was hard compared to Go,so was error management.It's not about one using Go or NodeJS,more about the fact that it is harder to build concurrent servers that dont crash on error in NodeJS than in Go.
Furthermore I personally dont rely on anything to OP wrote, so wether he stays or leaves nodejs doesnt matter.
Re: Why I’m staying with Node
#3Is there really any practical examples of sharing code between back-end and front-end? I only see really specific use-cases, such as sharing the logic of a game between the client and the server, since most of the time the back-end serves the content and the front-end displays it.
Re: Why I’m staying with Node
#4So?
I don't think TJ wrote his post just for the sake of complaining or comparing Node with Go. He had a decision, and had to tell the community he was leaving because, you know, a lot of people uses his modules. I rely on a couple of his modules and I liked that he took some time to explain why he'll not be working on them anymore.
This post is no more interesting than blogging "I'll keep drinking my morning coffee.. Just as always."
Re: Why I’m staying with Node
#5> Hiring for Go — I wouldn’t even know where to start.
Ridiculously simple: Set out to hire a good programmer (as opposed to "a Go programmer"), and make it clear in the job description that they're expected to spend the first 6 months learning Go on the job.
You end up demonstrating to employees that you're willing to give them something useful, gain loyalty; AND end up with someone you can be confident is able to learn whatever else your company might need in the future, and writes better code by way of having a focus on programming knowledge, not language knowledge.
Re: Why I’m staying with Node
#6Is there really any practical examples of sharing code between back-end and front-end? I only see really specific use-cases, such as sharing the logic of a game between the client and the server, since most of the time the back-end serves the content and the front-end displays it.
This is the weakest argument for the use of nodejs in my opinion.
But I can imagine people sharing models and validation code in an AJAX heavy app.
Re: Why I’m staying with Node
#7"And for that matter, I guess that makes Java, German."
Well, now I feel offended.
Re: Why I’m staying with Node
#8"And for that matter, I guess that makes Java, German." Well, now I feel offended.
Java should be Indonesian if you really think about it
Re: Why I’m staying with Node
#9> Hiring for Go — I wouldn’t even know where to start. Ridiculously simple: Set out to hire a good programmer (as opposed to "a Go programmer"), and make it clear in the job description that they're expected to spend the first 6 months learning Go on the job. You end up demonstrating to employees that you're willing to give them something useful, gain loyalty; AND end up with someone you can be confident is able to l…
I haven't seen this type of hiring since the .com bubble days.
Nowadays either one has the right keywords on the CV or good luck.
Re: Why I’m staying with Node
#10> Hiring for Go — I wouldn’t even know where to start. Ridiculously simple: Set out to hire a good programmer (as opposed to "a Go programmer"), and make it clear in the job description that they're expected to spend the first 6 months learning Go on the job. You end up demonstrating to employees that you're willing to give them something useful, gain loyalty; AND end up with someone you can be confident is able to l…
How to train a new employee on Go:
Day 1: complete the tour - http://tour.golang.org/
and read "How to Write Go Code" http://golang.org/doc/code.html
Day 2-3: read Effective Go - http://golang.org/doc/effective_go.html
Take a whole week, if you feel it is necessary.