Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

jQuery
jQuery

126.4K
18.8K
+ 1
6.6K
RefluxJS
RefluxJS

27
22
+ 1
5
Add tool

jQuery vs RefluxJS: What are the differences?

jQuery: The Write Less, Do More, JavaScript Library. jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML; RefluxJS: A simple library for uni-directional dataflow application architecture inspired by ReactJS Flux. The goal of the refluxjs project is to get this architecture easily up and running in your web application, both client-side or server-side.

jQuery and RefluxJS belong to "Javascript UI Libraries" category of the tech stack.

"Cross-browser" is the primary reason why developers consider jQuery over the competitors, whereas "Easy to understand" was stated as the key factor in picking RefluxJS.

jQuery and RefluxJS are both open source tools. jQuery with 51.9K GitHub stars and 18.3K forks on GitHub appears to be more popular than RefluxJS with 5.43K GitHub stars and 352 GitHub forks.

What is jQuery?

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

What is RefluxJS?

The goal of the refluxjs project is to get this architecture easily up and running in your web application, both client-side or server-side.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose jQuery?
Why do developers choose RefluxJS?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use jQuery?
    What companies use RefluxJS?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with jQuery?
    What tools integrate with RefluxJS?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to jQuery and RefluxJS?
      Bootstrap
      Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.
      JavaScript
      JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
      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 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.
      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.
      See all alternatives
      Decisions about jQuery and RefluxJS
      StackShare Editors
      StackShare Editors
      Rails
      Rails
      Redux
      Redux
      React
      React
      Ruby
      Ruby
      jQuery
      jQuery

      Late in 2014, around the time of the Series D, the WeWork engineering team had grown to 14, and while the backend was modernized with Rails and Active Admin CMS, the main website was lacking. The new headcount provided enough capacity to address the aging WordPress website.

      As the team experimented with front-end technologies, they implemented a new signup flow with Angular, and other flows, including the Market Page, in React and Redux. The team says of that time: “If you’re following closely, yes, this means that in one rails app we had pages that included one or many of the following: jQuery, Angular, and React.”

      See more
      StackShare Editors
      StackShare Editors
      Rails
      Rails
      Node.js
      Node.js
      Python
      Python
      React
      React
      Java
      Java
      Ruby
      Ruby
      Go
      Go
      Swift
      Swift
      Objective-C
      Objective-C
      jQuery
      jQuery

      By mid-2015, around the time of the Series E, the Digital department at WeWork had grown to more than 40 people to support the company’s growing product needs.

      By then, they’d migrated the main website off of WordPress to Ruby on Rails, and a combination React, Angular, and jQuery, though there were efforts to move entirely to React for the front-end.

      The backend was structured around a microservices architecture built partially in Node.js, along with a combination of Ruby, Python, Bash, and Go. Swift/Objective-C and Java powered the mobile apps.

      These technologies power the listings on the website, as well as various internal tools, like community manager dashboards as well as RFID hardware for access management.

      See more
      Kir Shatrov
      Kir Shatrov
      Production Engineer at Shopify · | 18 upvotes · 223.2K views
      atShopifyShopify
      jQuery
      jQuery
      JavaScript
      JavaScript
      React
      React
      TypeScript
      TypeScript
      Prototype
      Prototype
      #FrameworksFullStack
      #Languages

      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
      Dan Robinson
      Dan Robinson
      at Heap, Inc. · | 18 upvotes · 177.2K views
      atHeapHeap
      jQuery
      jQuery
      Backbone.js
      Backbone.js
      Marionette
      Marionette
      TypeScript
      TypeScript
      React
      React
      MobX
      MobX
      #JavascriptUiLibraries
      #Libraries
      #JavascriptMvcFrameworks
      #TemplatingLanguagesExtensions

      The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

      Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

      #JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

      See more
      Rails
      Rails
      Sidekiq
      Sidekiq
      PostgreSQL
      PostgreSQL
      Redis
      Redis
      MongoDB
      MongoDB
      Vue.js
      Vue.js
      vuex
      vuex
      jQuery
      jQuery
      React
      React
      Redux
      Redux
      Yarn
      Yarn
      #Bulma.io
      #Font-awesome

      I'm building a new process management tool. I decided to build with Rails as my backend, using Sidekiq for background jobs. I chose to work with these tools because I've worked with them before and know that they're able to get the job done. They may not be the sexiest tools, but they work and are reliable, which is what I was optimizing for. For data stores, I opted for PostgreSQL and Redis. Because I'm planning on offering dashboards, I wanted a SQL database instead of something like MongoDB that might work early on, but be difficult to use as soon as I want to facilitate aggregate queries.

      On the front-end I'm using Vue.js and vuex in combination with #Turbolinks. In effect, I want to render most pages on the server side without key interactions being managed by Vue.js . This is the first project I'm working on where I've explicitly decided not to include jQuery . I have found React and Redux.js more confusing to setup. I appreciate the opinionated approach from the Vue.js community and that things just work together the way that I'd expect. To manage my javascript dependencies, I'm using Yarn .

      For CSS frameworks, I'm using #Bulma.io. I really appreciate it's minimal nature and that there are no hard javascript dependencies. And to add a little spice, I'm using #font-awesome.

      See more
      Johnny Bell
      Johnny Bell
      Senior Software Engineer at StackShare · | 9 upvotes · 141.1K views
      atStackShareStackShare
      jQuery
      jQuery
      React
      React
      ES6
      ES6
      JavaScript
      JavaScript
      MobX
      MobX
      GraphQL
      GraphQL
      Apollo
      Apollo
      #Hooks🎣
      #Context

      We are always building new features and replacing old code at StackShare. Lately we have been building out new features for the frontend, and removing a lot of old jQuery code (sorry jQuery but it's time to go).

      We've mainly been using React, ES6 and JavaScript on the frontend to build out the components, and we've been slowly removing some legacy MobX and using GraphQL and Apollo for our state management, if we need to control state further than GraphQL and Apollo allows us to we use just plain React with #context , or the new fancy React #hooks🎣 .

      As we've moved towards the above tech, its really made smashing out new features and updating legacy code super fast, and really fun!

      See more
      Ganesa Vijayakumar
      Ganesa Vijayakumar
      Full Stack Coder | Module Lead · | 15 upvotes · 838.6K views
      Codacy
      Codacy
      SonarQube
      SonarQube
      React
      React
      React Router
      React Router
      React Native
      React Native
      JavaScript
      JavaScript
      jQuery
      jQuery
      jQuery UI
      jQuery UI
      jQuery Mobile
      jQuery Mobile
      Bootstrap
      Bootstrap
      Java
      Java
      Node.js
      Node.js
      MySQL
      MySQL
      Hibernate
      Hibernate
      Heroku
      Heroku
      Amazon S3
      Amazon S3
      Amazon RDS
      Amazon RDS
      Solr
      Solr
      Elasticsearch
      Elasticsearch
      Amazon Route 53
      Amazon Route 53
      Microsoft Azure
      Microsoft Azure
      Amazon EC2 Container Service
      Amazon EC2 Container Service
      Apache Maven
      Apache Maven
      Git
      Git
      Docker
      Docker

      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
      Justin Welter
      Justin Welter
      jQuery
      jQuery

      I use jQuery because like other frameworks/libraries it handles significant amounts of boilerplate and heavy lifting compared to crafting your own UI tooling. Certainly more modern options such as Angular/Vue/React overcome some of the challenges in large jQuery based applications, but if you just need some straightforward DOM manipulation on a small scope, why not jQuery?

      See more
      JavaScript
      JavaScript
      jQuery
      jQuery

      "Do you recommend using jQuery, vanilla JavaScript or some combination of them, and in what situation do each of those make sense?"

      If jQuery or vanilla are the only two options available, then use the library that's available when its features will avoid having to reinvent wheels. Look at what jQuery offers, and look at the things you want to do. If a handmade solution doesn't require a lot of extra effort, then don't bother.

      But the correct answer is NONE OF THE ABOVE. There are a LOT of other options. https://www.google.com/search?q=top+javascript+frameworks&tbs=qdr:m Use a tool that makes sense for the goals of your project. Will it save you effort? Will it make the code more maintainable? There is no one perfect answer.

      See more
      Pedro Arnal Puente
      Pedro Arnal Puente
      CTO at La Cupula Music SL · | 8 upvotes · 22K views
      atLa Cupula Music SLLa Cupula Music SL
      JavaScript
      JavaScript
      jQuery
      jQuery
      jQuery UI
      jQuery UI
      Vue.js
      Vue.js
      Webpack
      Webpack
      ESLint
      ESLint