You probably don’t need an applets framework.
On the market, there will be large companies to launch their own small program r & D library/framework, the function is very powerful, but also for the development of small program brought convenience. But in some positive feedback, we also see a different voice:
- White bug: Another wheel.
- Jsweber: Applet doesn’t use any framework. It’s a great experience. It borrows ideas from Vue and React.
- @ teil month: now in polite company front end are very keen to build its own wheels or wheels in leather to others and then own wheels, crazy lego’s own technical barriers, which have to brag about the leadership of the capital, let the new arrivals must belong to the gaffer, and can bring their own security, don’t know what is good or bad.
- Redbuck: The more wheels I’m building, I’m thinking maybe I should switch back to native for the next widget.
- Fantasy525: I don’t think it’s necessary to support all aspects of the code at once. The more we support, the more bugs we may have, the more bugs we may have.
- @ A lot of meat: can’t learn to move ah… ðŸ˜
The comments above are culled from nuggets user reviews.
These days, we met some students in school. Two of them are impressive:
1. At the end of the interview, student A suddenly asked if you had to use MPVUE (A small program framework introduced by Meituan in the early years) after being acquired by Meituan. When I answer is not hind, the classmate A long relief: that is good. He explained that he prefers to use native to write small programs, because the update pace of wechat team is relatively fast, and the framework often cannot keep up with the pace of wechat, resulting in the new features cannot be used in the project.
Ii. Student B wrote in his resume that he was proficient in jQuery. I was thinking that jQ appeared less and less in his resume these years. “I often use jQ to do some web demos, because it’s easy to get started,” he said. “I just need to introduce CDN JS without installing node packages.”
em… Seems to make a lot of sense.
Inside Mobike, we have encapsulated Mozzy, a basic library of small programs that is extended based on the native grammar of wechat small programs and friendly to the native wechat API support. Note: It is positioned as a base library, not a framework. Simply introduce a JS file into the native syntax applet project, and even a half-developed applet can be quickly introduced.
I remember that when I just finished this project and shared it internally, the last sentence of my future vision was as follows:
Maybe one day, you’ll delete Mozzy. Js with the little program Mozzy created, and it’ll work just fine.
I believe many students have imagined in the early years of jQ project, if the browser native support jQ API, or simply browser integration OF jQ, there is no need to introduce a section of jQ code in the HTML of each project, after all, jQ was almost the basic library required for web development.
With the update to wechat’s official API, many of Mozzy’s implementations now have official support. Maybe the shared vision of the future was already here, and the latest Mozzy move to exist in a million lines of code.
Embrace change.
The next series of articles will chronicle the details and journey of Mozzy and even mobike’s miniapp development, in what can be called a memoir of the progression of miniapp skills.
The main contents are as follows, most of which have been written and will be updated from time to time:
- Small program skills Advanced Memoirs – in the absence of componentized days
- Small program skills advanced memoir – self-implementation of data listeners and calculators
- Small program skills advanced memoir – autonomously implemented interceptor
- Mini-program skills progression memoir – globalData stuff
- Applets skill Progression Memoir – When to execute onLoad
- Small program skills advanced Memoir – enhanced WX. NavigateBack
- To be determined
Of course, do not rule out title modification for the “title party” form fool people. Just like this