Twitter | Search | |
jordwalke
Maker of things: ReactJS. Working on: . At: Facebook Engineering.
11,040
Tweets
461
Following
22,382
Followers
Tweets
jordwalke retweeted
Repl.it 11h
Introducing 's Universal Package Manager: 🔎 Search 📦 Auto-install ⚡️ Run With our common package manager abstraction it's going to be easy to add more and more language support:
Reply Retweet Like
jordwalke 4h
Replying to @JDStringfellow
I’ve never seen docs that provide both. Got an example?
Reply Retweet Like
jordwalke 5h
Replying to @mjambon
You might have meant to say “should government favor for society’s own good”.
Reply Retweet Like
jordwalke 24h
Replying to @alexeyraspopov
Style looks great on the site! Nice and minimalist.
Reply Retweet Like
jordwalke Jul 18
Replying to @jordwalke
Of course there's challenges too like making a navigation system that can scale. Increasingly easy to solve with position:sticky though, and there are existing solutions.
Reply Retweet Like
jordwalke Jul 18
Replying to @jordwalke
5. From maintainer's standpoint, no need to sign up for some service that you (might have to) pay to index your search. 6. Search works in offline mode too because you don't need to connect to a service.
Reply Retweet Like
jordwalke Jul 18
Replying to @jordwalke
4. Instantly gives you all of the docs "offline". Just keep a browser tab open or save the HTML or print to pdf.
Reply Retweet Like
jordwalke Jul 18
Hot take: Single page documentation is superior to documentation that spoon feeds three paragraphs at a time to you with prev/next pagers at the bottom. 1. Use command+f to search for things like you always do. 2. Easier to keyboard navigate. 3. Can still hyperlink to headers...
Reply Retweet Like
jordwalke retweeted
Khoa Nguyen Jul 18
Introducing ReasonML online REPL - rtop URL: GIthub: cc
Reply Retweet Like
jordwalke Jul 18
You can just dive into the Nuclide code base.
Reply Retweet Like
jordwalke Jul 18
Being unable to edit while on a flight doesn't ever become "slick" though.
Reply Retweet Like
jordwalke Jul 18
Never heard of it. It's clear the protocol should live above the fs layer and closer to the editor because it's difficult to implement all fs operations generally remote+fast+consistent, but much easier to implement higher level IDE fs features remote+fast+consistent.
Reply Retweet Like
jordwalke Jul 18
Replying to @yotambarnoy @rauchg
Another observation is that using a command line app isn't much different from chatting in a GUI chat app, but with a boring friend who always seems to want to talk about your file system.
Reply Retweet Like
jordwalke Jul 18
It's not just tests - even Flow is run on the server internally.
Reply Retweet Like
jordwalke Jul 18
It's solved by local development, which FB's internal web stack doesn't support except in the case of some more isolated projects. You can understand why due to the scale, but you could also imagine being able to develop *portions* of it locally with unit test etc.
Reply Retweet Like
jordwalke Jul 18
The downside is that it requires one specific editor, not that the editor it requires is Atom. To each their own.
Reply Retweet Like
jordwalke Jul 18
It's a really great idea though and I wish someone would generalize it to all (or more) editors because all the alternatives for remote file systems are so incredibly terrible.
Reply Retweet Like
jordwalke Jul 18
There is custom Nuclide integration to make it feel like you're editing locally so that every keystroke doesn't have to be sent across the network - it edits some local buffer that is synced with the server periodically. Only downside is that it requires Atom editor.
Reply Retweet Like
jordwalke Jul 18
Components without borders! All components should share all state with each other!
Reply Retweet Like
jordwalke Jul 18
Replying to @andrestaltz
Reason React reducers must be statically typeable and so any query selector style API is kind of a non starter.
Reply Retweet Like