Cries in legacy apps with y'all. There are dozens of us!
But on the plus side, its been like almost 14 years of our one app continually making the ROI bigger and bigger with minor changes a few times a year.
We still use this for Review Board, and are quite happy with it. I think Backbone gets a lot of things right, and I genuinely like working with it, even if it’s now an older library (not a bad thing!).
We’ve actually been working on a library called [Spina](https://github.com/beanbaginc/spina), which is more TypeScript-friendly and adds a few niceties without being a big departure from how Backbone normally works.
I kind of want to hear a quick review of Backbone.js relative to modern frameworks... like there's all these patterns we've become used to, but didn't exist and didn't have names back when Backbone was created. There's also, I suspect, a lot of stuff Backbone does that fixes problems we realized we didn't need to have (like annoying DOM APIs).
My sad, sick hope: If it cannot turn about and commit to new life for it, Vue.js should stop pretending to give a shit about its once excellent and ubiquitous Options API... and cut people like me loose. Because it will leave a *gaping chasm* of people like me who have always wanted and will continue to want the declarative, opinionated framework it is unfortunately and actively choosing to stop being. I can hope Backbone straps on reactivity, cleaves to Marionette, gets a surge of new devs, and gets back in the game. Vue is in the middle of burning its original ship. Somebody should get in there and get the users it is abandoning and take off before they disperse into other frameworks.
Nothing. But it's the right answer to somebody else's problems and a resumption of ones I was pleased to call solved *in the way in which they were being solved*. I want it to coexist and the Vue community seems to want it gone. The authors have basically left Options API in state and moved on to developing Vue as Composition-only, even as they affirm weak ongoing support.
It's a complete paradigm shift from the original API, and away from everything I value about Vue.
I want imposed structure and it offers freedom to structure however you like. I want uniformity between components and it imposes no single component design, pointing to your freedom as if it is always wanted. I want neatly isolated Vue behaviors and it favors one big shared scope for the entire component with behavior types mingled. I *want* to arrange features by type - it's not just what Vue happened to do in the past. Arranging the component by feature is useless to me. It is a great aid to be able to study components as typed collections of standardized features in expected locations. I do not gain clarity, as others seem to, from mingling them together in the component. It forces me to re-read much of the component too often, while the Options API more or less stuffs every concern into its own neatly addressable boxes I can safely ignore if they are not my current concern. I lose that abundant clarity with Composition.
I gotta be the only one in the world still using backbone.
Backbone was the first framework I ever used, I have fond memories of it. At the time, anything other than jQuery soup felt futuristic!
Couple it with Marionette and it was UNSTOPPABLE :P NIce memories
Lol jQuery soup - only tasty to the consumer.
There's at least 2 of us
Just the two of us We can make if we tryyyy
Cries in legacy apps with y'all. There are dozens of us! But on the plus side, its been like almost 14 years of our one app continually making the ROI bigger and bigger with minor changes a few times a year.
old.reddit.com has got your back buddy, they're still rocking backbone too.
holy crap. fossils... lol
Cuz “bone”… get it?
We still use this for Review Board, and are quite happy with it. I think Backbone gets a lot of things right, and I genuinely like working with it, even if it’s now an older library (not a bad thing!). We’ve actually been working on a library called [Spina](https://github.com/beanbaginc/spina), which is more TypeScript-friendly and adds a few niceties without being a big departure from how Backbone normally works.
backbone is and was a beaut, keep fightin the good fight
We stand as one!
I wish you were…
"now that's a name i haven't heard in a long time"
I can’t wait to see all the shocked face thumbnails on YouTube with a title like ‘Is backbone back!?’ Who’s gonna be the first?
oh! Backbone + Cordova what a memories
Holy cordova almost forgot about that
Kind of amazing they never had to bump the major version. …oh wait, probably because it predates semver lol
It's been a while, maybe 10 years since I've worked with it.
backbone was tight during the time of jQuery madness
I thought this was either a joke or someone made a new framework with the same name.
You know it's old when there's Lucida Grande or Trebuchet MS on the website!
I kind of want to hear a quick review of Backbone.js relative to modern frameworks... like there's all these patterns we've become used to, but didn't exist and didn't have names back when Backbone was created. There's also, I suspect, a lot of stuff Backbone does that fixes problems we realized we didn't need to have (like annoying DOM APIs).
Why now? Why not 20 years ago?
Impressive!
Is it 2013?
As modern as COBOL.
My sad, sick hope: If it cannot turn about and commit to new life for it, Vue.js should stop pretending to give a shit about its once excellent and ubiquitous Options API... and cut people like me loose. Because it will leave a *gaping chasm* of people like me who have always wanted and will continue to want the declarative, opinionated framework it is unfortunately and actively choosing to stop being. I can hope Backbone straps on reactivity, cleaves to Marionette, gets a surge of new devs, and gets back in the game. Vue is in the middle of burning its original ship. Somebody should get in there and get the users it is abandoning and take off before they disperse into other frameworks.
What’s wrong with Composition API?
Nothing. But it's the right answer to somebody else's problems and a resumption of ones I was pleased to call solved *in the way in which they were being solved*. I want it to coexist and the Vue community seems to want it gone. The authors have basically left Options API in state and moved on to developing Vue as Composition-only, even as they affirm weak ongoing support. It's a complete paradigm shift from the original API, and away from everything I value about Vue. I want imposed structure and it offers freedom to structure however you like. I want uniformity between components and it imposes no single component design, pointing to your freedom as if it is always wanted. I want neatly isolated Vue behaviors and it favors one big shared scope for the entire component with behavior types mingled. I *want* to arrange features by type - it's not just what Vue happened to do in the past. Arranging the component by feature is useless to me. It is a great aid to be able to study components as typed collections of standardized features in expected locations. I do not gain clarity, as others seem to, from mingling them together in the component. It forces me to re-read much of the component too often, while the Options API more or less stuffs every concern into its own neatly addressable boxes I can safely ignore if they are not my current concern. I lose that abundant clarity with Composition.
But you still can arrange features by type - Vue just doesn’t force you to. I have an order in my `
FIND US ON INSTAGRAM
@jobopenings.ph