Tweet

More from @dan_abramov

Dan Abramov

@dan_abramov

30 Dec 20

Where is the monument to the person who invented a pickle

Early culinary history must have been fascinating. All the heroes who got sick or died eating the wrong stuff just so we can discover the 1% of food that actually gets better after burning, freezing, crushing, or leaving it open for a week

O Brave souls who ate a thousand poisonous herbs to find the one that goes well with meat, you may be gone but not forgotten

Read 5 tweets

Dan Abramov

@dan_abramov

29 Dec 20

Funny how people don’t really know their impact on others. Like some song may be hugely personally meaningful to me but it’s just a few random streams for the artist. Or I’ve learned something from a random old comment but that commenter would say it’s silly or uninformed today.

And would they care? I don’t know. Like if I told that to some artist they’d probably feel icky and awkward. They just made a thing and they know it’s good, but they’re not responsible for my feelings. That thing has its own life now.

I think the part I tend to get wrong is projecting the awesomeness onto the person when it’s really about the work of art they’ve fished out, and my interpreting it. Stanning them might be awkward but stanning the work is not because clearly we both liked it a lot.

Read 4 tweets

Dan Abramov

@dan_abramov

27 Dec 20

I love how people watching me talk and mentioning my age or calling me a millennial straight up assume I wasn’t around when PHP, ASP .NET, or even XSLT were hype. I’m not deeply familiar with them because I mostly did desktop but I started early so I’ve seen a few things. 🙂

Here’s a challenge. When I want to tweet “X is just like Y back in the olden days” I try adding “but...” and figure out what the difference is. If I thought of a past analogy after one minute of thinking, clearly I’m not the first one to think this, and there might be more to it.

It’s easy to see the past references. They stand out, and there’s a limited number of variables to play with in the design. Some things will repeat. It’s harder to notice the new twist. Which can turn a past weakness into strength or solve a limitation.

Read 6 tweets

Dan Abramov

@dan_abramov

18 Sep 20

I was thinking about the sentiment you might see when something new is introduced. “Oh no, another thing to learn, why can’t we stop.”

And while I get the frustration I also wonder. Are there people who genuinely expect that they’ll be able to stop learning in this field?

Like, another JS library. Of course there is. Why wouldn’t there be? I would be concerned if there are no new ideas being tried. What did you expect, that there’s a limited number of things to learn and then you’re done for the rest of your career? That’s not how it works.

I think maybe the sentiment here may actually be directed against inexperienced project leads. Who might be overly tempted to jump between solutions and impose new things on their team. That can be frustrating.

Read 5 tweets

Dan Abramov

@dan_abramov

18 Sep 20

Crash 4 time squeeze gameplay is really addictive. Digging it. Like the visual style too. My only gripe is the shadow — I get that it helps placement but it almost feels like a cop-out so that the games can’t blame the collision system. “You saw where you landed!”

I so DON’T miss the “four lives and then you have to restart” mechanic. Glad they cut it.

So many subtle touches. Keeping some mechanics like you can smash a box with tnt above it. But doing away with annoying things like accidentally spinning wumpas.

Read 5 tweets

Dan Abramov

@dan_abramov

13 Sep 20

I wonder if our early messaging about Concurrent Mode should have been focused on mounts rather than updates. Some of the conversation I’m seeing assumes we could just “do less work” which is not an option for rendering *new* subscreens — where granular rerendering doesn’t help.

This depends on the app — some apps, like dataviz, almost exclusively do “updates”. So dataviz example, while effective visually, may have been a misdirection. In consumer apps a lot of the interactions we want to make smoother are mounts — like switching tabs or infinite scroll.

There’s also a question of responsibility. We consider what happens when you have hundreds of components that all run a little bit of code *our* responsibility. Userland code then dwarves library overhead in CPU time. We can’t just wash our hands and say “don’t write slow code”.

Read 7 tweets

Share this page!

Dan Abramov

Try unrolling a thread yourself!

More from @dan_abramov

Dan Abramov

Dan Abramov

Dan Abramov

Dan Abramov

Dan Abramov

Dan Abramov

Did Thread Reader help you today?

Like this author's thread?