249 engineers on Hacker News describe using React first-hand: 66 endorse it, 31 regret it, 20 are mixed.
“once we switched to React we actually saw improvements in many parts of the sites' loading speeds.”
endorse · production · satvikpendem · 2026-10-21 · source ↗ · wrong label?“the React-only version was incredibly slow even with carefully placed memoizations, because they were very hard to get right.”
mixed · production · molf · 2026-06-10 · source ↗ · wrong label?“I completely stick to the boring mainstream (like react) now”
endorse · production · atonse · 2026-05-30 · source ↗ · wrong label?“I've been using React since its initial release; I think both RSC and App Router are great, and things are better than ever.”
endorse · production · 12 yr · berekuk · 2025-12-12 · source ↗ · wrong label?“I've never enjoyed JSX/TSX syntax, nor appreciated the mix of markup with code, but I've subsequently learned to live with it.”
mixed · production · bartread · 2025-12-04 · source ↗ · wrong label?“I really regret the last few years of choices React has made... I still use it every day, but as soon as I find a good off-ramp for my product... I will take it.”
regret · production · pimterry · 2025-12-04 · source ↗ · wrong label?“React has its issues — notably more after exposing its internals in hooks”
mixed · production · port11 · 2025-10-17 · source ↗ · wrong label?“That's the solution I've been using for 10+ years without any problem.”
endorse · production · 10 yr · ggregoire · 2025-06-12 · source ↗ · wrong label?“I'm a bit hesitant to base our front-end on react.”
regret · production · ToJans · 2025-04-28 · source ↗ · wrong label?“After going through hell with self hosting and then their platform around version 12 we migrated away... We mostly moved away from react as a whole over time”
regret · production · no_wizard · 2025-03-23 · source ↗ · wrong label?“I've been using React templating lately, then you get a lot of cool features like Tailwind and can even use React for your email templates”
endorse · personal · welder · 2024-12-19 · source ↗ · wrong label?“when all we had to go by was the hooks api documentation in what now is the legacy documentation site”
mixed · personal · azangru · 2024-12-07 · source ↗ · wrong label?“we went off react to vanilla js, htmx and liveview type stuff which makes this all far simpler.”
regret · production · anonzzzies · 2024-12-06 · source ↗ · wrong label?“We ditched react and nextjs(broth of satan himself that it is) mostly (clients we are trying to lose)”
regret · production · anonzzzies · 2024-12-04 · source ↗ · wrong label?“the unholy React+jQuery (yes, that's a bad idea) code it replaces.”
regret · production · cies · 2024-12-04 · source ↗ · wrong label?“It loads faster than the React version and it has observably less maintenance cost.”
regret · production · 6 yr · hmeh · 2024-12-01 · source ↗ · wrong label?“I think React really helped move things forward and I don't regret my time using it.”
endorse · production · hmeh · 2024-12-01 · source ↗ · wrong label?“We’ve run React for almost a decade now and the only major parts we’ve swapped have been react build with Vite.”
endorse · production · 9 yr · devjab · 2024-10-26 · source ↗ · wrong label?“react server component is a misnomer - "use client" still does a server side render”
regret · production · theogravity · 2024-10-10 · source ↗ · wrong label?“React allows me to decouple. Templates are hell. I lived in it for many years, never again.”
endorse · production · throwaway60320 · 2024-02-23 · source ↗ · wrong label?“I convinced them to drop the react/typescript frontend for now (it was terribly bolted on)”
regret · production · berkes · 2024-02-20 · source ↗ · wrong label?“I've been developping two websites for more than a year, both pure react web apps, one of them having millions of users per year.”
mixed · production · maelito · 2024-01-04 · source ↗ · wrong label?“before transitioning to the React world. I LOVE it, but the jobs are all gone now”
endorse · production · solardev · 2023-12-28 · source ↗ · wrong label?“Eventually we replaced Manage Listing backbone views with React components one by one until there was no backbone left.”
endorse · production · jitl · 2023-11-27 · source ↗ · wrong label?“I'm liking RSC and server actions”
endorse · production · jitl · 2023-10-28 · source ↗ · wrong label?“When we switched all greenfield JS development from Closure to React around 2016, it resulted in a 2-3x speed-up in the development process.”
endorse · production · jawns · 2023-09-28 · source ↗ · wrong label?“we were willing to put up with shortcomings like being forced into a SPA, CSS-in-JS, etc.”
mixed · production · Brendinooo · 2023-05-23 · source ↗ · wrong label?“I chose React because AngularJS was horrible”
endorse · production · d0100 · 2023-05-23 · source ↗ · wrong label?“I lead a 4 dev team working with a React codebase of 80k LoC for 2 years. Hooks' lack of orchestration mechanism, props drilling and its quirks”
regret · production · 2 yr · batmansmk · 2023-03-23 · source ↗ · wrong label?“I worked with class components first. Built a whole app in them. Now we've migrated to functional and I look back at the class based ones”
endorse · production · Aeolun · 2023-03-16 · source ↗ · wrong label?“To be fair, React's simplicity does make it eminently typeable, this is more of a code-stylistic issue.”
mixed · production · evnp · 2022-12-25 · source ↗ · wrong label?“at work we use React... React has many benefits for large, diverse teams, but performance is not one of them; it has many performance footguns”
mixed · production · leeoniya · 2022-12-17 · source ↗ · wrong label?“almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”
regret · production · just_a_username · 2022-12-15 · source ↗ · wrong label?“It has simplified our development tremendously from ClojureScript / React to vanilla Clojure on the backend”
regret · production · silver-arrow · 2022-12-14 · source ↗ · wrong label?“I almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”
regret · production · azangru · 2022-12-06 · source ↗ · wrong label?“I've become very used to declarative programming after sinking my teeth into React.”
mixed · personal · SeanAnderson · 2022-11-12 · source ↗ · wrong label?“Eventually React came out and I started experimenting with it and I thought it was revolutionary.”
endorse · personal · ggregoire · 2022-09-09 · source ↗ · wrong label?“the biggest perf improvement we realized was when we switched from React to Preact.”
regret · production · vijaybritto · 2022-09-07 · source ↗ · wrong label?“I've used it in prod for multiple years, but it does get slow at times due to too much CPU spent running vdom diff on large trees.”
mixed · production · 2 yr · nojvek · 2022-07-31 · source ↗ · wrong label?“Last six months with my last employer I spent immersed in the full Next, React, Prisma ecosystem. I swear that 80% of developers' time was wasted”
regret · production · 0.5 yr · abraxas · 2022-07-02 · source ↗ · wrong label?“I have been using React and React Native for 5 years and noticed that a lot of developers are complaining that it's hard to learn.”
mixed · production · 5 yr · aartem · 2021-12-22 · source ↗ · wrong label?“I have been using it for years and I have never enjoyed it.”
regret · production · stopcraeting · 2021-12-20 · source ↗ · wrong label?“We threw out our React front end and don't miss it at all.”
regret · production · janglezz · 2021-12-11 · source ↗ · wrong label?“We migrated a huge/complex React app in a month and the difference is night and day... React was great but it's time to move on.”
mixed · production · sxiao · 2021-11-11 · source ↗ · wrong label?“performance of tree diffing was not acceptable (especially in Safari) so we replaced whole text component with manually managed DOM”
mixed · production · szastamasta · 2021-10-20 · source ↗ · wrong label?“Since React Hooks & TypeScript, my component library lost about 40% of the LOC (after adding type definitions), looks much prettier”
endorse · production · nawgz · 2021-10-19 · source ↗ · wrong label?“We switched to React in 2015 and never looked back once.”
endorse · production · 6 yr · emteycz · 2021-10-10 · source ↗ · wrong label?“Agreed. Same here. It's wonderful. In particular Mobx.”
endorse · production · drewpc · 2021-09-21 · source ↗ · wrong label?“the only ones to break a 8/10 rating among 500+ users are based on angular, react, electron or vue.”
regret · production · moksly · 2021-09-09 · source ↗ · wrong label?“We have fewer bugs than we did with React, and we ship things about 3 times faster.”
regret · production · hpvic03 · 2021-01-15 · source ↗ · wrong label?“I have React apps in production that are blazing fast, and I have seen many others in the wild.”
endorse · production · arcturus17 · 2020-12-23 · source ↗ · wrong label?“I have barely used it in three years pushing React to production, even when I used classes”
endorse · production · 3 yr · arcturus17 · 2020-12-21 · source ↗ · wrong label?“React and many libraries built on it have ridiculously complex types. That's not because of TS but interacting with and satisfying those types at compile time is extremely frustrating”
regret · production · eyelidlessness · 2020-12-08 · source ↗ · wrong label?“We've switched to Svelte for new projects at work, from React. It feels like a significant improvement, especially regarding unnecessary complexity and verbosity.”
regret · production · erokar · 2020-12-03 · source ↗ · wrong label?“We've switched from React to Svelte at work. ... so much feels needlessly overengineered with awkward APIs.”
regret · production · erokar · 2020-10-27 · source ↗ · wrong label?“Our code was a spaghetti mess without components, so eventually we moved to React (2015?).”
endorse · production · rileytg · 2020-07-01 · source ↗ · wrong label?“Overall I feel that React is the best tech for building frontends that we have so far”
endorse · production · 1.5 yr · lukevp · 2020-06-18 · source ↗ · wrong label?“Since then the productivity of the team has noticeably increased. Even new hire "ramp up" has been reduced with them producing production code faster”
endorse · production · yazaddaruvala · 2020-04-29 · source ↗ · wrong label?“As someone who has been using React for five years and especially liked it for its simple class API to write components”
mixed · personal · 5 yr · 2Pacalypse- · 2019-12-25 · source ↗ · wrong label?“I'm not sure I would pick React for an SEO driven website. It is hard to get a competitive "time to first byte".”
regret · production · todd3834 · 2019-12-22 · source ↗ · wrong label?“when I worked on webapps using Node.JS and React. The last few startups I worked at we had a bug in production at least once a week”
regret · production · alexmingoia · 2019-12-03 · source ↗ · wrong label?“Between TypeScript, React, and styled components, I've come to find it extremely enjoyable to build interesting and complex things for the browser.”
endorse · personal · sickcodebruh · 2019-11-29 · source ↗ · wrong label?“after adding a single new app my boss hated the syntax and we switched to Vue.”
regret · production · merpnderp · 2019-10-03 · source ↗ · wrong label?“We ended up going with React/Jest/Puppeteer, but this meant we (meaning, I) had to write 150 lines of boilerplate”
endorse · production · howdydoo · 2019-09-27 · source ↗ · wrong label?“moved the majority of the SaaS elements ... to React and used Rails as our backend because this provided a much better user experience.”
endorse · production · chptung · 2019-02-09 · source ↗ · wrong label?“it will make your client bundles more complex”
mixed · production · jypepin · 2019-01-20 · source ↗ · wrong label?“I've been writing React code for years now... I couldn't imagine doing the same with React.”
regret · production · sergiotapia · 2018-12-26 · source ↗ · wrong label?“luckily we've moved to React and distributed some things on AWS and we've been much better off.”
endorse · production · simpsn · 2018-10-15 · source ↗ · wrong label?“We switched to React and never looked back.”
endorse · production · huy-nguyen · 2018-06-02 · source ↗ · wrong label?“React and TypeScript are actually a slightly awkward fit, because React's component classes and idiomatic HOCs are quite difficult to type correctly”
mixed · production · dgreensp · 2018-05-18 · source ↗ · wrong label?“speaking as someone who's done React for a couple years now and had to port old rails codebases to api-only / react views”
endorse · production · 2 yr · rublev · 2018-04-12 · source ↗ · wrong label?“When we switched productivity went through the roof and the site rendered faster.”
endorse · production · throwaway2016a · 2018-01-11 · source ↗ · wrong label?“I've been using react and redux a lot lately, and the design patterns make the code much easier to debug”
endorse · personal · jorjordandan · 2017-12-25 · source ↗ · wrong label?“we use React+mobx on both our web and RN stacks and it's been great.”
endorse · production · tmail21 · 2017-12-24 · source ↗ · wrong label?“When I was using a JS framework, the refactoring was so painful I seriously considered throwing the whole thing out”
regret · production · git-pull · 2017-12-24 · source ↗ · wrong label?“introducing React ironically helped reduce the file size... So based on how the announcements were made... React seemed the safer bet.”
endorse · production · pluma · 2017-12-07 · source ↗ · wrong label?“After seeing React upgrade the entire library to v16 to enable entirely new use cases, without breaking the API... That's in production right now”
endorse · production · ENGNR · 2017-11-28 · source ↗ · wrong label?“My three biggest gripes with React are solved with Vue”
regret · production · kendallpark · 2017-11-16 · source ↗ · wrong label?“I've been using React with MobX and Typescript for the past year in production and it's been treating me and my team very well.”
endorse · production · 1 yr · buttminer · 2017-11-16 · source ↗ · wrong label?“I use React daily, and the whole experience has been extremely pleasant.”
endorse · production · computerex · 2017-11-10 · source ↗ · wrong label?“For me personally it's to a React/RxJS front-end stack... it's a much more stable, decoupled and scalable stack.”
endorse · production · Blixs · 2017-11-04 · source ↗ · wrong label?“TL;DR we switched to react because 1. react is small (codebase wise) 2. react community is wide 3. react + redux = love.”
endorse · production · melicerte · 2017-09-20 · source ↗ · wrong label?“constant breaking changes are just taking too much time away from development time, so it's not a good fit for our project”
regret · production · whostolemyhat · 2017-09-20 · source ↗ · wrong label?“I think I am overall perhaps more productive with React than Angular... less issues with state management in Angular, which has been a pita in React”
mixed · production · Bahamut · 2017-08-19 · source ↗ · wrong label?“having used React productively for a couple of years now, I don't really see much point in throwing out something that works well”
endorse · production · 2 yr · steve_taylor · 2017-05-28 · source ↗ · wrong label?“it's still possible to use React in prod without Webpack and Babel. We're adding a couple new features to an existing ES5/Backbone app”
endorse · production · acemarke · 2017-03-23 · source ↗ · wrong label?“now is exactly when we will start seeing the problems with mingling code + UI as the code gets forgotten, opened again, modified, added to and bloats.”
regret · production · mattmanser · 2016-12-20 · source ↗ · wrong label?“It's actually one of the simplest, cleanest and most completely specified interfaces of any modern JS UI library or framework, in my experience.”
endorse · production · Chris_Newton · 2016-12-20 · source ↗ · wrong label?“I've been able to accomplish 90% of what I could do in Angular, using React, React Router and Fetch API.”
endorse · production · joshmanders · 2016-12-11 · source ↗ · wrong label?“I love React, I'm bullish on React-Native as well for a lot of use cases.”
endorse · production · mikeryan · 2016-11-16 · source ↗ · wrong label?“where we migrated some components to react and keep the rest using jQuery”
endorse · production · simion314 · 2016-11-06 · source ↗ · wrong label?“React can be fun to learn in the beginning but over time it does cause a lot of fatigue”
regret · production · jaequery · 2016-10-30 · source ↗ · wrong label?“In the end we chose React due to the wonderful combination between it and TypeScript.”
endorse · production · teniutza · 2016-10-21 · source ↗ · wrong label?“these modern javascript tools have solved a lot of problems we had.”
endorse · production · mehwoot · 2016-10-04 · source ↗ · wrong label?“it FEELS like we have some really good, reusable components that will save us lots of time going forward”
mixed · production · 0.5 yr · yawgmoth · 2016-08-14 · source ↗ · wrong label?“Having simple and easy to create components is a major win.”
endorse · production · merpnderp · 2016-03-01 · source ↗ · wrong label?“I've been using it now for just over a year, and it feels like I should have been building applications like this all along.”
endorse · production · 1 yr · stuartleigh · 2015-07-23 · source ↗ · wrong label?“I've been using a lot of it lately... the front-end took maybe 20 minutes: no fishing around for the right selector or clashing functions.”
endorse · personal · arenaninja · 2015-07-09 · source ↗ · wrong label?“I've been using React for a year and a half, and it's probably the first thing in the JavaScript ecosystem for a long time”
endorse · personal · 1.5 yr · andrewingram · 2015-07-04 · source ↗ · wrong label?“I've done a bit with react in cordova as well and found similar problems.”
mixed · personal · agmcleod · 2015-07-03 · source ↗ · wrong label?“I have to say, the combination is magnificent for productivity.”
endorse · personal · liamzebedee · 2015-07-01 · source ↗ · wrong label?“the new version is a fully isomorphic React and Flux (Flummox) application. Working on it has been great”
endorse · production · girvo · 2015-06-27 · source ↗ · wrong label?“I use it at work and for personal projects. It's great, creating sophisticated interactions is a lot simpler with flux and react.”
endorse · production · TheAceOfHearts · 2015-06-21 · source ↗ · wrong label?“I've been using React a good bit lately and it's fun to use. Overall I'd say I'm happy working with it and Flux.”
endorse · personal · bwilliams · 2015-06-21 · source ↗ · wrong label?“it is the most helpful and pleasant JavaScript technology I've ever used”
endorse · production · guscost · 2015-06-21 · source ↗ · wrong label?“we've moved to React, and JQuery was included from day one.”
endorse · production · tyleregeto · 2015-02-27 · source ↗ · wrong label?“a mix of jQuery and React for the front end and couldn't be happier.”
endorse · production · ssiddharth · 2014-12-31 · source ↗ · wrong label?“Since I have been using React.js, my opinion has changed 100% -- and I realized that the supposed "separation of concerns" that drove us to template languages”
endorse · personal · 1 yr · reverius42 · 2014-12-23 · source ↗ · wrong label?“I'm having a lot of fun with React (with Backbone-based stores), and it just feels right after all of that.”
endorse · production · btown · 2014-12-20 · source ↗ · wrong label?“I've been using React and Webpack to build the clientside of my Rails apps and have been very happy with that approach.”
endorse · personal · picardo · 2014-11-29 · source ↗ · wrong label?“As someone who has been using React on a daily basis for the last few months, I have a severe man-crush on it.”
endorse · production · 0.25 yr · DigitalSea · 2014-11-26 · source ↗ · wrong label?“I've been using and enjoying React and am excited to learn more about Reagent.”
endorse · personal · arms · 2014-11-26 · source ↗ · wrong label?“I've been using ReactJS since it came out as tech lead on small teams, and it was not without challenges to get an OOP trained team to use React well”
mixed · production · 1 yr · dustingetz · 2014-11-24 · source ↗ · wrong label?“thanks to React & Flux I'm building a large scale web app without jQuery for the first time in my life”
endorse · production · juriga · 2014-08-21 · source ↗ · wrong label?“most of our frontend is now using React ... we're really happy with it. We have about 750 React components”
endorse · production · spicyj · 2014-07-17 · source ↗ · wrong label?“it definitely does make for code which is easy to reuse and reason about.”
endorse · personal · 0.25 yr · tomhallett · 2013-12-30 · source ↗ · wrong label?“If we run into a case where we're not seeing an outstanding return on that investment, we just use React's supported optimization hooks”
endorse · production · jordwalke · 2013-07-18 · source ↗ · wrong label?“the team started off composed by a bunch of TypeScript/React/Node developers”
neutral · production · dminik · 2026-07-16 · source ↗ · wrong label?“We're now migrating to React, but have some very large Elm projects still in prod.”
neutral · production · k_bx · 2026-07-06 · source ↗ · wrong label?“We are already in the works of removing 2: backoffice software that we moved to an in house react app”
neutral · production · tossandthrow · 2026-05-02 · source ↗ · wrong label?“In my dayjob as a (mostly react) freelance contractor doing B2B and LoB apps”
neutral · production · littlecranky67 · 2025-12-29 · source ↗ · wrong label?“I work regularly with Go, React, TypeScript, and I don't miss VSCode.”
neutral · production · srfrog · 2025-12-16 · source ↗ · wrong label?“I already know React, I'm quite familiar with prisma.js.”
neutral · personal · esperent · 2025-12-05 · source ↗ · wrong label?“I have a .NET/React/Vite webapp that despite the typical stack has a lot of very specific business logic for a real world niche.”
neutral · production · ewoodrich · 2025-12-03 · source ↗ · wrong label?“We ditched classes in React because someone didn't bind a handler. Now we have hooks with a ton of best practices.”
neutral · production · efortis · 2025-11-30 · source ↗ · wrong label?“forcing us to build a React frontend. This introduced the exact split-stack complexity”
neutral · production · ryanrasti · 2025-10-17 · source ↗ · wrong label?“I run 6 React apps in prod, which used to consume APIs written with Falcon, Django and FastAPI.”
neutral · production · ggregoire · 2025-10-10 · source ↗ · wrong label?“Honestly, from a person who has been part of both React and Svelte, this feels like the bastard child of both.”
neutral · production · h4ch1 · 2025-09-02 · source ↗ · wrong label?“our app is largely built like a standard React app”
neutral · production · jhaile · 2025-09-02 · source ↗ · wrong label?“I picked up an old JS project that had several developers fail over weeks to upgrade to newer versions of react. But I got it done in a day”
neutral · production · wordofx · 2025-09-01 · source ↗ · wrong label?“Angular/Vue/React on the front end before this.”
neutral · production · hnurl · 2025-07-18 · source ↗ · wrong label?“We started prototyping in-house dashboards using React with libraries like D3.js, Visx, and Recharts.”
neutral · production · matthewhefferon · 2025-05-20 · source ↗ · wrong label?“Decided against it in favor of a React frontend.”
neutral · production · stickfigure · 2024-12-24 · source ↗ · wrong label?“When I started working on a React app years ago every state management package I saw was filled with it”
neutral · production · Rohansi · 2024-12-05 · source ↗ · wrong label?“It's the best way to use React, by far.”
neutral · production · 0xblinq · 2024-12-04 · source ↗ · wrong label?“then use React through Inertia.js.”
neutral · production · 0xblinq · 2024-12-04 · source ↗ · wrong label?“we replaced a super messy hotwire/stimulus frontend with Inertia+React”
neutral · production · 0xblinq · 2024-09-07 · source ↗ · wrong label?“expected everyone, who already had a full time job working on their main product, to also be a full stack react+flask dev on the side”
neutral · production · 1.5 yr · al_borland · 2024-08-08 · source ↗ · wrong label?“I also helped out with friend startup which is using React + .Net REST API backend”
neutral · personal · stackskipton · 2024-05-16 · source ↗ · wrong label?“even though our frontend used React and JS exclusively”
neutral · production · solardev · 2023-12-26 · source ↗ · wrong label?“It takes some time to import all the React components I need but once you do”
neutral · production · ryscheng · 2023-12-20 · source ↗ · wrong label?“it really can have hand written react and Plasmic generated react live by side”
neutral · production · 0.25 yr · addisonj · 2023-12-19 · source ↗ · wrong label?“I've been using React for a couple of years and tend to stick with Next.js if I have a choice.”
neutral · production · 2 yr · nathan_tarbert · 2023-12-11 · source ↗ · wrong label?“We use Django Channels for WebSocket support, DRF for APIs, and ReactJS for the frontend.”
neutral · production · ajhai · 2023-12-04 · source ↗ · wrong label?“JavaScript (both Node and browser, sometimes React)”
neutral · production · mbork_pl · 2023-12-02 · source ↗ · wrong label?“then Webpack and React.”
neutral · production · erikpukinskis · 2023-11-11 · source ↗ · wrong label?“we have a separate UI created with React that pulls NixOS configuration declarations”
neutral · production · Jhsto · 2023-09-10 · source ↗ · wrong label?“We love tremor as it perfectly fits into our React/Tailwind setup.”
neutral · production · mdeichmann · 2023-08-29 · source ↗ · wrong label?“I learnt building in it after experience in react.”
neutral · personal · YetAnotherNick · 2023-06-25 · source ↗ · wrong label?“We picked Flow because we were using React, and Flow was from Facebook.”
neutral · production · brundolf · 2023-03-16 · source ↗ · wrong label?“My chosen stack is React (DaisyUI, deployed with cloudflare) + Node”
neutral · personal · lightning19 · 2023-03-11 · source ↗ · wrong label?“we switched a couple of legacy react apps to SSR with it and it was super easy”
neutral · production · kkarimi · 2023-01-24 · source ↗ · wrong label?“Learned React and a few other tools after that, tried to be a consultant for a year.”
neutral · personal · yawnxyz · 2023-01-22 · source ↗ · wrong label?“Been using preact/react since 2016”
neutral · personal · 6 yr · devmunchies · 2022-12-25 · source ↗ · wrong label?“return React.createElement(..., ...merged props..., ...children...)”
neutral · production · bnert · 2022-12-15 · source ↗ · wrong label?“I'm a React expert, but whenever I can I choose Svelte”
neutral · production · nathias · 2022-12-14 · source ↗ · wrong label?“the one person who is really good at React can take a vacation or a sickday”
neutral · production · devjab · 2022-12-14 · source ↗ · wrong label?“We use SPAs and a pretty strict typescript/react stack.”
neutral · production · _gabe_ · 2022-12-10 · source ↗ · wrong label?“I've used React, Vue, Elm, Vanilla JS, and some legacy JQuery in production over my last three years of work”
neutral · production · 3 yr · naet · 2022-12-10 · source ↗ · wrong label?“for .NET we use Microsoft's style guide for React we use Facebook's, etc.”
neutral · production · throw1234651234 · 2022-12-06 · source ↗ · wrong label?“we use lenses in react/typescript together with jotai atoms to express data paths in complex structures.”
neutral · production · valyagolev · 2022-12-06 · source ↗ · wrong label?“eventually learned to just use the tools I knew (react, node, postgres)”
neutral · personal · rozenmd · 2022-11-20 · source ↗ · wrong label?“React came along and we replaced Angular.”
neutral · production · elt · 2022-08-02 · source ↗ · wrong label?“We migrated from React to Svelte because of two reasons: (1) speed”
neutral · production · abidlabs · 2022-06-23 · source ↗ · wrong label?“The stack is ASP.NET Core with .NET 6 on the backend, React on the frontend, Postgres as the database.”
neutral · personal · romanhn · 2022-06-01 · source ↗ · wrong label?“Our React app just uses a simple home-rolled set of keys in localStorage; we have a "secret" route”
neutral · production · outsidetheparty · 2022-01-28 · source ↗ · wrong label?“We migrated the front-end to React eventually.”
neutral · production · ss108 · 2021-12-28 · source ↗ · wrong label?“Many of the React libraries that I use already have bindings”
neutral · production · jordanmarr · 2021-12-21 · source ↗ · wrong label?“I've been using a weird implementation of useReducer() (most commonly suggested on SO) but extendState() is a more elegant solution.”
neutral · personal · mattwad · 2021-12-17 · source ↗ · wrong label?“I was much more comfortable in React”
neutral · production · scottc · 2021-12-16 · source ↗ · wrong label?“I've been using them at works for years.”
neutral · production · lwouis · 2021-12-15 · source ↗ · wrong label?“We use it with Angular for our web application and with Gatsbyjs/React for our production website.”
neutral · production · Yabood · 2021-12-09 · source ↗ · wrong label?“The video designing process is a React app that leverages a Ruby on Rails based backend API.”
neutral · production · rememberlenny · 2021-12-06 · source ↗ · wrong label?“implementing it in a React/Redux/RTK Query app”
neutral · personal · joekrill · 2021-11-24 · source ↗ · wrong label?“I completely stopped using React”
neutral · production · jonathan-adly · 2021-11-23 · source ↗ · wrong label?“Finally we decided to rewrite it again with React. A lot of Python in the backend.”
neutral · production · massiarri · 2021-10-18 · source ↗ · wrong label?“For our quite big JS codebase on React + typescript, we switched from Webpack to esbuild earlier this year.”
neutral · production · Zarkaos · 2021-10-14 · source ↗ · wrong label?“and then React (a 1 year experiment, 2018-2019).”
neutral · production · 1 yr · pixelmonkey · 2021-08-10 · source ↗ · wrong label?“doing something modern with React or Angular. The JWT is stored in JS.”
neutral · production · deviledeggs · 2021-07-04 · source ↗ · wrong label?“now we are onto React and storybook and several other tools that help us build better software.”
neutral · production · apineda · 2021-06-27 · source ↗ · wrong label?“we tried most of it, from vanilla JS, over Backbone+Marionette through React, Angular 1 - ?? and Vue.”
neutral · personal · cygned · 2021-04-05 · source ↗ · wrong label?“We've been working with clojure/java/react/typescript.”
neutral · production · throw20210211 · 2021-02-11 · source ↗ · wrong label?“I've been deploying reasonably complex React apps since its inception”
neutral · production · 8 yr · kingdomcome50 · 2021-02-04 · source ↗ · wrong label?“Even where I work now, its all about speed to market. Get it working, release it... they got a janky ReactJs app for users to use”
neutral · production · at-fates-hands · 2020-11-19 · source ↗ · wrong label?“We also use F# for two react front ends with fable (F# to JS compiler).”
neutral · production · JaggerJo · 2020-11-03 · source ↗ · wrong label?“Angular with TypeScript, React (and that whole ecosystem)”
neutral · personal · alasdair_ · 2020-05-16 · source ↗ · wrong label?“Huge react app veteran lead syatem designer here.”
neutral · production · valand · 2020-01-01 · source ↗ · wrong label?“return a dangerous HTML string from a component instead of a tree of React nodes”
neutral · production · eliseumds · 2019-12-31 · source ↗ · wrong label?“As someone who has web apps in production written in backbone.js, Angular, and React”
neutral · production · adatavizguy · 2019-12-21 · source ↗ · wrong label?“I am in a big react SPA right now, that also uses TypeScript”
neutral · production · bryanrasmussen · 2019-12-19 · source ↗ · wrong label?“I've been using React for a year or two, and I thought it's my holy grail for frontend.”
neutral · personal · 2 yr · wiradikusuma · 2019-12-11 · source ↗ · wrong label?“get around Asciinema's weird support for React”
neutral · production · eatonphil · 2019-12-10 · source ↗ · wrong label?“my auth library failing when backed by a more modern React”
neutral · personal · the_other · 2019-12-05 · source ↗ · wrong label?“Almost constantly we run into a problem where a third party React library gets us 80% of what we want”
neutral · production · ng12 · 2019-11-26 · source ↗ · wrong label?“We run a React SPA, and our backend for initial page load & API is in PHP.”
neutral · production · charrondev · 2019-10-20 · source ↗ · wrong label?“I'm in a React team that was doing BEM via Sass for a few years.”
neutral · production · steve_taylor · 2019-06-17 · source ↗ · wrong label?“I work on a specialized React interface that's effectively a full-on IDE in the browser.”
neutral · production · _bxg1 · 2019-04-25 · source ↗ · wrong label?“plus the react binding necessary to attach this to the approve button.”
neutral · production · eqdw · 2019-01-14 · source ↗ · wrong label?“We've written our own blue-green deployment scripts for Spring Boot, Node.js/React/Vue, and Python.”
neutral · production · karmakaze · 2018-12-30 · source ↗ · wrong label?“There's a React team. I'm on that team. We develop React. Facebook uses it all over the place.”
neutral · production · danabramov · 2018-12-29 · source ↗ · wrong label?“we have EnhancedButton, which gets 'block' boolean prop to make it full-width.”
neutral · production · mp3k · 2018-12-26 · source ↗ · wrong label?“The FrontEnd is built on React and jQuery (for the static pages).”
neutral · production · sinstein · 2018-12-26 · source ↗ · wrong label?“Started off the year with React, like others have mentioned in this thread”
neutral · personal · dave7 · 2018-12-24 · source ↗ · wrong label?“I also keep playing with React on the side but haven't gotten very far in my understanding”
neutral · personal · bowlich · 2018-12-23 · source ↗ · wrong label?“has been great while i've been leaning React this year.”
neutral · personal · 1 yr · diesal11 · 2018-12-14 · source ↗ · wrong label?“Our agency most mostly does SaaS apps. We use Rails and React.”
neutral · production · InGodsName · 2018-12-11 · source ↗ · wrong label?“We build our apps with React, then we use React Router to match routes on the server”
neutral · production · migueloller · 2018-12-05 · source ↗ · wrong label?“Written in React, developed with Storybook.”
neutral · production · keremkazan · 2018-12-05 · source ↗ · wrong label?“Even the tools we use to make web parts now are React, Yeoman, webpack, Yarn, Sass etc.”
neutral · production · grumblepeet · 2018-12-04 · source ↗ · wrong label?“We have a similar problem at my company that we build our frontend React code for the browser and for node”
neutral · production · skrebbel · 2018-11-05 · source ↗ · wrong label?“simply renders a React app that communicates with our API server”
neutral · production · Zimbleton · 2018-09-26 · source ↗ · wrong label?“I'm a ReactJS developer by trade, but when doing side projects, I still use jQuery from time to time”
neutral · production · Secretmapper · 2018-08-19 · source ↗ · wrong label?“recently we've moved to doing more client-side programming in React”
neutral · production · adimitrov · 2018-04-24 · source ↗ · wrong label?“I've been using React for 4 years and never used observables, what do you mean?”
neutral · production · 4 yr · andrewingram · 2017-12-24 · source ↗ · wrong label?“If any major/breaking version of react/django/drf comes out, we pause and update the tech stack.”
neutral · production · bkovacev · 2017-12-19 · source ↗ · wrong label?“now that we've switched from backbone to react, suddenly it's ok.”
neutral · production · dsego · 2017-12-17 · source ↗ · wrong label?“we wanted to produce react/graphql projects quickly.”
neutral · production · parris · 2017-12-14 · source ↗ · wrong label?“Everything is server-side rendered React.”
neutral · production · dfcowell · 2017-12-09 · source ↗ · wrong label?“The frontend was built using ReactJS and Relay.”
neutral · production · leetbulb · 2017-12-05 · source ↗ · wrong label?“I'm 100% node/react/etc”
neutral · personal · MentallyRetired · 2017-11-30 · source ↗ · wrong label?“switching from Flux to Redux for our React app... we even used PureScript for a bit”
neutral · production · BalinKing · 2017-11-24 · source ↗ · wrong label?“having used Vue in production for over a year and React on personal projects, they are incredibly similar.”
neutral · personal · wcarron · 2017-11-16 · source ↗ · wrong label?“Built this game in React in ~ 20 hrs.”
neutral · personal · pcmaffey · 2017-10-31 · source ↗ · wrong label?“its focus on React makes it of little help for client<->server comms in vanilla JS”
neutral · production · e1g · 2017-10-26 · source ↗ · wrong label?“having used in prod vanilla, jquery, react, angular and Vue”
neutral · production · sametmax · 2017-09-20 · source ↗ · wrong label?“we did fast sessions learning by using ES6 and react”
neutral · personal · netdur · 2017-08-19 · source ↗ · wrong label?“We've switched to Typescript for our React projects”
neutral · production · dfcowell · 2017-08-09 · source ↗ · wrong label?“The performance difference between dev and prod builds of React is significant in my experience. In tests of an animated interface”
neutral · production · Androider · 2017-08-01 · source ↗ · wrong label?“the front end has been transitioning towards being more react based”
neutral · production · nstart · 2017-07-05 · source ↗ · wrong label?“At that point we switched to React.”
neutral · production · erichmond · 2017-06-30 · source ↗ · wrong label?“Other than that, I'm learning React and looking into options”
neutral · personal · Jugurtha · 2016-12-29 · source ↗ · wrong label?“I also use it with React, but it took me some time to set it up properly.”
neutral · production · cygned · 2016-12-22 · source ↗ · wrong label?“When I switched to React over a year ago I had to learn a lot to fit all the pieces of the puzzle together.”
neutral · production · 1 yr · mariusandra · 2016-12-11 · source ↗ · wrong label?“I tried making a React app but Chromium on the Raspberry Pi 2 is laggy”
neutral · personal · mbrock · 2016-12-02 · source ↗ · wrong label?“As someone who is deep into fancy Javascript stuff (React/Redux/Webpack you name it)”
neutral · production · borplk · 2016-10-11 · source ↗ · wrong label?“I've done large apps in Angular (which nearly made me regret choosing programming as a profession), React, Backbone”
neutral · production · rlander · 2016-09-30 · source ↗ · wrong label?“At my current workplace we're using React and BEM for CSS.”
neutral · production · ergothus · 2016-01-12 · source ↗ · wrong label?“We also use React, so movement of the selection box created events that generally had to flow through multiple react elements.”
neutral · production · bjterry · 2016-01-09 · source ↗ · wrong label?“This is what you end up dealing with when using ES6 + React”
neutral · production · yogthos · 2015-12-25 · source ↗ · wrong label?“we switched to React at my company.”
neutral · production · mercurial · 2015-12-16 · source ↗ · wrong label?“I've been using react with reflux, reflux is an excellent implementation of the flux model.”
neutral · production · bluejekyll · 2015-07-29 · source ↗ · wrong label?“I got my first impression of React/Flux from a project that was already using it (Redux) in production”
neutral · production · k__ · 2015-07-29 · source ↗ · wrong label?“I do most of my backend programming in Python (Flask) and have been using React for the front.”
neutral · production · izyda · 2015-07-24 · source ↗ · wrong label?“If you're using React and need DnD in your app... I've been using it exclusively in a complex react app for the past 3 months”
neutral · personal · 0.25 yr · krat0sprakhar · 2015-07-20 · source ↗ · wrong label?“a recent project where I got to work with React directly.”
neutral · production · okal · 2015-06-29 · source ↗ · wrong label?“open source parts of the React-based editor we use to develop PlanOut experiments at Facebook.”
neutral · production · ebakshy · 2014-12-13 · source ↗ · wrong label?“a green field project using flux/react server and client”
neutral · production · tracker1 · 2014-11-13 · source ↗ · wrong label?“I'm by no means an Angular fan (similar to the author I use Closure Tools and React where I can)”
neutral · production · rhofmeyr · 2014-10-07 · source ↗ · wrong label?