Rant: Backbone, Angular, Meteor, Derby • Hacker News Board

Re: Rant: Backbone, Angular, Meteor, Derby

#41

Post by hellopat » Fri, Jan 04, 2013, 9:09 PM UTC

heyitsnick wrote: post #23

I wanted to use Ember, and I started going down that road, but I just didn't click with it. I didn't progress past the tutorial! I can't remember what exactly I didn't get working, but I just felt very lost and overwhelmed, and that was spending a couple of days reading around online, looking at the code and examples.* I switched to Backbone and got going right away, in half a day of reading the docs and watching a c…

They just recently updated the guide. I haven't read through the whole thing, but it looks much more organized. Also there is a new Router API which is apparently significantly more intuitive.

http://emberjs.com/guides/

Re: Rant: Backbone, Angular, Meteor, Derby

#42

Post by typicalrunt » Fri, Jan 04, 2013, 9:11 PM UTC

MattRogish wrote: post #31

heyitsnick wrote: post #23

I wanted to use Ember, and I started going down that road, but I just didn't click with it. I didn't progress past the tutorial! I can't remember what exactly I didn't get working, but I just felt very lost and overwhelmed, and that was spending a couple of days reading around online, looking at the code and examples.* I switched to Backbone and got going right away, in half a day of reading the docs and watching a c…

We use Ember + Rails at work and if we didn't start with an Ember expert contractor we'd have been sunk. Ember is definitely a winding maze of stuff and until there's a "Agile Web Development with Ember 1.0" book, it's still very difficult to just jump in from scratch. Still, once we've learned Ember we're very happy with it. Backbone is just too small to start any medium/large app, and Ember has a decent community b…

What function is the Rails component serving? Is it just a REST interface or is it also acting as a separate HTML interface?

Re: Rant: Backbone, Angular, Meteor, Derby

#43

Post by stesch » Fri, Jan 04, 2013, 9:17 PM UTC

Apache Derby? http://en.wikipedia.org/wiki/Apache_Derby

Am I missing something here? Maybe next time put some links into your rants. Apache Derby was the only one I found on Wikipedia.

Re: Rant: Backbone, Angular, Meteor, Derby

#44

Post by sgdesign » Fri, Jan 04, 2013, 9:19 PM UTC

I can only speak for myself, but the reason I use Meteor (http://telesc.pe) is because I believe that while it's not perfect right now, it has a bright future ahead of it.

The Meteor devs themselves will acknowledge that some features are lacking (I imagine that's why it's not 1.0 yet), but the roadmap looks very promising and I believe Meteor also has the right team to make all this come true.

Re: Rant: Backbone, Angular, Meteor, Derby

#45

Post by callmevlad » Fri, Jan 04, 2013, 9:19 PM UTC

stesch wrote: post #43

Apache Derby? http://en.wikipedia.org/wiki/Apache_Derby Am I missing something here? Maybe next time put some links into your rants. Apache Derby was the only one I found on Wikipedia.

http://derbyjs.com/

Re: Rant: Backbone, Angular, Meteor, Derby

#46

Post by taylorbuley » Fri, Jan 04, 2013, 9:21 PM UTC

Backbone is a thoughtfully minimalistic approach to prototypical binding. There's no magic.

If you need more than that -- automagic binding using HTML data attributes via Angular -- it's OK to use another library.

Re: Rant: Backbone, Angular, Meteor, Derby

#47

Post by adolph » Fri, Jan 04, 2013, 9:22 PM UTC

Discusses Derby: http://derbyjs.com/

Not Apache Derby: http://db.apache.org/derby/

Re: Rant: Backbone, Angular, Meteor, Derby

#48

Post by lefnire » Fri, Jan 04, 2013, 9:22 PM UTC

stesch wrote: post #43

Apache Derby? http://en.wikipedia.org/wiki/Apache_Derby Am I missing something here? Maybe next time put some links into your rants. Apache Derby was the only one I found on Wikipedia.

woops, I added links into the rant.

Re: Rant: Backbone, Angular, Meteor, Derby

#49

Post by CapnCrooked » Fri, Jan 04, 2013, 9:24 PM UTC

hnwh wrote: post #34

johnnymonster wrote: post #21

Earlier quoted context omitted.

I personally use knockout all the time. Can't stand backbone or angular after using knockout.

Backbone I understand, but why not angular? It seems quite similar to knockout to me? Whats your backend platform?

I just finished evaluating frameworks for a project and chose Knockout over angular for a couple of reasons:

Extensibility & hooks: Extending built in behavior in Knockout was much easier than in Angular. Without getting into too much detail, one of the things I tried to do was create a list of items on the page with a simple animation for item removal. In Knockout, it was trivial. In angular it would have required a copy-pasta style rewrite of the repeat directive.

Some weird missing features: Angular has no conditional add/remove element directive (that I could find). This just seems like a weird oversight. There's a show/hide element directive, but trying to substitute that for add/remove will break CSS first/last/nth child selectors.

Angular has a lot of potential, but it felt to me like it needs a few more iterations before I'd want to try to build a rich UI on top of it.

Re: Rant: Backbone, Angular, Meteor, Derby

#50

Post by Angelo7 » Fri, Jan 04, 2013, 9:26 PM UTC

davidw wrote: post #36

I have a rant coming about these things too. * I started out with Backbone. It seems ok as far as it goes, but a bit annoying in that there's enough "magic" and stuff going on that I don't quite understand it completely, but without enough magic to really make things simple and easy. * Angular.js. Now this is more like it in terms of magic. Then, the other day, I decided to add a date picker to one of my forms. Uh oh…

"Also: a lot of these tools have tutorials that don't really walk me through all of what I want to do, which initially involves a fairly straightforward "CRUD" type of application. I want to see how the framework deals with both 'make me a new one' and 'edit an existing one' forms, for instance."

Couldn't have said it better myself. I can't count the number of times I had been excited about learning some new framework, only to discover that their documentation is non-existent, poor, or written for rocket scientists.