JSLite - Introduction
If you have any questions, you are welcome to communicate in these places, and you are welcome to join the JSLite.io organization team for joint development!
segmentfault Community | Official website | Official documentation - more details | Issues
__ ______ __ __ ______ ______ /\ \ /\ ___\ /\ \ /\ \ /\__ _\ /\ ___\ _\_\ \ \ \___ \ \ \ \____ \ \ \ \/_/\ \/ \ \ __\ /\_____\ \/\_____\ \ \_____\ \ \_\ \ \_\ \ \_____\ \/_____/ \/_____/ \/_____/ \/_/ \/_/ \/_____/
- jQuery's goal is to be compatible with all major browsers, which means it A lot of code is useless or inefficient for mobile browsers.
- JSLite is only written for advanced browsers (supporting HTML5, CSS3) and mobile browsers. It uses new js methods to implement jQuery API, so it is smaller and more efficient.
- More The important thing is that JSLite's API is completely modeled after jQuery, so the learning cost is also very low.
- JSLite and jQuery have most similar APIs. The general library is only 5-10k, and every kb on the mobile phone is money.
- Make web development faster, download and execute faster, and be lighter, a JavaScript library for modern advanced browsers. Advancing front-end development standards is everyone's responsibility for Siege Division.
This compatibility is judged based on the support of some js method functions I use. There are too few devices, which is partly determined based on the method function compatibility data of developer.mozilla.org. Our main compatibility targets are as follows
Safari 6+ (Mac)
Chrome 30+ ( Windows, Mac, Android, iOS, Linux, Chrome OS)
Firefox 24+ (Windows, Mac, Android, Linux, Firefox OS)
iOS 5+ Safari Android 2.3+ Browser
Internet Explorer 10+ (Windows, Windows Phone)
