Share this page!

дэн Profile picture
Twitter logo
May 26, 2019 • 4 tweets • 1 min read
I don’t understand micro-frontends.
The problems they’re supposed to solve sound to me like they’re already solved by a good component model. So is this solving an organizational issue rather than technical one? Such as if two teams can’t agree on anything, even shared infra.
OK I just realized from reading the original doc that this seems to (at least partially?) be a Web Components architecture thing. Didn’t mean to enter this debate 😛
At least it’s not XSLT

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with дэн

дэн Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @dan_abramov

дэн Profile picture
Feb 13
let’s play a game. you ask me a javascript/programming question (something generic, not “help me with my project”), i try to answer/explain it in a single tweet. let’s go
gonna thread a few common ones:
1) what is "this"
2) what are closures
Read 14 tweets
дэн Profile picture
Feb 11
just spent twenty minutes debugging why this doesn't work

.something > .stuff:nth-child(0) {
/* ... */
}

can you spot the mistake?
wouldn’t it be nice if something, like, reported an error. or a warning. isn’t this, like, a baseline expectation
C in CSS stands for “the C programming language”
Read 4 tweets
дэн Profile picture
Feb 3
i think it was a good question! even if the answer was a bit predictable
of course at fb we had a dozen callers to this. some pretty hard to rip out, and it took months of effort to get them locked down and ported to other approaches. no one got fired but it’s nasty when you can’t do internal refactor because somebody added a usage 5 years ago
at one point one of my teammates who is usually very calm and composed deleted some of the internals to “send a message”, which was reverted the next day because it broke a bunch of things for different teams. we didn’t do this again but this started a conversation
Read 7 tweets
дэн Profile picture
Feb 3
we’ve been trying some tweaks to how the information is structured in the react docs beta api reference. would love to hear what you like/dislike about this useState page! beta.reactjs.org/reference/uses…
not gonna lie, i feel pretty lost about the “not api-like” feedback. i’m not sure if this is a slice of power users or representative of what we’ll hear en masse. guess i’ll try to make a dry version to feel it out.
i think the structure of the page is actually very api-like because it’s structured around different overloads and goes outside-in from the api nesting perspective. maybe the headers don’t make it obvious..
Read 7 tweets
дэн Profile picture
Feb 2
sublime text is so good. everyone’s adopting vs code, blablabla, sublime text 4 comes out and quietly fixes a bunch of shit that annoyed me and has better defaults. the only change i do now is .js > open all files as > javascript > jsx. that’s all. a beautiful piece of software.
what’s that? oh it’s just a gorgeous default theme in a minimal, light, friendly editor. nothing to see here screenshot of sublime text
sublime text is a case study in ux design so incredibly well-thought-out that most of us mortals will never — not just approach — *notice* it.

if you scroll down the sidebar to move “open files” out of sight, opening next tabs auto-adjusts sidebar scroll position to avoid jumps
Read 8 tweets
дэн Profile picture
Feb 1
how do you feel about FAQ-like page sections in technical documentation? where the information is laid out as a sequence of question headers and answers instead of a narrative flow
my personal perspective is i dislike faq as a top-level thing but i love it as a leaf thing. like “common questions about %thing%” in the reference documentation page of %thing%. headers make it highly scannable and it models how i’d ask someone instead of reading a manual. ymmv
imo “faq just means gaps elsewhere” is a weak argument. it doesn’t have to be if you close the gaps! then faq serves as a meaningful and rich in information (if it reflects real frequency) index of content elsewhere. it’s a bridge to being a power user. also people don’t read lol
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

Like this author's thread?

Get emails when @dan_abramov has new unrolls!

Check out other threads from @dan_abramov!

Read all threads by @dan_abramov

:(