mvc - How to deal with the relationship between Model View and other elements in non-Web graphics applications?

Question

Today I complained and posted a Weibo:
http://weibo.com/1651843872/B09Wxlokv?mod=weibotime

Looking back now, jQuery's interface may even be harmful to large applications. The concept of MVC largely abstracts a clear Model, and the View is synchronized to the interface based on the Model. In jQuery, it is directly Treating the View as a Model... I was confused all the way.

I learned the front-end because I realized that it is very cheap to develop graphical interfaces on the Web platform,
It wasn’t until I started working on applications that I began to truly realize the complexity of graphics applications..
According to my recollection, this learning process is simply a step-by-step process to support the use of jQuery..
The separation of Model, View, and other components and their respective functions can only be gradually seen more clearly.

The Web is very messy, because the DOM already has a layer of abstraction, and it also blocks some roads in terms of provision,
So how to deal with the relationship between View and Model in graphics development on other platforms without DOM?

For example, the underlying implementation of the Webkit tool library maintains Model and View.
There are also Unity3D, Flash, etc. How do you understand these parts?

The question is a bit general. Please give me some advice, thank you.

Answer 1

Wait a minute, why are you against jQ? jQ is a DOM operation encapsulation and has almost nothing to do with MVC. Just like fighting with both guns and cannons, you can't say "I realize that a cannon can blow up a bunker with one shot, so the use of rifles is harmful to the battlefield"

In fact, although AngularJS advocates no jq, the essence is to streamline jqLite for use, while Backbone is naturally pro-jQ. Large applications have no structure at all. Hard-coding in jQ is certainly a wrong way, but simply thinking that implementing MVC without jQ is not a correct idea.

Posting my review of last year’s Backbone for reference. In fact, I now think that unless it is a "management interface" type application, Backbone or Backbone-like Model mechanism, specifically Backbone.sync用处不大。因为浏览器端的JS天生不『拥有』任何数据，不会负责数据的简单CURD式的落地（H5涉及离线本地存储另说）。浏览器端JS可能更需要的是维护数据和DOM绑定，也就是所谓ViewModel, refer to KnockoutJS

Sorry for not having non-Web experience.