Home/ Questions/Q 7939059
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T22:59:02+00:00

I’ve just started using Spine.js. I like it. But sometimes I just need to

  • 0

I’ve just started using Spine.js. I like it.

But sometimes I just need to make a simple call to the backend to get JSON data to fill, say, a navigation bar that won’t be changing after it gets populated. Here, making a front end model and controller seem like overkill, when I could just use a simple jQuery call and push the JSON response into a template and inject the result into the DOM.

Is there any disadvantage to this hybrid approach, where some of the view gets managed by JavaScript MVC and others just get injected by simple jQuery Ajax code?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The whole idea behind MVC is separation of concerns. A Model handles data, a View handles display, and a Controller handles flow and in some cases business logic. Sure, you could easily make that jQuery call within your view; after all, JavaScript is wide open, and as long as you can get a reference, you’re free to do what you want. But doing that defeats the pattern and muddies the waters of the role your view plays. All in all, if you adopt the design pattern, stick to it. It’ll make managing your application months or even years from now a lot easier because you won’t have to think about the roles of your components.

    • 0