16 Matching Annotations
  1. Mar 2023
    1. hese challenges demand an ethos not of technologicalcleverness, but of social prudence, of acting with humility and cautionwhen confronted by risk and uncertainty. The French philosopherHans Jonas calls this the “imperative of responsibility.”

      // - see also Kevin Anderson's presentation on "The Ostrich and the Phoenix" - https://jonudell.info/h/facet/?max=100&expanded=true&user=stopresetgo&exactTagSearch=true&any=ostrich+and+the+phoenix - humans opt for the just-in-time techno path because we can "kick the can down the road" and procastinate and allow the next generation deal with the problem - As Anderson shows, there isn't enough time for renewable energy to scale to make a difference in the short term and the difficult social problem of massive social behavior change is unfortunately the best way to solve the problem - the allure of technology is that it can fix any problem - the reality is that last generation's technology is unfortunately often the source of this generation's problems - technology not only produces progress, but the unintended consequences produce progress traps which become the inspiration for new technology in an endless cycle of self-created problems giving rise to avoidable solutions

  2. Dec 2021
    1. That’s a pattern that repeats again and again: a solution is created in an imperative language and if it’s popular enough, it migrates to a declarative language over time. When a feature is available in a declarative language, not only is it easier to write, it’s also more robust.
  3. Nov 2021
  4. Oct 2020
    1. Declarative programming is an enabler of abstraction. Imperative programming is an inhibitor of abstraction. Declarative programming allows you to say “I want this and I don’t care how I get it” while imperative programming requires you to define each and every step.

      Declarative programming, i.e. "build me a house, I don't care how", is an enabler of abstraction.

      Imperative programming, i.e. "build walls, windows, a roof.", is an inhibitor of abstraction.

    1. SwiftUI is a user interface toolkit that lets us design apps in a declarative way. That’s a fancy way of saying that we tell SwiftUI how we want our UI to look and work, and it figures out how to make that happen as the user interacts with it.
    2. Imperative UI causes all sorts of problems, most of which revolve around state, which is another fancy term meaning “values we store in our code”. We need to track what state our code is in, and make sure our user interface correctly reflects that state.
  5. Sep 2020
    1. detach, as an api, should be declarative (ensure the node is detached) instead of imperative (detach the node), allowing it to be called multiple times by performing a noop if the node is already detached. This way, it won't matter if the node is removed from the DOM from outside of svelte.
  6. Jul 2020
  7. Oct 2019
  8. Feb 2019
  9. Sep 2018
  10. Mar 2018
    1. when you ask the same people to do something FOR you, e.g. lend you a book or sign a recommendation letter for you, you can’t just use ください.

      This is like a homeless person saying "give me money, sir." It is still an order.

  11. Oct 2015