Viewing profile — yashke

Ok, now I see what you meant. So basically we don't want to limit audience of that idea to just CoffeeScripters. Also: maybe we'll switch to JS some day - if community show the nee…

We use Around in such cases - it can put original method call to callback of asynchronous method.

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 >…

We'll try to deliver new examples in pure JS.

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.

Sorry for my poor english, I'm still learning :(

Good question. In hexagonal.js approach client side is full app - so there's model part (use case is part of model), glue ~ controller and views are GUI and other adapters.

I scoped my blog just to unit tests, because it's short note rather than article. DI can be useful on integration and acceptance level too - for simple apps you should be able to c…

I think the basic difference between library and framework is that if you use framework it's responsible for bootstrap of your application, and library does not. But also framework…

Thanks, as I mentioned in other comment - I plan to digg deeper and share knowledge, so be patient :)

That's the next topic I want to digg in playing with Google Analytics. When I have some results I'll post them.

Thanks for your comment. I really try to find which part of this post could alienate any of our customers and I can't. I just described why we decided not to use ORM and I find it …