News for hackers. Stuff that matters.

A comment on Introducing hexagonal.js. Parent comment

Re:Introducing hexagonal.js by ricardobeat on Monday February 18, 2013 @09:42AM (#5238466)
Because it is javascript, to be used by javascript projects. Not having JS examples is just a problem in the docs, not the library.
[ Parent | on HN ]
Re:Introducing hexagonal.js by k3n on Monday February 18, 2013 @11:57AM (#5239178)
No, it's not JS.

    > class UseCase
    SyntaxError: Unexpected reserved word
[ Parent | on HN ]
Re:Introducing hexagonal.js by gfodor on Monday February 18, 2013 @02:56PM (#5240242)
Of course the point is it's not clear what it means to "be JS". Is it more important for the name to express what syntax the source code is in or what platform the code can run on? I think for your average developer who just wants to consume a library, they care more that it is a javascript-based library that they can use.
[ Parent | on HN ]
Re:Introducing hexagonal.js by ricardobeat on Monday February 18, 2013 @01:16PM (#5239622)
Of course CoffeeScript code won't run as javascript, it's not a superset. But it operates on the same global scope, the same object model, with similar semantics, so it "is" javascript, unlike other compile-to-js languages.

After reading more about it, I agree that it shouldn't have .js in it's name, or any other language extension, since it's not a framework/library. The fact that the examples are written in CoffeeScript is incidental.

[ Parent | on HN ]