3 ms·
The best message [0] in the thread: IMHO you must consider nodeJs. [0] https://groups.google.com/forum/#!original/Golang-nuts/_6K8SpMFsTM/TITjtP5jBwAJ https
by 0xmohit 10y ago
The best message [0] in the thread:
IMHO you must consider nodeJs.
[0] https://groups.google.com/forum/#!original/Golang-nuts/_6K8SpMFsTM/TITjtP5jBwAJ https://groups.google.com/forum/#!original/Golang-nuts/_6K8S...
- kodfodrasz 10y agoYea, I also laughed :)
- tracker1 10y agoThere are some things that node is great for... even some automation tasks... not sure that a web scraper is an ideal example... pretty much anything dealing with huge streams isn't a great fit, and getting the back-pressure on streams right in node is sometimes hard. A lot of db's for example may not expose cursors for being able to do a record at a time, so you'll get it shoved in... and before you can process the million records, node will crash. I love node... but it's not always the right fit... dealing with that for something at work now... I'm like if we can break it up through an MQ, awesome, otherwise node will be a very bad fit.
- pitaj 10y agoHoly... ellipsis... Batman...!
- tracker1 10y agoI tend to write conversationally, closely to how I speak. I wouldn't write the same way if this were a white paper, research or other types of instruction. In more casual conversation I will pause to think... Then continue speaking, I do the same when writing online in casual settings. There's also the aspect of typos, or grammatical error that I'm inclined to let slide in one setting and not others. In this setting, I'm less inclined to use leet-speak shortcuts though.