Ditching Go for Node.js

Re:Ditching Go for Node.js by adamweston on Thursday November 23, 2017 @01:58PM (#15767111)

Node makes the Node-like architecture much easier than it would be in Go, sort of by definition. Also, wouldn't Node's JIT fare much better in the face of dynamic typing than using reflection (interface {}) everywhere?

[ Parent | on HN ]

Re:Ditching Go for Node.js by weberc2 on Thursday November 23, 2017 @09:22PM (#15769063)

No, there's nothing special about it, and I probably shouldn't have used that term because it might convey that it is particular to Node. Event loop, callback based programming is easily implemented in most languages.

[ Parent | on HN ]

Re:Ditching Go for Node.js by Vendan on Thursday November 23, 2017 @02:16PM (#15767217)

interface{} is not reflection, and using both reflection and excessive amounts of interface{} are not a good idea in Go, and frankly, I don't see anything in this code that would require using either

[ Parent | on HN ]

Re:Ditching Go for Node.js by weberc2 on Thursday November 23, 2017 @09:20PM (#15769059)

To be clear, my point is that interface{} is the worst case in Go and the only case in JS.

[ Parent | on HN ]