@formido an acceptor is just a unit of work within the present method. It's essential to keep the many-to-many otherwise you'll start to inflate acceptors with otther parts of the model that otherwise would be dealt with an independent acceptor.
There are many cases when an acceptor would be use to set the view in a particular configuration (I don't want to use the word state), when that configuration can be used fo in different scenarios, then all the config aspects can be in a separate acceptor
I can understand XXX + JQuery because it's going to be a while until we port all the good stuff that was built with it but after that, even underscore, I am always hesitant to add a library for a couple of functions I can write in a few lines of code.
I can't, the project is using jQuery just for event delegation, the model and B.I. is in Backbone and rendering is backbone > react + ejs. He showed me some parts of code and is not spaghetti code, but spaghetti with rice, beans and meat.
I showed SAM to him, but him is a Junior dev. in the company. Next month we will start develop an app with SAM. We are tired of this companies of poor coding practices, architecture and design. But if we go in their web sites they look like GODs.
ah ah, as I say, the world is built on bullshit (I don't mean it in a negative way). When you think of it progress has always happened pretending something can be done (e.g. I can fly) until one day someone does it. Same applies to I can write good code.