spicyj

58 ms·

1. 571.▲
   by spicyj 13y ago

   Various companies (in one famous case, Twitter) have found that server rendering beats client rendering for initial rendering speed. React is designed so that if you care about server rendering, you can have the best of both worlds -- using
2. 572.▲
   by spicyj 13y ago

   (React does too.)
3. 573.▲
   by spicyj 13y ago

   > The main culprit after some rudimentary profiling seemed to be the jQuery's .html('') tag. Apparently it does some cleanup which takes awhile on a huge DOM block with lots of attached events. Replaced it with by looping
4. 574.▲
   by spicyj 13y ago

   Correct.
5. 575.▲
   by spicyj 13y ago

   This is correct. Unless you manually add code to touch the DOM in your component methods (which is rarely necessary), React only touches the DOM when it needs to mutate it and more or less does not read from it. For example, when mutating s
6. 576.▲
   by spicyj 13y ago

   React is designed so that you should never need to read from the DOM except things like an input field's value. React specifically tries to never touch the DOM except when doing necessary mutations. If you're doing complicated lay
7. 577.▲
   by spicyj 13y ago

   Wow, this looks awesome. > [x+1 for (x of @[1,2,3])] I wasn't aware Objective-C++ or JavaScript supported list comprehensions like that.
8. 578.▲
   by spicyj 13y ago

   This is cool to see. I added the React benchmark yesterday ( https://twitter.com/soprano/status/423659115743682560 ) and @ebryn updated it to compare against the Ember+HTMLBars implementation. I wanted to mention th
9. 579.▲
   by spicyj 13y ago

   GitHub acquired https://speakerdeck.com/ and as far as I can tell, has continued to improve it. I assume that they'll do the same with Easel.
10. 580.▲
    by spicyj 13y ago

    I've used React quite a bit and find React apps pretty easy to debug so I haven't felt the need for something like this, but I'm looking forward to having another tool in my belt for the next time I find myself in a confusing
11. 581.▲
    by spicyj 13y ago

    I could imagine a future version of React using self-adjusting computation like you describe.
12. 582.▲
    by spicyj 13y ago

    Yes, React's synthetic event system is supposed to bubble for focus.
13. 583.▲
    by spicyj 13y ago

    We do: https://www.khanacademy.org/donate#bitcoin Thank you.
14. 584.▲
    by spicyj 13y ago

    Sorry about that, can't edit my post any more. Mountain View, CA, but remote is a possibility for the right candidate.
15. 585.▲
    by spicyj 13y ago

    > just use jQuery's focusin/focusout to make up for the lack of bubbling focus support in React I believe the focus event bubbles just fine in React. If not, please file a bug.
16. 586.▲
    by spicyj 13y ago

    React's diff algorithm is completely deterministic. For form inputs and other components which have their own state, it's recommended to put a `key` attribute on each one so that React understands what you meant if you reorder ele
17. 587.▲
    by spicyj 13y ago

    Yes. See my response here: https://news.ycombinator.com/item?id=6995262 .
18. 588.▲
    by spicyj 13y ago

    Does this post answer any of your questions? http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-Angu... Declarative syntaxes are easier to work with because you can look at your template and see exactly what
19. 589.▲
    by spicyj 13y ago

    This is false. Although it's true that React makes the most sense when each individual component is all React, it's easy to embed small React components into a non-React application, and you can also wrap small jQuery plugins (lik
20. 590.▲
    by spicyj 13y ago

    Hi all, As you're planning your New Year's resolutions, consider: if you could work anywhere, what would you do? - Wouldn't you want to work towards really making the world a better place? - Wouldn't you want to work w
21. 591.▲
    by spicyj 13y ago

    See http://lambda-the-ultimate.org/node/4862 .
22. 592.▲
    How Salman Khan of Khan Academy hires(hbr.org)

    3 points by spicyj 13y ago|0 comments
23. 593.▲
    by spicyj 13y ago

    On non-SPDY connections, it won't be, correct? Seems like the best approach might be to simply serve different static asset URLs based on User-Agent sniffing.
24. 594.▲
    by spicyj 13y ago

    It's been good practice for years now to place static assets on a separate domain to reduce cookie traffic. In some cases, the website owner can't control which cookies are set on the root domain (e.g., Google Analytics sets cooki
25. 595.▲
    by spicyj 13y ago

    I wrote a little bit about my experiences here: http://benalpert.com/2013/06/09/using-react-to-speed-up-khan... In short, it's simple (very little to learn) and very fast. One other big thing I love is t
26. 596.▲
    by spicyj 13y ago

    As I said here the last time a new React version came out, we're using React for more or less all new JS development at Khan Academy, and we're loving it. Happy to answer questions.
27. 597.▲
    Comcast Will Spend Millions on Khan Academy for Low-Income Broadband Adoption(techcrunch.com)

    61 points by spicyj 13y ago|19 comments
28. 598.▲
    by spicyj 13y ago

    Annoying how the site creates history entries when scrolling -- would be nice if it used replaceState instead.
29. 599.▲
    by spicyj 13y ago

    It doesn't, but judging by the number of upvotes this submission has, lots of people missed it last time so perhaps it's useful to post again anyway.
30. 600.▲
    by spicyj 13y ago

    Lots of discussion from 9 days ago: https://news.ycombinator.com/item?id=6791153