9 Matching Annotations
  1. Aug 2021
    1. but in a more practical scenario, you often suffer from "death by a thousand cuts" which means that there's not really a single place that's slow, so you wind up applying React.memo everywhere. And when you do that, you have to start using useMemo and useCallback everywhere as well (otherwise you undo all the work you put into React.memo). Each of these optimizations together may solve the problem, but it drastically increases the complexity of your application's code and it actually is less effective at solving the problem than colocating state because React does still need to run through every component from the top to determine whether it should re-render. You'll definitely be running more code with this approach, there's no way around that.
  2. Dec 2020
  3. Oct 2020
    1. following address

      address --> URL か?

    2. --repo-user <repo username>

      repo user とはなんだ?

    3. ph-platform_2.0.2020102021275716537694816175_all.deb

      この細かなversionは逐次変わっていく。

      2.0.2020102021275716537694816175_all.deb

  4. Oct 2019
  5. Aug 2017
    1. An excellent meditation that brings out the problem in today's computing culture: under-representation of the minority and females in computing, starting with the students and all the way up to venture capitalists and the culture. It is interesting how Bogost talks about alternative scenarios. Looks like this is a disbalance of power.

  6. Jan 2016