4 ms·

"We chose node.js for a few reasons. The first was, we simply wanted to play with a new technology." Well at least he's honest, but this seems like an exceedin

by ericflo 16y ago

"We chose node.js for a few reasons. The first was, we simply wanted to play with a new technology." Well at least he's honest, but this seems like an exceedingly bad reason to choose a technology stack.

aaronblohowiak 16y ago
Later in the same paragraph: Node.js is architected near perfectly for this situation. (And Proxlet demonstrates amazing throughput on minimal hardware to validate that). That sounds like a good reason to me.
- aaronwhite 16y ago
  Can't wait to share these numbers! Blog post forthcoming in a few weeks.
aaronwhite 16y ago
Chris & I started Proxlet as a side project to scratch an itch and keep our skill-set fresh & do things in new ways. A great & rare opportunity to choose wild new tech stacks!
techiferous 16y ago
> exceedingly bad reason It depends on the context. If it's a developer's side project, why not? If it's a businessperson's project that you are under contract to build, then yes, it's a bad reason.
- deleted 16y ago
  [deleted]
jaekwon 16y ago
Playing with new technology == motivation win.
jrockway 16y ago
The key to getting work done is to want to do it. Using technology that you want to play with makes the "wanting to do it" part easier. What follows is the project being done.
blantonl 16y ago
Well at least he's honest, but this seems like an exceedingly bad reason to choose a technology stack. No it doesn't. If you see the promise and potential value of a new technology that solves a problem, you jumping aboard to play could mean the difference between a problem being solved or not. A lot of very powerful influential projects were started by people who wanted their end users to "play" with their technology.
mathgladiator 16y ago
One good reason to choose new technology is to ride the buzz wave and build up a technology brand. Additionally, you can exploit the python paradox to get amazing developers.
finkle12 16y ago
FYI, ericflo maintains a twitter account whose sole purpose is to covertly mock node.js http://twitter.com/nodecore http://twitter.com/nodecore It's good to see these Django guys having to use questionable tactics to challenge node.js.
- ericflo 16y ago
  Err, that is not me.
- huxley 16y ago
  my impression of Eric (I don't know him, I've only talked briefly at a couple of conferences) is that if he disagreed with something or thought it had problems, he'd tell you to your face. I sat in on his speech "Why Django Sucks, and How We Can Fix It" at Djangocon last year: http://djangocon.blip.tv/file/4112452/ http://djangocon.blip.tv/file/4112452/ And he gave a lot of tough love to Django in front of most of the establishment and people who are hardcore Djangonauts. Speaking of questionable tactics, why create a HN account just for the express purpose of attacking him?

by ericflo 16y ago

aaronblohowiak 16y ago

Later in the same paragraph: Node.js is architected near perfectly for this situation. (And Proxlet demonstrates amazing throughput on minimal hardware to validate that). That sounds like a good reason to me.

aaronwhite 16y ago
Can't wait to share these numbers! Blog post forthcoming in a few weeks.

aaronwhite 16y ago

Chris & I started Proxlet as a side project to scratch an itch and keep our skill-set fresh & do things in new ways. A great & rare opportunity to choose wild new tech stacks!

techiferous 16y ago

> exceedingly bad reason It depends on the context. If it's a developer's side project, why not? If it's a businessperson's project that you are under contract to build, then yes, it's a bad reason.

deleted 16y ago
[deleted]

jaekwon 16y ago

Playing with new technology == motivation win.

jrockway 16y ago

The key to getting work done is to want to do it. Using technology that you want to play with makes the "wanting to do it" part easier. What follows is the project being done.

blantonl 16y ago

Well at least he's honest, but this seems like an exceedingly bad reason to choose a technology stack. No it doesn't. If you see the promise and potential value of a new technology that solves a problem, you jumping aboard to play could mean the difference between a problem being solved or not. A lot of very powerful influential projects were started by people who wanted their end users to "play" with their technology.

mathgladiator 16y ago

One good reason to choose new technology is to ride the buzz wave and build up a technology brand. Additionally, you can exploit the python paradox to get amazing developers.

finkle12 16y ago

FYI, ericflo maintains a twitter account whose sole purpose is to covertly mock node.js http://twitter.com/nodecore http://twitter.com/nodecore It's good to see these Django guys having to use questionable tactics to challenge node.js.

ericflo 16y ago
Err, that is not me.
huxley 16y ago
my impression of Eric (I don't know him, I've only talked briefly at a couple of conferences) is that if he disagreed with something or thought it had problems, he'd tell you to your face. I sat in on his speech "Why Django Sucks, and How We Can Fix It" at Djangocon last year: http://djangocon.blip.tv/file/4112452/ http://djangocon.blip.tv/file/4112452/ And he gave a lot of tough love to Django in front of most of the establishment and people who are hardcore Djangonauts. Speaking of questionable tactics, why create a HN account just for the express purpose of attacking him?