Live data from Hacker News

Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

towerjs.org

11–20 of 118 posts

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#14
post #8

Thanks for the efforts and the framework. Unfortunately, I cannot properly appreciate it for the following reason: Please don't call something JavaScript if it's actually all in CoffeeScript (even if it's just the documentation). A lot of us have not bothered to learn CoffeeScript and a good many of them have no intention of doing so. My time was wasted following a link that says "JavaScript", a language I know well,…

It was the coffeescript that put me off too. I dont have anything against CS, i just dont want the additional overhead of having to learn it

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#15
post #8

Thanks for the efforts and the framework. Unfortunately, I cannot properly appreciate it for the following reason: Please don't call something JavaScript if it's actually all in CoffeeScript (even if it's just the documentation). A lot of us have not bothered to learn CoffeeScript and a good many of them have no intention of doing so. My time was wasted following a link that says "JavaScript", a language I know well,…

To the down voters:

My comment is civil and explannatory. You may not like my sentiments, but down votes are not intended for unpopularity. Not only that, but in this case, my comment serves to reinforce the standards of HN regarding mis-titling of links and it is being downvoted.

A house divided against itself cannot stand.

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#16

Would some node.js experts mind weighing in here with pros and cons of this framework as they see it? I'm too new to node to really understand the tradeoffs here. Thanks!

Second. While I'm no expert, I did attend a Node.js Bootcamp this past weekend. One of the topics brought up was Coffeescript and how unwieldily it can be, especially if you mix it with straight-up Javascript, and by extension jQuery.

While avoiding any new FUD, and since Tower.js is Coffeescript and jQuery top heavy, wouldn't this inevitably lead to conflicts?

(Side note, at the bootcamp the framework recommended was Express.)

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#18
post #15
post #8

Thanks for the efforts and the framework. Unfortunately, I cannot properly appreciate it for the following reason: Please don't call something JavaScript if it's actually all in CoffeeScript (even if it's just the documentation). A lot of us have not bothered to learn CoffeeScript and a good many of them have no intention of doing so. My time was wasted following a link that says "JavaScript", a language I know well,…

To the down voters: My comment is civil and explannatory. You may not like my sentiments, but down votes are not intended for unpopularity. Not only that, but in this case, my comment serves to reinforce the standards of HN regarding mis-titling of links and it is being downvoted. A house divided against itself cannot stand.

"a language I have not bothered to learn, nor do I plan to anytime soon"

That's why I down voted you. Is a JS compiler beneath you? Fine. Then post about that. Don't try to slip it into a veiled complaint about title accuracy.

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#19
post #8

Thanks for the efforts and the framework. Unfortunately, I cannot properly appreciate it for the following reason: Please don't call something JavaScript if it's actually all in CoffeeScript (even if it's just the documentation). A lot of us have not bothered to learn CoffeeScript and a good many of them have no intention of doing so. My time was wasted following a link that says "JavaScript", a language I know well,…

It generates JavaScript. If you want to read JavaScript, it's there for you to do.

Re: Tower.js - JavaScript Framework for Node.js modeled after Ruby on Rails

#20

Would some node.js experts mind weighing in here with pros and cons of this framework as they see it? I'm too new to node to really understand the tradeoffs here. Thanks!

You'd have to already know CoffeeScript and Rails to benefit from this framework. I've used neither so personally I'd have a lot of trouble and a steep learning curve.

This builds on top of two other frameworks (Connect and Express) so I imagine the dependency stack for this framework is really long which might make debugging painful.

Post reply on HN