11 ms·

(However, It's also worth mentioning that Discourse is, if anything, even more of a JavaScript project than a Ruby on Rails project. So why not Node.js? Presum

by Offler 14y ago

(However, It's also worth mentioning that Discourse is, if anything, even more of a JavaScript project than a Ruby on Rails project. So why not Node.js? Presumably it's down to maturity.

edu 14y ago
He addressed it: Ruby isn't cool any more. Yeah, you heard me. It's not cool to write Ruby code any more. All the cool people moved on to slinging Scala and Node.js years ago. Our project isn't cool, it's just a bunch of boring old Ruby code. Personally, I'm thrilled that Ruby is now mature enough that the community no longer needs to bother with the pretense of being the coolest kid on the block. That means the rest of us who just like to Get Shit Done can roll up our sleeves and focus on the mission of building stuff with our peers rather than frantically running around trying to suss out the next shiny thing. (edit: formatting)
- k__ 14y ago
  This is just a rant and not a reason. "Hurr I said it's old school, so I use it. Now node.js is cool, so we can do our thang and no kiddies getting in the way" I mean, wth?! This whole post could be written with ruby changed to python and node.js changed to go or something. Seems like there is no "real" reason to use ruby at all, he just likes it but can't simply admit it...
  - edu 14y ago
    It's his reason for his decision. I don't see any problem with it, he prefers a more mature language/ecosystem (i.e. not cool) so they focus on GTD not trying to be the coolest guys around. He has a longer post on that topic: http://www.codinghorror.com/blog/2008/01/the-magpie-developer.html http://www.codinghorror.com/blog/2008/01/the-magpie-develope... As he also noted: There's always more than one way to do it, and just because I chose one particular way doesn't make it the right way – or even a particularly good way. I guess you've other metrics to decide what tools to use, and that's great :)
spoiler 14y ago
I think, what he meant to say by that, is that the forum is more of a browser app unlike your traditional forum software.
devniel 14y ago
I think that "node.js" is excelent for build real-time applications in a few days but for huge projects is a little difficult to handle all the "callback-style" and async results, IMHO it's about readable code , a key factor in developer teams.
- anonfunction 14y ago
  It's certainly a departure for many, but any code can be hard to read depending on how it's architected and who's writing it.
- pjmlp 14y ago
  Or a callback soup in the hands of many teams.
petercooper 14y ago
And the language simply isn't as good, IMHO. The ecosystem and the runtime may be better in numerous ways (the "node" part of "node.js" is also superb) and it may be fun to develop in, but that's in spite of the language. As a pure language JS isn't just up with Python, Ruby, C# or the like yet IMHO but progress is being made on this front (and even if it doesn't, things like asm.js, CoffeeScript, TypeScript, and Dart give us options.)

by Offler 14y ago

(However, It's also worth mentioning that Discourse is, if anything, even more of a JavaScript project than a Ruby on Rails project. So why not Node.js? Presumably it's down to maturity.

edu 14y ago

He addressed it: Ruby isn't cool any more. Yeah, you heard me. It's not cool to write Ruby code any more. All the cool people moved on to slinging Scala and Node.js years ago. Our project isn't cool, it's just a bunch of boring old Ruby code. Personally, I'm thrilled that Ruby is now mature enough that the community no longer needs to bother with the pretense of being the coolest kid on the block. That means the rest of us who just like to Get Shit Done can roll up our sleeves and focus on the mission of building stuff with our peers rather than frantically running around trying to suss out the next shiny thing. (edit: formatting)

k__ 14y ago
This is just a rant and not a reason. "Hurr I said it's old school, so I use it. Now node.js is cool, so we can do our thang and no kiddies getting in the way" I mean, wth?! This whole post could be written with ruby changed to python and node.js changed to go or something. Seems like there is no "real" reason to use ruby at all, he just likes it but can't simply admit it...
- edu 14y ago
  It's his reason for his decision. I don't see any problem with it, he prefers a more mature language/ecosystem (i.e. not cool) so they focus on GTD not trying to be the coolest guys around. He has a longer post on that topic: http://www.codinghorror.com/blog/2008/01/the-magpie-developer.html http://www.codinghorror.com/blog/2008/01/the-magpie-develope... As he also noted: There's always more than one way to do it, and just because I chose one particular way doesn't make it the right way – or even a particularly good way. I guess you've other metrics to decide what tools to use, and that's great :)

spoiler 14y ago

I think, what he meant to say by that, is that the forum is more of a browser app unlike your traditional forum software.

devniel 14y ago

I think that "node.js" is excelent for build real-time applications in a few days but for huge projects is a little difficult to handle all the "callback-style" and async results, IMHO it's about readable code , a key factor in developer teams.

anonfunction 14y ago
It's certainly a departure for many, but any code can be hard to read depending on how it's architected and who's writing it.
pjmlp 14y ago
Or a callback soup in the hands of many teams.

petercooper 14y ago

And the language simply isn't as good, IMHO. The ecosystem and the runtime may be better in numerous ways (the "node" part of "node.js" is also superb) and it may be fun to develop in, but that's in spite of the language. As a pure language JS isn't just up with Python, Ruby, C# or the like yet IMHO but progress is being made on this front (and even if it doesn't, things like asm.js, CoffeeScript, TypeScript, and Dart give us options.)