ariabuckles

9 ms·

1. 61.▲
   by ariabuckles 11y ago

   Correct. That and passing mutable backbone models as props went poorly back when we did more of that. Mutable props are hard to reason about and go against all of the recommendations for React props. (There are plenty of good use-cases of b
2. 62.▲
   by ariabuckles 11y ago

   1. If you're not passing the backbone models to React components, this sounds fine. backbone models as props ends up being really painful because of how mutable they are, and when we tried to manage that with mixins, it was buggy and c
3. 63.▲
   by ariabuckles 12y ago

   I'm really excited for `React.cloneElement` and inlining of `React.createElement`! `React.cloneElement` makes a bunch of tricks that used to require hacks much cleaner, and finally promotes cloneWithProps to non-addon API and removes t
4. 64.▲
   by ariabuckles 12y ago

   I've been through some of this myself, and have several friends who've gone through it as well. I cannot recommend finding a good cognitive-behavioural therapist enough. Cognitive behavioural therapy with a good therapist actually
5. 65.▲
   by ariabuckles 12y ago

   Oh, I'm quite aware :). It's an effort of extreme dogfooding of https://github.com/khan/perseus . This post doesn't use anything interesting, but if I wanted to post about some of the interactive math con
6. 66.▲
   Why CommonMark Isn't the Solution(ariabuckles.github.io)

   85 points by ariabuckles 12y ago|53 comments