taterbase

7 ms·

61.
by taterbase 14y ago
My biggest gripe with Meteor is their effort in creating a new package manager. We already have NPM and it works well. I feel that for Meteor to truly be embraced by the Node.js community they'll need to embrace NPM.
62.
by taterbase 14y ago
We live in public may be what you're looking for.
63.
by taterbase 14y ago
You can, it just makes some of Rails' niceties unnecessary. Views and "Controllers" are handled up front by backbone. You just need routing and models from Rails.
64.
by taterbase 14y ago
It's not "society" that's failed. It's basic natural instinct kicking in. Many men prefer wider hips, large breasts, and youthful appearance. We can say all day that this comes down to taste but your inner caveman knows that she will be a h
65.
by taterbase 14y ago
Angular is fast and easy for development. Very ittle boiler-plate and comes with easy UI bindings. I feel it's perfect for smaller projects where separation of logic isn't as important. Angular has the ability to grow in complexity if you n
66.
by taterbase 14y ago
Do you have a repo with this prototype? I would really like to see this possibility pan out. I think using node to interface with file system is the most feasible and portable at this point.
67.
by taterbase 14y ago
CMD + K, CMD + B (Ctrl on windows/linux) opens up the gutter with all your files.
68.
by taterbase 14y ago
Awesome to see you guys utilizing a few different technologies to their strengths and not going the "silver bullet" route. Regarding your "Update resource B when A changes" situation you can use Backbone's callback hash var self = this;