inossidabile

4 ms·

1.
AWS Lambda Orchestration via Kubernetes(staal.io)
1 points by inossidabile 2y ago|0 comments
2.
2-Way Data Binding under the Microscope(staal.io)
3 points by inossidabile 13y ago|1 comments
3.
by inossidabile 13y ago
Active links (that for some reason did not activate at post itself): README: https://github.com/inossidabile/protector Intro: http://staal.io/blog/2013/06/04/the-protector/
4.
Show HN: Protector – Ruby ORM security on a field level
5 points by inossidabile 13y ago|2 comments
5.
by inossidabile 13y ago
We are waiting for 1.2.0 Vagrant release to make use of the librarian plugin. Vagrant self-installer will solve Windows issue. It contains several tiny bugs atm unfortunately :(
6.
by inossidabile 13y ago
We moved it to http://rove.io
7.
by inossidabile 13y ago
We were only able to add packages that we use ourselves for now. It will take some time but we are going to expand the list.
8.
by inossidabile 13y ago
Makes sense. We will consider changing it. Thank you.
9.
by inossidabile 13y ago
Well... That's just a name after all. Short and memorable.
10.
by inossidabile 13y ago
http://github.com/aderyabin/hospice
11.
Show HN: Hospice.io – Vagrant configurations generator(hospice.io)
93 points by inossidabile 13y ago|46 comments
12.
Mastering ActiveAdmin(staal.io)
2 points by inossidabile 14y ago|0 comments
13.
Joosy future: avoid JS MVC transport boilerplate with tighter Rails integration(borisstaal.com)
2 points by inossidabile 14y ago|0 comments
14.
by inossidabile 14y ago
The site itself (joosy.ws) is hosted on a company server. The repo is on github but it's private. However, Guides are in public repo (hosted at Github Pages). Here they are: https://github.com/roundlake/joosy-guides If you want to modify
15.
by inossidabile 14y ago
What a dumb joke it would be %). Fixed, thank you.
16.
by inossidabile 14y ago
Take Ember for example. Joosy is only 2-3kb more including Sugar. Compare the profit. One framework can not (and should never try to) address everything. Sugar beats Underscore without a hope ( http://borisstaal.com/post/24270017179/please-
17.
by inossidabile 14y ago
Fixed! Thanks for the catch! :)
18.
by inossidabile 14y ago
Agreed. It's planned already in fact. Just need some more hours in a day :)
19.
by inossidabile 14y ago
While you have a point, you seem to miss the original problem of browser frameworks. Browsers work _differently_. This is not the problem of a framework. Moreover nothing can stop you from using node.js + DOM mock to test anything you want.
20.
by inossidabile 14y ago
If you don't, please take a moment to share your thoughts with me :)
21.
by inossidabile 14y ago
It will work with any Rails JST binding. Just use .jst.slim instead of .jst.hamlc (remember to use JS version and not Ruby one :D). Everything that has a proper binding to Rails should work out of box. For everything else, it has an abstra
22.
by inossidabile 14y ago
You just take it and use it. Joosy doesn't make to write you code in some special way (except CoffeeScript but it can be used with node.js). What's for binding parts (pages, layouts), I doubt you will ever want to use browser parts in node.
23.
by inossidabile 14y ago
Reusability is a thing that comes from your hands and not a framework. Of course, framework can influence it a bit. But we promote correct encapsulation at each layer. What exactly you think is wrong?
24.
Show HN: Joosy, the rails-tied browser app framework(borisstaal.com)
91 points by inossidabile 14y ago|35 comments
25.
Rails + REST: avoiding the views nightmare(borisstaal.com)
1 points by inossidabile 14y ago|0 comments