Twitter | Search | |
Dan Abramov
Does anyone actually *like* React these days? 😛
Reply Retweet Like More
bootrino Jun 12
Replying to @dan_abramov
Visual Basic made easy things easy. Delphi made hard things easy. ReactJS is more like Delphi.
Reply Retweet Like
Collin Miller ❁ Jun 12
Replying to @dan_abramov
Way ahead of you, I even like redux.
Reply Retweet Like
Manfred Neustifter Jun 12
Replying to @dan_abramov
its a little complicated
Reply Retweet Like
🍂🍁Anna 🕸 Goncharova🍁🍂 Jun 12
Replying to @dan_abramov
Why would someone dislike it?
Reply Retweet Like
Dan Abramov Jun 12
Replying to @anna1go
Plenty of reasons: often associated with an ecosystem that relies on more tooling (package managers, compilers), no official prescriptions for some things (routing, file structure), a certain barrier to entry because it needs JS knowledge
Reply Retweet Like
Dan Abramov Jun 12
Replying to @SuperManfred
What do you feel could be simpler?
Reply Retweet Like
Dan Abramov Jun 12
Replying to @collintmiller
Nobody likes Redux
Reply Retweet Like
Dan Abramov Jun 12
Replying to @unikernelguru
This is actually funny because I was a VB fan back in the day
Reply Retweet Like
Dan Abramov Jun 12
Replying to @dan_abramov
Seems like there’s still plenty of you who actually like it and aren’t just forced to use it due to popularity or job market etc. 🙂 That makes me happy.
Reply Retweet Like
José Trezza Jun 12
Replying to @dan_abramov
Are you planning to replace it with something different?
Reply Retweet Like
Dan Abramov Jun 12
Replying to @jtrezza
Every release is a tiny bit different. But the spirit stays the same.
Reply Retweet Like
Dan Abramov Jun 12
Replying to @dan_abramov
If you don’t like it that’s cool too. Just drop by every now and then and tell us what we could do better?
Reply Retweet Like
Scott Cahill O'Brien Jun 12
Replying to @dan_abramov
Sniff out React lovers in two simple questions: 1. Do you have a degree in computer science? (Yes) 2. Do you enjoy writing static HTML and CSS? (No) Guaranteed React lover.
Reply Retweet Like
Pavel Tkachenko Jun 12
Replying to @dan_abramov
Major problem for me is a deploy of SPA. I still don’t know elegant solutions to refresh app on client side after successful deployment. But this more SPA problem in general, rather than React. Would be very happy if someone share some related resources.
Reply Retweet Like
Luke Jun 12
Replying to @dan_abramov
Noob question why on the react site does it teach you to do React.Component and not import React, { Component } from 'react' ?
Reply Retweet Like
Raja Rao DV Jun 12
Yes, of course, i think its a bit complicated compared to preact but I still like it
Reply Retweet Like
Alex Indigo Jun 12
Replying to @dan_abramov
It would be nice to have separate path for dependency resolution from rendering. Will be useful for server-side frameworks like nextjs and to combat double render hacks the way apollo graphql does it.
Reply Retweet Like
Ivan Babak Jun 12
Replying to @dan_abramov
Hydration of component state along with component markup to revive the app that started at the server to continue in the browser.
Reply Retweet Like
pkellner Jun 12
When you were 5?
Reply Retweet Like