Need advice about which tool to choose?Ask the StackShare community!
Marko vs jQuery: What are the differences?
- Syntax: Marko uses a declarative syntax that resembles HTML, while jQuery relies on a more imperative approach using JavaScript for DOM manipulation.
- Performance: Marko is known for its high performance, optimized for server-side rendering and efficient re-renders, whereas jQuery can be slower due to its extensive use of querying and manipulating the DOM.
- Modularity: Marko promotes a modular architecture with components as the building blocks of the UI, providing better organization and reusability, whereas jQuery lacks clear structure and modularity for complex applications.
- Learning Curve: Marko requires a learning curve due to its unique syntax and concepts, whereas jQuery is easier to grasp for beginners familiar with JavaScript and HTML.
- Client-Side vs Server-Side: Marko is primarily a server-side technology for rendering UI components efficiently, while jQuery focuses on client-side scripting for enhancing user interactions within a web page.
- Tooling and Ecosystem: Marko has a smaller ecosystem and fewer third-party plugins compared to jQuery, which has an extensive range of plugins and tools available for various web development tasks.
In Summary, Marko and jQuery differ in syntax, performance, modularity, learning curve, client-side/server-side focus, and ecosystem support.
I have made an extended effort to drop frameworks completely if they are not actually needed. While I still use JS Frameworks like Vue, Angular and React ( if I have too ), I see far too often devs / teams deciding to build a single page site entirely in a framework, rather than just using HTML, CSS and a little JS.
I personally feel it's important to know when a framework is a good solution, and maybe when it's overkill.
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.
Pros of jQuery
- Cross-browser1.3K
- Dom manipulation957
- Power809
- Open source660
- Plugins610
- Easy459
- Popular395
- Feature-rich350
- Html5281
- Light weight227
- Simple93
- Great community84
- CSS3 Compliant79
- Mobile friendly69
- Fast67
- Intuitive43
- Swiss Army knife for webdev42
- Huge Community35
- Easy to learn11
- Clean code4
- Because of Ajax request :)3
- Powerful2
- Nice2
- Just awesome2
- Used everywhere2
- Improves productivity1
- Javascript1
- Easy Setup1
- Open Source, Simple, Easy Setup1
- It Just Works1
- Industry acceptance1
- Allows great manipulation of HTML and CSS1
- Widely Used1
- I love jQuery1
Pros of Marko
- Simplicity6
- Speed5
- Better than React, Vue, etc5
- No JSX5
- HTML markup4
- Components4
- Performance4
- Data Flow2
- Documentation1
- Low CPU cost1
- Virtual DOM1
- Isomorphic1
- Chut1
Sign up to add or upvote prosMake informed product decisions
Cons of jQuery
- Large size6
- Sometimes inconsistent API5
- Encourages DOM as primary data source5
- Live events is overly complex feature2
Cons of Marko
- Extensibility1
- Unit test1
- Mobile native1
Sign up to add or upvote consMake informed product decisions
What is jQuery?
What is Marko?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Marko?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with jQuery?
What tools integrate with Marko?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+43
+26+29