4 ms·

TJ Holowaychuk, who has written some of the most popular Node.js libraries. Express.js is probably the one most have heard of. He now operates in the Go space i

TJ Holowaychuk, who has written some of the most popular Node.js libraries. Express.js is probably the one most have heard of. He now operates in the Go space in which I presume he also has some influence as well for OP to bother mentioning. I would say that his handiwork in crafting good libraries was a significant reason that Node took off like it did so quickly. This article from 2014 highlights just how many libraries he has written and how good he as at writing them: https://medium.com/@kelas/how-is-tj-holowaychuk-so-insanely-productive-604818b4e9eb https://medium.com/@kelas/how-is-tj-holowaychuk-so-insanely-...

steve_adams_86 6y ago
I don’t hear about his work often anymore, but I always appreciated his insights and how humble he was. Definitely seemed like the kind of person I’d like to work with and learn from. Though I suppose I did indirectly - I dug through his libraries for years out of curiosity and necessity.
agumonkey 6y ago
This might explain the 'we repurposed npm to manage go deployment' articles I saw recently ..
kelas 6y ago
> article [by @kelas is all about] how good he as at writing them funny to see how this is still relevant. i'm sorry to say, but anyone who read this ancient piece at least marginally past tl;dr would know that your conclusion can't be more false (must be due to my poor command of your language, sorry about that.) i originally wrote this text in response to eponymous question on quora, which saw some unexpected gargantuan success with 100k+ views in the first year or something like that. tj said "meow" under that quora answer, and disappeared for good - while i was left exposed to some really agitated tech bloggers who wanted an interview about how did i get so smart to figure out that the entire headless chicken called node community was just brutally duped. no such interviews could be granted, but in wake of the story some people bothered to look for the clues in his gh activity - mostly frequency analysis of "his" commit logs in a galaxy of repos. this is why most tj's repos were promptly republished elsewhere after that. bottomline: the article says that tj was a SCAM, so there's that.

steve_adams_86 6y ago

I don’t hear about his work often anymore, but I always appreciated his insights and how humble he was. Definitely seemed like the kind of person I’d like to work with and learn from. Though I suppose I did indirectly - I dug through his libraries for years out of curiosity and necessity.

agumonkey 6y ago

This might explain the 'we repurposed npm to manage go deployment' articles I saw recently ..

kelas 6y ago

> article [by @kelas is all about] how good he as at writing them funny to see how this is still relevant. i'm sorry to say, but anyone who read this ancient piece at least marginally past tl;dr would know that your conclusion can't be more false (must be due to my poor command of your language, sorry about that.) i originally wrote this text in response to eponymous question on quora, which saw some unexpected gargantuan success with 100k+ views in the first year or something like that. tj said "meow" under that quora answer, and disappeared for good - while i was left exposed to some really agitated tech bloggers who wanted an interview about how did i get so smart to figure out that the entire headless chicken called node community was just brutally duped. no such interviews could be granted, but in wake of the story some people bothered to look for the clues in his gh activity - mostly frequency analysis of "his" commit logs in a galaxy of repos. this is why most tj's repos were promptly republished elsewhere after that. bottomline: the article says that tj was a SCAM, so there's that.