jQuery vs. React vs. Famous Framework

We've probably only scratched the surface of what we can use jQuery for. It's likely a place that we will keep growing into.

I use this for most of my HTML5 based applications.

extensively for client-side logic

A solid JS core library.

Broad Use

Easy and cool front end interactions.

Came With Knack Ar

Used jQuery for dom manipulations. Another great feature used was its deferred() function with promise to avoid callback hell.

It provides a great API for DOM manipulation, AJAX, and other handy tools.

Drupal JQuery for UI.

반응형 웹 개발

The Opstax website uses some jQuery for effects and functionality.

jQuery powers some scripts on the Trends dashboard.

Frontend enhancements.

Used on the landing page.

The best known DOM manipulation library we know of. Still not a silver buller.

Also, its Deferred object is very useful.

As all html dom manipulator

website

null

It's jQuery. What more can I say?

DOM manipulation and animation.

Front end

Standard usage.

jQuery's pretty useful for DOM manipulations within Angular directives. We're considering switching to a lighter-weight alternative though, such as Zepto.

Some good plugins around there to use for visual effects.

Amazing plugins are available for all UI needs.

Legacy

5 years of experience using jQuery for DOM manipulation.

We use a wee bit of jQuery in the Web App UI.

example

Graphics Animations and Responsive Animated Menu

frontend

Browser compatible Javascript is faster and more reliable using this well established library.

Pluginzzzz

cross-browser DOM manipulation

Just the frontend controls.

Basic web pages

Just about everywhere on front-end as glue.

Work as a hard dependency of Meteor Blaze, also use it for DOM data operations.

New customer-facing pages make heavy use of jQuery to enhance Javascript usability, provide cross-platform compatibility, and ease of coding.

Because WordPress needs it

To save time on javascript coding.

¯_(ツ)_/¯

Website magic

Just for ajax requests.

jQuery is used offload some of the work to the client (browser) so not everything has to be done on the server side.

Agile Toolkit allows you to bind JavaScript on View objects.

DOM manipulation for file input field.

AJAX data calls, geolocation, cookie setting and JS plugin dependency.

Used to built rich experience for the users

instead of javascript

jquery가 없었다면 저는 프론트엔드를 정말 어려워했을 것입니다. jquery를 좋아하고 사용하는데 부담이 딱히 없으며 문서를 보고 새로운 함수 등을 익히는 중입니다.

Dom Manipulation

Basic front-end DOM manipulation inside componentDidMount lifecycle in React Components as well as serving as a dependency for other javascript modules.

Extremely versatile integration with views. Easy to create forms, interaction, animation and comms with backend service.

Funcionalidades de cliente Cross-browser

Used jQuery for web application development, created button responsed to right/center/left button mouse click events in web application.

지금 단계에서 React나 Angular, Vue 같은걸 도입하기엔 무리가 있다고 생각해 일단은 jQuery로 개발 중

Frontend utility library. Use was fairly minimal: lodash, ReactJS, and 'native' ES6 functions now fill the gap jQuery used cover. Will likely be removed in an upcoming iteration.

I don't use javascript, I use jquery....well I know it does not make sense, but I just want to stress how important it is. let's rephase it: whenever I use javascript, I use jquery. when you look at any js file of mine, 90% is jqery api.

Client-side interaction.

Some parts of the frontend are using jQuery.

I use a bit of jQuery here and there for AJAX.

expert

Used for development on QuickBase.com

StyleGuide infrastructure

• basic foundation
• cross-brands
• modular
• responsive

copy and hack menu.js file if meeting SG issues

Front-end user interfacing.

anything front-end, jquery usually gets used.

jQuery has it's quirks, but they're well understood. We opted for a more traditional web app using older, more well-tested technologies like jQuery instead of newer "single page application" type apps.

Easy DOM manipulation and plugins.

Front개발을 쉽게 하게 도와주었습니다. 최근에도 새로운 함수들을 주의깊게 지켜보고 있습니다.

The Ajax calls you can make with jQuery makes integrating the front end with the back end very smooth.

Dom munipliation

Used to add dynamic features such as AJAX

Web and mobile UI.

jQuery is used mostly because I needed jQuery UI for the modal dialog. Otherwise, I use it to reference DOM elements when I'm too lazy to type "document.getElementById(...)".

Front-end interactions (Client)

Quick and easy to implement Javascript DOM manipulation that is cross browser compatible.

jQuery is used to build a more dynamic and fun experience for the users.

jQuery is required by some of the libraries we use on the website. Other than that, having jQuery around is just great for manipulating the DOM or other common functions.

jQuery is only used in small amounts, primarily for animations and UIs, but it is included in the WSC, so we felt like not including it here would be kind of cheating. jQuery also almost makes ajax-requests a pleasure to work with, so ... you got that point, jQuery.

styles and animations

jQuery supplements our Thymeleaf HTML templates

jQuery is the perfect default client architecture for most UI design. However if there is a need to scale, Angular or Vue.js will be my alternative choice.

I use jQuery to speed up the development process of JavaScript and I love the way jQuery works.

Used on web frontend

Client-side UI rendering and AJAX requests

I use it for janky reasons when I need to fix an issue that I can't figure out how to do properly: JQuery it is!

jQuery has been the basis of our front end JS for a number of years. The key part for us was that the amount of code saved by using jQuery methods, as opposed to writing out cross-browser compatible alternatives made it a no brainer. In recent years we've had to be clever in how we deliver jQuery on the websites, to ensure it's not render blocking and improve client-side performance but it's still a vital library.

In process of Learning Technics. Cross-browser Compatibility: handles a lot of infuriating cross-browser issues . used to make some widgets and effects: jQuery plugin repository.

jQuery allows to easily do DOM scripting (i.e. HTML elements manipulation and event handling). using jquery under MVC webapps. Studing to know more

Along with Twitter Bootstrap

It's awesome to access DOM elements and modifying their properties.

Mostly with Django, sometimes with Angular/Typescript. Not a very solid knowledge, just the basics.

Simple front-end javascript

Before two weeks ago or so, it used to be Backbone views and models, and everything was on our main store app, and our mobile web app, but actually, we just switched our mobile web app to using ReactJS for the interface. So it’s using Backbone models but ReactJS front-end components. Really, it was borne out of the frustration with how the Backbone model-view bindings worked, and it wasn’t especially performant for large views, and we had to do lots of tricks to make it performant. But swapping that out with React views meant that it could be both simpler and faster without having to spend a lot of time on that.

One other interesting thing about that is, since React actually works okay with the Backbone models and the Backbone router and stuff like that, we didn’t have to rewrite the mobile web application and update it to ReactJS. Rewrites are almost always a bad idea. We were able to upgrade pieces of it at a time, move on to React, and now the entire thing is using React and just has the Backbone router and models and stuff like that that we already had, so it's a lot faster.

Display components, routing.

At the beginning of last year, Netflix UI engineers embarked on several ambitious projects to dramatically transform the user experience on our desktop and mobile platforms. Given a UI redesign of a scale similar to that undergone by TVs and game consoles, it was essential for us to re-evaluate our existing UI technology stack and to determine whether to explore new solutions. Do we have the right building blocks to create best-in-class single-page web applications? And what specific problems are we looking to solve? Much of our existing front-end infrastructure consists of hand-rolled components optimized for the current website and iOS application. Our decision to adopt React was influenced by a number of factors, most notably: 1) startup speed, 2) runtime performance, and 3) modularity.

React has exceeded our requirements and enabled us to build a tremendous foundation on which to innovate the Netflix experience.

React forms the core of the single-page application allowing us to declarative build the app in a modular way.

React is amazing for applications that have a lot of moving pieces. The underlying abstraction makes it easy to keep track of highly stateful UIs while keeping code complexity down, so we don't spend as much time fixing bugs.

Building Website UI components

Front-end components driven by server data.

React, with Om, is used for all our front-end UIs.

Our UI is built with Reagent, a ClojureScript wrapper around React, allowing us to build UI components that manage their own state instead of performing constant stateful DOM manipulations.

View components

Composition of views and higher-order components.

Web-frontend programming prior to React: like banging rocks together. With React: Like wearing fusion powered underwear. Gives you a nice warm feeling. Using React for Cloudcraft.co allowed us to create a beautiful UI in record time (1 month start to launch), with virtually no bugs popping up during development. The functional approach to just rendering your component given a state just makes so much sense, with React figuring out the delta between your current and desired representation. It's the future kids!

We use it in the majority of our webapps

Our main JavaScript front end styling and instant search.

React powers enlist's job boards.

DOM manipulation of front-end tasks.

For complex and full featured web interfaces

Our Console section uses React to create a view for each message logged from our users' devices. Each message has a different type of information, from simple strings to cookies data or DOM trees. Define each type of message declaratively eases our product's development cycle.

React is heavily used in Shimo.im. We use it in the homepage, spreadsheet and other places.

Isomorphic web app with server + client rendering

We happily use React for our Web UI

React in conjunction with RefluxJS is used to create an extendable and responsive dashboard for our clients to analyse their daily business activities in their restaurants.

Powers the UI.

React replaces front end templates and url routing usually defined in a Django project; I've found it more flexible and it's the easiest way to integrate javascript into Django to replace its templates.

Used to dynamically render Front-end by directly manipulating the DOM. Very powerful Library especially with used with Flux.

Meteor + React + Semantic-UI

All of our new product front-end code is being developed with React.

Everything is written in React. Main app, QuizWall, Landing

All frontend logic consisted of a plain React app without state management of some sort.

The vast majority of the app's frontend was built in ReactJS with Redux.js as its flux implementation.

Only for HTML-templates

다노에서 인턴기간 동안 react를 사용해 다이어트 코칭 서비스와 유저들을 관리하는 코치용 서비스를 제작하고 배포하였습니다

We're using React for our new frontend projects.

Frontend built entirely in react

I've used React for templating here because I don't like the angular brackets and react seemed like the cool thing to learn

To build user interfaces

html 코드를 짜다 보면 여러 엘리먼트를 조합해 사용하는 경우가 많은데, 이런 것은 하나로 묶어 관리 해야 하지 않을 까 했는데, 그때쯤 나온 라이브러리 이다. 프레임워크가 아니라 라이브러리라 러닝 커브가 적으나, 결국 이것 저것 필요하게 되지면서 점점 프레임워크 처럼 되어 버린다. jsx 는 정말 편리하고 가독성을 높여주는데 그것 때문에 babel 에 webpack을 써야 되는게, 정말 싫다.

React with AEM

React to HTML (https://github.com/killercentury/sc-osp-react-demo/blob/master/multi-react-components-using-es5-module.html)

HTML to React as children components (https://github.com/aknuds1/html-to-react, HTML React AEM.md)

3rd components:

• react-cookie
• react-modal
• react-slick (with slick-carousel)
• react-sticky
• react-text-truncate
• react-helmet

Ambar UI is built with React

Powers the more advanced aspects of our front-end interface, esp. the real-time inbox.

We use react to build responsive and interactive web applications on our data platform.

Favourite frontend framework. Used it in three web projects (+ one project in React Native).

a couple of years experience developing with react, mostly during my foray at talenthouse.

Components in the project are written using the React framework. React Native then takes it a step further using their native components that are interpreting as mobile views.

This is the best component framework and API available today for building modern web sites and apps. I really enjoy how minimal it is, and powerful at the same time. It removes opinionated development and replaces it with logic and data philosophies, which has in turn fostered a robust and lively code and support community.

I mostly use React via a Clojure wrapper called Reagent. Reagent is dead simple and faster than bare React is out of the box. If I have to write a UI myself, I would strongly move to use React via Reagent.

When I have to build front-page components, React helps organize the concepts behind each piece of the UI. However, I prefer to use more native approaches to building elaborate user interfaces than the web.

All UI components

Using this in combination with a whole bunch of related libraries, such as Redux.

React is choice number 1 when it comes to JS development at Kurzor. We choose React because it solves many issues with web applications in a elegant way. Writing an app in components is useful for coordination and isolation of concerns. React forces you to abandon state and use vertical passing through props instead. And having as many Pure Components as possible helps to write cleaner code.

With React we usually use: Redux, React Router, React Toolbox, Styled Components.

React is the first instance I've seen of a framework that provides truly reusable components, something I've been promised for many, many years.

"No-one got fired for buying IBM" of front-end 'frameworks', React is a view library that manipulates DOM in an efficient way. Our front-end is build around React & it's ecosystem.

Web app stuff

We use React for our front end at Binded.com.

Giving a smooth, responsive cart & checkout experience

• 간단하게 UI 구성을 해봄

Client Apps

I use React as a frontend view framework. It's not always needed, but when the UI for a site has lots of changing parts and/or interactive functionality, React makes it a lot easier to work with.

Virtual DOM, Clean state management, great dev tools, javascript at it's best

Frontend

React powers our dashboard and other front end apps.

Used in all new projects (mobile website with AZTEC scanner)

We use react on our web apps.

standard for model, view of the client side - also creating re-usable widgets (based on react)

High performance UI. WebApp.

The application is built as a single page web application using React.

Framework Javascript