slorber

19 ms·

1. 151.▲
   Atomic CSS-in-JS, Used by Facebook and Twitter(sebastienlorber.com)

   1 points by slorber 6y ago|0 comments
2. 152.▲
   Running Expo Inside Gatsby(twitter.com)

   1 points by slorber 7y ago|0 comments
3. 153.▲
   Handling API request race conditions in React(sebastienlorber.com)

   3 points by slorber 7y ago|0 comments
4. 154.▲
   React: most easy way to manage a spinner for a deeply nested button(github.com)

   1 points by slorber 9y ago|0 comments
5. 155.▲
   React-reboot: simplest way to update the syntax of your old React components

   3 points by slorber 9y ago|1 comments
6. 156.▲
   Rereduce: reducer library for Redux(github.com)

   2 points by slorber 11y ago|0 comments
7. 157.▲
   by slorber 11y ago

   Is the same data displayed into multiple branches of the tree? :)
8. 158.▲
   by slorber 11y ago

   Let's talk about building an app with 50 independant ScalaJs modules then and how you manage/compose them in one or many of your apps without embedding multiple times the ScalaJs runtime. Don't forget Scala is slow to compile
9. 159.▲
   by slorber 11y ago

   I agree that some points are actually valid (conceptually). However React permits to do useful compromises on purity for practicity. In Elm you have to hack the system to give the focus to a single input or use an external lib... See https
10. 160.▲
    by slorber 11y ago

    It's easy to use Redux in a composable way once you start removing imperative code in components and just make them describe what happened. Redux-saga can glue this all together. See http://stackoverflow.com/a/3458