5 ms·

http://backbonejs.org/ http://backbonejs.org/ is my favorite framework. It doesn't do much, I continue to be impressed with it daily. I'm on my second major pro

http://backbonejs.org/ http://backbonejs.org/ is my favorite framework. It doesn't do much, I continue to be impressed with it daily. I'm on my second major project with it. It's getting old now in JS years (read, actual years). Doesn't have any steam behind it compared to ember, react, angular. But it continues to work daily

at-fates-hands 10y ago
One of the first React workshops I was a part of was put on by Henrik Joreteg. In the first five minutes he said something along the lines of: "React has its place, and I mean Backbone still works and is a fucking amazing library." Then went on a mini rant about how people abandon libraries because they're new and shiny and its not because they're bad or deficient in any way - which is why he used his Backbone example. It's still awesome, it still works incredibly well and is still very much supported by a large, well informed community. Then of course, he went back to telling us how awesome ReactJS was and why we should want to try it and use it for our projects.
mohaine 10y ago
I hate backbone. Lots of boilerplate and everyone I see a set("field",value) I die a little inside. Also, everything of any size I've seen written in backbone turned into an unmaintainable mess.
- 91bananas 10y ago
  What boilerplate? React is all the rage now and it looks a hell of a lot like a backbone view. It has an initialize function, render, events, some constants, and the handlers for events. I don't know how much more minimal you can get than that. As for the unmaintainable part, I couldn't disagree more. Maybe you've worked with poor programmers?
  - mohaine 10y ago
    Really it is the requirement to to redefine your model in backbone that is a deal breaker. Alot of code that just don't have to write in other frameworks, although i understand why it is there. Most of the unmaintainable comes from it being a lighter weight frame work so devs often fall back to jquery. This is OK if you can figure out exactly where they added that trigger. Way to often that is overly hard. It could be pages away. And yes, most of my coworkes are poor programmers. Saddly that is the world we live in and I like frameworks that make them a little easier to live with.
    - Tenhundfeld 10y ago
      The issue I've seen with backbone apps, even written by "good programmers", is that no two are alike. So, when you come into a new app, a nontrivial amount of time is spent figuring out how the original programmers are using it, which libraries they pulled in for stuff like model validations, etc. To be fair, that's somewhat due to the fact that I mostly encounter them in consulting arrangements, and I don't know that any of the other frameworks are much better in this respect. I think I've just gotten spoiled by doing most of my work in Rails, a mature opinionated framework.
choward 10y ago
> It doesn't do much You can say that again. I used it for a pretty decent sized project and I'm not sure if it added any value. It doesn't do anything.
- 91bananas 10y ago
  Did you use it? Usually for it to do things you have to instantiate the objects, use their functions etc.

at-fates-hands 10y ago

One of the first React workshops I was a part of was put on by Henrik Joreteg. In the first five minutes he said something along the lines of: "React has its place, and I mean Backbone still works and is a fucking amazing library." Then went on a mini rant about how people abandon libraries because they're new and shiny and its not because they're bad or deficient in any way - which is why he used his Backbone example. It's still awesome, it still works incredibly well and is still very much supported by a large, well informed community. Then of course, he went back to telling us how awesome ReactJS was and why we should want to try it and use it for our projects.

mohaine 10y ago

I hate backbone. Lots of boilerplate and everyone I see a set("field",value) I die a little inside. Also, everything of any size I've seen written in backbone turned into an unmaintainable mess.

91bananas 10y ago
What boilerplate? React is all the rage now and it looks a hell of a lot like a backbone view. It has an initialize function, render, events, some constants, and the handlers for events. I don't know how much more minimal you can get than that. As for the unmaintainable part, I couldn't disagree more. Maybe you've worked with poor programmers?
- mohaine 10y ago
  Really it is the requirement to to redefine your model in backbone that is a deal breaker. Alot of code that just don't have to write in other frameworks, although i understand why it is there. Most of the unmaintainable comes from it being a lighter weight frame work so devs often fall back to jquery. This is OK if you can figure out exactly where they added that trigger. Way to often that is overly hard. It could be pages away. And yes, most of my coworkes are poor programmers. Saddly that is the world we live in and I like frameworks that make them a little easier to live with.
  - Tenhundfeld 10y ago
    The issue I've seen with backbone apps, even written by "good programmers", is that no two are alike. So, when you come into a new app, a nontrivial amount of time is spent figuring out how the original programmers are using it, which libraries they pulled in for stuff like model validations, etc. To be fair, that's somewhat due to the fact that I mostly encounter them in consulting arrangements, and I don't know that any of the other frameworks are much better in this respect. I think I've just gotten spoiled by doing most of my work in Rails, a mature opinionated framework.

choward 10y ago

> It doesn't do much You can say that again. I used it for a pretty decent sized project and I'm not sure if it added any value. It doesn't do anything.

91bananas 10y ago
Did you use it? Usually for it to do things you have to instantiate the objects, use their functions etc.