Alternatives to Zepto logo

Alternatives to Zepto

jQuery, jQuery Mobile, React, AngularJS, and Vue.js are the most popular alternatives and competitors to Zepto.
296
66
+ 1
3

What is Zepto and what are its top alternatives?

While 100% jQuery coverage is not a design goal, the APIs provided match their jQuery counterparts. The goal is to have a ~5-10k modular library that downloads and executes fast, with a familiar and versatile API, so you can concentrate on getting stuff done.
Zepto is a tool in the Javascript UI Libraries category of a tech stack.
Zepto is an open source tool with 14.9K GitHub stars and 4.1K GitHub forks. Here’s a link to Zepto's open source repository on GitHub

Top Alternatives to Zepto

  • jQuery
    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • jQuery Mobile
    jQuery Mobile

    jQuery Mobile is a HTML5-based user interface system designed to make responsive web sites and apps that are accessible on all smartphone, tablet and desktop devices. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Vue.js
    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • jQuery UI
    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

  • Select2
    Select2

    It gives you a customizable select box with support for searching, tagging, remote data sets, infinite scrolling, and many other highly used options. It comes with support for RTL environments, searching with diacritics and over 40 languages built-in. ...

  • Prototype
    Prototype

    Prototype is a JavaScript framework that aims to ease development of dynamic web applications. It offers a familiar class-style OO framework, extensive Ajax support, higher-order programming constructs, and easy DOM manipulation. ...

Zepto alternatives & related posts

jQuery logo

jQuery

174.8K
54.9K
6.6K
The Write Less, Do More, JavaScript Library.
174.8K
54.9K
+ 1
6.6K
PROS OF JQUERY
  • 1.3K
    Cross-browser
  • 957
    Dom manipulation
  • 807
    Power
  • 660
    Open source
  • 610
    Plugins
  • 458
    Easy
  • 395
    Popular
  • 350
    Feature-rich
  • 281
    Html5
  • 227
    Light weight
  • 92
    Simple
  • 84
    Great community
  • 79
    CSS3 Compliant
  • 69
    Mobile friendly
  • 67
    Fast
  • 43
    Intuitive
  • 42
    Swiss Army knife for webdev
  • 35
    Huge Community
  • 11
    Easy to learn
  • 4
    Clean code
  • 3
    Because of Ajax request :)
  • 2
    Just awesome
  • 2
    Used everywhere
  • 2
    Powerful
  • 2
    Nice
  • 1
    Widely Used
  • 1
    Improves productivity
  • 1
    Open Source, Simple, Easy Setup
  • 1
    It Just Works
  • 1
    Industry acceptance
  • 1
    Allows great manipulation of HTML and CSS
  • 1
    Javascript
  • 1
    Easy Setup
CONS OF JQUERY
  • 6
    Large size
  • 5
    Sometimes inconsistent API
  • 5
    Encourages DOM as primary data source
  • 2
    Live events is overly complex feature

related jQuery posts

Kir Shatrov
Engineering Lead at Shopify · | 21 upvotes · 675.3K views

The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

#FrameworksFullStack #Languages

See more
Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
jQuery Mobile logo

jQuery Mobile

1.5K
297
0
Touch-Optimized Web Framework for Smartphones & Tablets
1.5K
297
+ 1
0
PROS OF JQUERY MOBILE
    Be the first to leave a pro
    CONS OF JQUERY MOBILE
      Be the first to leave a con

      related jQuery Mobile posts

      Ganesa Vijayakumar
      Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      React logo

      React

      129K
      105.1K
      3.9K
      A JavaScript library for building user interfaces
      129K
      105.1K
      + 1
      3.9K
      PROS OF REACT
      • 775
        Components
      • 658
        Virtual dom
      • 567
        Performance
      • 492
        Simplicity
      • 438
        Composable
      • 176
        Data flow
      • 162
        Declarative
      • 124
        Isn't an mvc framework
      • 114
        Reactive updates
      • 111
        Explicit app state
      • 40
        JSX
      • 24
        Learn once, write everywhere
      • 19
        Uni-directional data flow
      • 17
        Easy to Use
      • 14
        Works great with Flux Architecture
      • 10
        Great perfomance
      • 8
        Built by Facebook
      • 7
        Javascript
      • 5
        Speed
      • 5
        TypeScript support
      • 4
        Easy to start
      • 4
        Scalable
      • 4
        Awesome
      • 4
        Feels like the 90s
      • 4
        Hooks
      • 3
        Excellent Documentation
      • 3
        Scales super well
      • 3
        Functional
      • 3
        Obama
      • 3
        Fancy third party tools
      • 3
        Server side views
      • 3
        Props
      • 3
        Server Side Rendering
      • 3
        Cross-platform
      • 2
        Rich ecosystem
      • 2
        Start simple
      • 2
        Allows creating single page applications
      • 2
        Sdfsdfsdf
      • 2
        Beautiful and Neat Component Management
      • 2
        Very gentle learning curve
      • 2
        Has functional components
      • 2
        Simple
      • 2
        Closer to standard JavaScript and HTML than others
      • 2
        Super easy
      • 2
        Has arrow functions
      • 2
        Strong Community
      • 2
        Great migration pathway for older systems
      • 2
        SSR
      • 2
        Fast evolving
      • 2
        Simple, easy to reason about and makes you productive
      • 2
        Just the View of MVC
      • 1
        Sharable
      • 1
        Every decision architecture wise makes sense
      • 1
        Permissively-licensed
      • 1
        Split your UI into components with one true state
      • 1
        Fragments
      • 0
        Recharts
      CONS OF REACT
      • 36
        Requires discipline to keep architecture organized
      • 23
        No predefined way to structure your app
      • 22
        Need to be familiar with lots of third party packages
      • 9
        JSX
      • 7
        Not enterprise friendly
      • 5
        One-way binding only
      • 2
        State consistency with backend neglected
      • 2
        Bad Documentation
      • 1
        Paradigms change too fast

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 1.9M views

      I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

      See more
      Adebayo Akinlaja
      Engineering Manager at Andela · | 27 upvotes · 1.1M views

      I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

      A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

      In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

      If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

      See more
      AngularJS logo

      AngularJS

      49.4K
      36.1K
      5.2K
      Superheroic JavaScript MVW Framework
      49.4K
      36.1K
      + 1
      5.2K
      PROS OF ANGULARJS
      • 887
        Quick to develop
      • 587
        Great mvc
      • 572
        Powerful
      • 521
        Restful
      • 503
        Backed by google
      • 349
        Two-way data binding
      • 343
        Javascript
      • 328
        Open source
      • 305
        Dependency injection
      • 197
        Readable
      • 75
        Fast
      • 64
        Directives
      • 63
        Great community
      • 56
        Free
      • 38
        Extend html vocabulary
      • 29
        Components
      • 26
        Easy to test
      • 24
        Easy to learn
      • 23
        Easy to templates
      • 23
        Great documentation
      • 21
        Easy to start
      • 18
        Awesome
      • 17
        Light weight
      • 14
        Angular 2.0
      • 14
        Javascript mvw framework
      • 13
        Great extensions
      • 13
        Efficient
      • 10
        Easy to prototype with
      • 8
        High performance
      • 8
        Coffeescript
      • 7
        Mvc
      • 7
        Two-way binding
      • 7
        Lots of community modules
      • 6
        Easy to e2e
      • 6
        Clean and keeps code readable
      • 5
        Easy for small applications
      • 5
        One of the best frameworks
      • 4
        Fast development
      • 4
        Works great with jquery
      • 3
        I do not touch DOM
      • 2
        Be a developer, not a plumber.
      • 2
        Declarative programming
      • 2
        Dart
      • 2
        Community
      • 2
        The two-way Data Binding is awesome
      • 2
        Hierarchical Data Structure
      • 2
        Typescript
      • 1
        Botionescu@gmail.com
      • 1
        The powerful of binding, routing and controlling routes
      • 1
        Fkin awesome
      • 1
        Opinionated in the right areas
      • 1
        Supports api , easy development
      • 1
        Common Place
      • 1
        Great
      • 1
        Very very useful and fast framework for development
      • 1
        Amazing community support
      • 1
        Readable code
      • 1
        Linear learning curve
      • 1
        Scopes
      • 1
        Programming fun again
      • 1
        Acoperișul
      • 1
        Consistency with backend architecture if using Nest
      • 0
        Httpș//Acoperișul 0757604335
      • 0
        Angular js
      • 0
        Oautho loc
      • 0
        Shvzjn
      • 0
        Acoperișul 0757604335
      • 0
        Js
      • 0
        Bot Ionescu
      • 0
        Google.com
      CONS OF ANGULARJS
      • 10
        Complex
      • 3
        Dependency injection
      • 2
        Learning Curve
      • 2
        Event Listener Overload
      • 1
        Hard to learn

      related AngularJS posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.2M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      Vue.js logo

      Vue.js

      43K
      34.6K
      1.5K
      A progressive framework for building user interfaces
      43K
      34.6K
      + 1
      1.5K
      PROS OF VUE.JS
      • 287
        Simple and easy to start with
      • 222
        Good documentation
      • 189
        Components
      • 126
        Simple the best
      • 96
        Simplified AngularJS
      • 87
        Reactive
      • 72
        Intuitive APIs
      • 52
        Javascript
      • 48
        Changed my front end coding life
      • 45
        Configuration is smooth
      • 34
        Easy to learn
      • 32
        So much fun to use
      • 23
        Progressive
      • 19
        Virtual dom
      • 15
        Faster than bulldogs on hot tarmac
      • 10
        It's magic
      • 10
        Component is template, javascript and style in one
      • 8
        Best of Both Worlds
      • 8
        Perfomance
      • 7
        Without misleading licenses
      • 7
        Light Weight
      • 7
        Application structure
      • 7
        Elegant design
      • 6
        Intuitive and easy to use
      • 5
        Good command line interface
      • 4
        Like Angular only quicker to get started with
      • 4
        Single file components
      • 4
        Easy to integrate to HTML by inline-templates
      • 4
        Small learning curve
      • 4
        Logicless templates
      • 3
        Customer Render ending eg to HTML
      • 2
        Intuitive
      • 2
        Vuex
      • 2
        Lots of documentation
      • 2
        Component based
      • 2
        Bridge from Web Development to JS Development
      • 2
        Concise error messages
      • 2
        Supports several template languages
      • 2
        High performance
      • 2
        One-way data flow
      • 1
        GUI
      • 0
        React
      CONS OF VUE.JS
      • 7
        Less Common Place
      • 3
        YXMLvsHTML Markup
      • 1
        Don't support fragments
      • 1
        Only support programatically multiple root nodes

      related Vue.js posts

      Johnny Bell
      Shared insights
      on
      Vue.jsVue.jsReactReact

      I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

      It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

      See more
      Shared insights
      on
      Vue.jsVue.jsReactReact

      I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

      See more
      jQuery UI logo

      jQuery UI

      37.4K
      10.7K
      896
      Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
      37.4K
      10.7K
      + 1
      896
      PROS OF JQUERY UI
      • 213
        Ui components
      • 155
        Cross-browser
      • 121
        Easy
      • 100
        It's jquery
      • 81
        Open source
      • 57
        Widgets
      • 48
        Plugins
      • 46
        Popular
      • 39
        Datepicker
      • 23
        Great community
      • 7
        DOM Manipulation
      • 6
        Themes
      • 0
        Some good ui components
      CONS OF JQUERY UI
      • 1
        Does not contain charts or graphs

      related jQuery UI posts

      Ganesa Vijayakumar
      Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      Khauth György
      CTO at SalesAutopilot Kft. · | 12 upvotes · 409.9K views

      I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

      Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

      On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

      On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

      See more
      Select2 logo

      Select2

      2.9K
      60
      3
      The jQuery replacement for select boxes
      2.9K
      60
      + 1
      3
      PROS OF SELECT2
      • 3
        H
      CONS OF SELECT2
        Be the first to leave a con

        related Select2 posts

        Prototype logo

        Prototype

        2.2K
        28
        0
        Prototype JavaScript framework
        2.2K
        28
        + 1
        0
        PROS OF PROTOTYPE
          Be the first to leave a pro
          CONS OF PROTOTYPE
            Be the first to leave a con

            related Prototype posts

            Kir Shatrov
            Engineering Lead at Shopify · | 21 upvotes · 675.3K views

            The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

            Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

            #FrameworksFullStack #Languages

            See more