8 Matching Annotations
  1. Jun 2021
    1. In the context of git, the word "master" is not used in the same way as "master/slave". I've never known about branches referred to as "slaves" or anything similar. On existing projects, consider the global effort to change from origin/master to origin/main. The cost of being different than git convention and every book, tutorial, and blog post. Is the cost of change and being different worth it? PS. My 3 projects were using your lib and got broken thanks to the renaming. PS. PS. I'm glad I never got a master's degree in college!
  2. Nov 2020
    1. However, those descriptors gave a bit too much flexibility/dynamism to the class shape in order to be efficiently optimizable.

      I think this:

      However, those descriptors gave a bit too much flexibility/dynamism to the class shape in order to be efficiently optimizable.

      means:

      However, because those descriptors were gave so much too much flexibility/dynamism to the class shape, it could not be be efficiently optimized.

      rather than:

      In order to be efficiently optimizable, those descriptors gave much flexibility/dynamism to the class shape.

      In other words that flexibility/dynamism hindered optimization; it wasn't for the purpose of optimization (as "in order to be" could be interpreted as).

      The "too much" wording also contributed to the confusion for me.

      But maybe just dropping "in order" would have been enough for me:

      However, those descriptors gave a bit too much flexibility/dynamism to the class shape to be efficiently optimizable. or However, those descriptors gave a bit too much flexibility/dynamism to the class shape for them to be efficiently optimizable.

  3. Sep 2020
  4. May 2020