Why not call it hexagonal.coffee? Why do CoffeeScript libraries get a .js extension? Yes I realize it works for JavaScript too, but it's weird to go see a library with *.js in the name and then to find only CoffeeScript in the documentation.
Introducing hexagonal.js
11–20 of 43 posts
Re: Introducing hexagonal.js
#12There's far too many typos for me to have any amount of confidence in the code itself. Sorry, but I can't trust my business with people who cannot even be bothered to write proper English for their introduction.
Unintended humor alert:
x1024's criticism is not idiomatic English. "... can't trust by business with ..." should be " ... can't trust my business to ..."
Re: Introducing hexagonal.js
#13There's far too many typos for me to have any amount of confidence in the code itself. Sorry, but I can't trust my business with people who cannot even be bothered to write proper English for their introduction.
Sorry for my poor english, I'm still learning :(
No need to apologise; he was being a dick. Your english isn't bad and his comment is totally uncalled for.
Re: Introducing hexagonal.js
#14Why not call it hexagonal.coffee? Why do CoffeeScript libraries get a .js extension? Yes I realize it works for JavaScript too, but it's weird to go see a library with *.js in the name and then to find only CoffeeScript in the documentation.
We'll try to deliver new examples in pure JS.
Re: Introducing hexagonal.js
#15Earlier quoted context omitted.
Thanks for letting me know. I'll not be rushing out to add hexagonal.js to my Rails app, but if one of my friends who likes js wants to try building their own full app I'll mention this as a possibility.
To be honest most of project I developed with hexagonal.js have Rails as a backend and it's really powerful with sprockets on board. So give it a try, maybe in toy project.
Cool, I'll give it a shot, buddy. Thanks for the advice.
Re: Introducing hexagonal.js
#16This looks quite neat and the Rails example (https://github.com/hexagonaljs/rails-example) is interesting. I'll definitely have a play around with it later in my never-ending quest to find JS libraries that don't make me want to snap my computer in half.
Re: Introducing hexagonal.js
#17Hexagonal uses Raganwald's metaprogramming ideas. Follow the links from the dependency at https://github.com/gameboxed/YouAreDaBomb.
This shows the beauty of Coffeescript syntax for functional programming. For a deep understanding read Raganwald's new book http://ristrettolo.gy.
Re: Introducing hexagonal.js
#18Woaah, it's a cool idea, but I wonder how productive one would be in it. Will have to give it a shot later.
So the switching your mindset to hexagonal.js is quite hard at the beginning and I think it's the most time consuming part. Then you are very productive - gameboxed.com developed > 20 small and large apps using hexagonal.js last year.
Re: Introducing hexagonal.js
#19Why not call it hexagonal.coffee? Why do CoffeeScript libraries get a .js extension? Yes I realize it works for JavaScript too, but it's weird to go see a library with *.js in the name and then to find only CoffeeScript in the documentation.
We'll try to deliver new examples in pure JS.
That was an honest question more than a complaint. Why do CoffeeScript libraries not use the coffee extension? For broader appeal? Even if you had JavaScript documentation, I would see the source was written in CoffeeScript and realize I can't easily evaluate the quality of the source. Choosing CoffeeScript must mean you prefer it over JavaScript, so why use the extension of a language you do not prefer over one you do?
Re: Introducing hexagonal.js
#20Hexagonal uses Raganwald's metaprogramming ideas. Follow the links from the dependency at https://github.com/gameboxed/YouAreDaBomb . This shows the beauty of Coffeescript syntax for functional programming. For a deep understanding read Raganwald's new book http://ristrettolo.gy .
This.
I'm one of the people behind hexagonal.js. Raganwald's work enabled us to implement one of the main components - the glue code.