jQuery vs Riot: What are the differences?
"Cross-browser" is the primary reason why developers consider jQuery over the competitors, whereas "Light weight. Fast. Clear" was stated as the key factor in picking Riot.
jQuery and Riot are both open source tools. It seems that jQuery with 51.9K GitHub stars and 18.3K forks on GitHub has more adoption than Riot with 13.7K GitHub stars and 1.02K GitHub forks.
Uber Technologies, Twitter, and reddit are some of the popular companies that use jQuery, whereas Riot is used by BestFone 2.0, Walla!, and Thanx. jQuery has a broader approval, being mentioned in 4049 company stacks & 2607 developers stacks; compared to Riot, which is listed in 9 company stacks and 6 developer stacks.
The project is a web gadget previously made using vanilla script and JQuery, It is a part of the "Quicktext" platform and offers an in-app live & customizable messaging widget. We made that remake with React eco-system and Typescript and we're so far happy with results. We gained tons of TS features, React scaling & re-usabilities capabilities and much more!
What do you think?
I've an eCommerce platform building using Laravel, MySQL and jQuery. It's working good and if anyone become interested, I just deploy the entire source cod e in environment / Hosting. This is not a good model of course. Because everyone ask for small or large amount of change and I had to do this. Imagine when there will be 100 separate deploy and I had to manage 100 separate source. So How do I make my system architecture so that I'll have a core / base source code. To make any any change / update on specific deployment, it will be theme / plugin / extension based . Also if I introduce an API layer then I could handle the Web, Mobile App and POS as well ? Is the API should be part of source code or a individual single API and all the deployment will use that API ?
When I started TipMe, I thought about using React frontend. At the end, plain, simple jQuery won.
I had to build this iteration of the site fast and by using jQuery I could keep using Django as a full stack development tool. One important point is Django form (combined with Django Bootstrap3) means that I don't have to reinvent form rendering again, which will be the case with React.
Over time, more interactivity seeped into the site and React components start making its way into the codebase.
I now wish the site is built using React so that I could add more user friendly interfaces easier (no more fuddling with server states) but I would still say jQuery helped me get past those early days.