#backbonejs — Public Fediverse posts

Is anyone still using npm v1 or v2 (most recent release 9 years ago)? Or do you know where I might find someone who does that? I have the following question:

Versions 1 and 2 of npm used to automatically install peerDependencies if they were not directly depended upon. From versions 3 to 6, a warning was given instead. From version 7 onwards, they went back to installing peerDependencies automatically, but this could be opted out of with peerDependenciesMeta.

Backbone has had an optional peer-ish dependency on jQuery from the beginning. Originally, this was not listed in the package.json so it was not installed unless the user opted in. We are now considering to make the dependency explicit and optional using peerDependenciesMeta, but for extant users of npm v1 or v2, that would mean jQuery is suddenly automatically installed where it previously would not. How bad would that be?

Of course, this would only affect users of the upcoming release of Backbone, which is perhaps a relatively uncommon combination with npm v2 or older, but the two can work together so it is not out of the question.

https://github.com/jashkenas/backbone/pull/4304

#JavaScript #nodejs #npm #legacy #BackboneJS

Got a notification that #BackboneJS has released a new version and was instantly mentally transported back to happier simpler times.

Still an example of clear, well-documented, and elegant (as it gets) #Javascript: https://github.com/jashkenas/backbone/blob/master/backbone.js

@papa_alpha_papa Interesting! Could I apply your benchmark to the #BackboneJS Events interface as well?

@aral Reminds me of #BackboneJS! 💕

I think about 2 years ago I had a long thread over here about updating my 10+ year old SPA (#backbonejs, #javascript, #perl, #Mojolicious) to a MPA using just #htmx for frontend interactivity.

Well, I've been way too busy to even start any of that! But, in the last couple of days I decided to go for a hybrid approach. I've added some htmx components to my single page application. My app's dashboard finally provides me with some interesting reports, powered by htmx.

That should do for now :-).

A beginner #webdev asked whether there was any #MustacheTemplating equivalent of #Angular's ngStyle. I answered on #StackOverflow with a short tutorial on how this can be achieved with #BackboneJS and #MVC.

https://stackoverflow.com/q/78307637/1166087

#JavaScript

I just released version 1.6.0 of #BackboneJS.

https://backbonejs.org/#1.6.0

#javascript #MVC

@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

I just released version 1.5.0 of #BackboneJS! It has

- an option to keep the trailing slash on a route URL
- bug fixes
- a code of conduct, security policy and many other doc improvements

Change log: https://backbonejs.org/#1.5.0
NPM: https://www.npmjs.com/package/backbone/v/1.5.0
#javascript

@[email protected] I still have a couple of SPA’s to manage that are about 9-10 years old. Written in #CoffeeScript 1 (not too bad) and #BackboneJS with a #Perl #Mojolicious backend.

Getting to run the JS dev stuff and keeping it up to date, or rather working with a newer Node version is challenging. Looking back it being a SPA doesn’t do much for 85% of these apps. I should’ve used some #jQuery instead for the interactive parts. That way I could’ve moved to #htmx without any issue.

I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087

I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087

I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087

I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087

I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087

@selzero Both. 🙂 Bootstrap (and jQuery, which it depends on) is still valid. Not using anything else is old-fashioned, but if it works for you, why not?

I make full-blown client side applications, which benefit from a proper application framework (Bootstrap calls itself a framework, but is a widget toolkit). You could try #BackboneJS, which is lightweight and compatible with Bootstrap+jQuery. I maintain it. But if most of your HTML is static, or generated on the server side, you can do without.

@yenzie @gizmomathboy @genehack @randomgeek @ovid Nice parable. Can I add #BackboneJS, which was written by a vegan adventurer. It is a Toyota Hilux, which looks outdated but never fails you.

@markstos For those who don't know it yet: #UnderscoreJS and #BackboneJS both have this. Every release in the change log has a link to the documentation of that version.

@markstos For those who don't know it yet: #UnderscoreJS and #BackboneJS both have this. Every release in the change log has a link to the documentation of that version.

Like I said, this stack of #perl, #Mojolicious, #MySQL, #CoffeeScript, #BackboneJS and #Bootstrap has served me well this past decade. I've got several business critical webapps running in it.

The backend stays. The frontend gets replaced by mostly plain #HTML with #htmx and #TailwindCSS. This makes development a lot faster: less context switching as most of it is done inside HTML templates. Added but very nice bonus: less complicated and error prone build pipeline!

END

Having been in webdevelopment for about 20 years now (yikes!) using stuff like #MooTools, #jQuery, #Knockoutjs, #Backbonejs, #Marionettejs and #React sort of fixed the issue of making webapps interactive/reactive. It always felt cumbersome though as it required a lot of different stuff to make it possible. And now we suddenly had to manage state, validation etc. on the client side as well. More work.

But, I think I found the solution to this problem. One that reminds me of the good old days...

Trying to add some new stuff this week made me realise: I don't enjoy working on this. It has nothing to do with the backend though. I'll always love #perl and #Mojolicious. Both very stable and this past decade I had very little issues with upgrading if any at all.

The part of the stack that needs replacement is the frontend. It's one big #SPA (single page application) which means a bunch of HTTP JSON endpoints and #Backbonejs + #CoffeeScript + #Mustache taking care of the client side.

The webapp is written in #perl with #Mojolicious for the backend powered by #MySQL.

For frontend I went with #Backbonejs and #CoffeeScript. The state and support of modern #JavaScript features was limited back then, dare I say cumbersome. I also enjoyed CoffeeScript, even though I don't like #Python ;-). To make it look half decent I went with #Bootstrap as a CSS framework, but hardly any customisations.

For development I used #Vagrant with #VirtualBox, but since 4-5 years I moved to #Docker.