25 Matching Annotations
  1. Aug 2024
  2. Feb 2023
    1. Despite the crudeness of his experimental setup 500 years ago, da Vinci, Dr. Gharib said, was able to calculate the gravitational constant to an accuracy within 10 percent of the modern value.

      Nearly a hundred years before Galileo and two hundred years before Newton, in a series of diagrams and notes in the Codex Arundel, Da Viinci was able to calculate the gravitational constant to an accuracy within 10 percent of the accepted value.

    1. ~ is a dimensional constant, called Planck’s constant, the value of whichdepends on what units one uses for time and for energy. It has the dimensions[energy] · [time] and its experimental values are1.054571726(47) × 10−34Joule · seconds = 6.58211928(15) × 10−16eV · seconds(eV is the unit of “electron-Volt”, the energy acquired by an electron movingthrough a one-Volt electric potential). The most natural units to use for quan-tum mechanical problems would be energy and time units chosen so that ~ = 1.
  3. Sep 2022
  4. Sep 2021
    1. Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

      Good move. Rather than having 2 different methods, and requiring people to "go out of their way" to "opt in" to using chunks by using the longer-named javascript_packs_with_chunks_tag, they changed it to just use chunks by default, out of the box.

      Now they don't need 2 similar but separate methods that do nearly the same, which makes things simpler and easier to understand (no longer have to stop and ask oneself, which one should I use? what's the difference?).

      You can't get it "wrong" now because there's only one option.

      And by switching that method to use the shorter name, it makes it clearer that that is the usual/common/recommended way to go.

  5. Aug 2021
    1. I really hope they keep breaking it. Being the lead on a library for several years, most of the forced refactors were pretty straight forward and in almost every case made our code either more sound or easier to be consumed. Now I work on a runtime that embeds TypeScript and 3.5.1 has broken some code, thought it took me all of about 15 minutes to make the changes to adopt it, and in every case, it broke because we were being a bit loose with the types. While it didn't find any bugs, it made the code more "safe".

      I really hope they keep breaking it.

  6. Apr 2021
  7. Mar 2021
    1. This creates what is essentially an evolution process for the program, causing it to depart from the original engineered design. As a consequence of this and a changing environment, assumptions made by the original designers may be invalidated, introducing bugs.
  8. Feb 2021
  9. Jan 2021
    1. Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.
    2. I don’t find the software slow, I find the startup time for snap packages when the start for the first time on a session slow, but that has been improved, and it’s public that the snapcraft team has been working hard to improve that.
  10. Oct 2020
  11. Sep 2020