239 Matching Annotations
  1. Last 7 days
  2. Jul 2021
    1. BlackRock employs a stable of former policymakers, underscoring the importance the company occupies in both financial and policymaking ecosystems, in something akin to a shadow government entity.[157] Good government groups have documented 118 examples of “revolving door” activity by the company—cases in which a government official joined BlackRock’s roster, or vice versa.[158] In one particularly troubling example of how Washington’s revolving door operates, in 2017, a former BlackRock executive was put in charge of reviewing the FSOC’s work for the Treasury Department.[159] Unsurprisingly, the Department’s conclusion was that FSOC should “prioritize its efforts to address risks to financial stability through a process that emphasizes an activities-based or industry-wide approach,” the company’s preferred position.[160] This conclusion all but ensures that BlackRock will not be designated for greater regulation by the FSOC under the Trump administration.

      To Big To Fail? Above The Law? Shadow Government?

      The term "shadow government" comes up often when investigating Revolving Door partnerships between corporations and former government policymakers. One particular public corporation, BlackRock Investments is the poster child of revolving door activity and comparisons to a shadow government.

      BlackRock is front and center in the manipulation of todays Real Estate bubble.

      BlackRock should be marketed as;*The Largest Asset Manager and Keeper of The Neo-liberal Flame; We Kill Children to Make You Money and We Enjoy Doing It!*

    1. urql stays true to server data and doesn’t provide functions to manage local state like Apollo Client does. In my opinion, this is perfectly fine as full-on libraries to manage local state in React are becoming less needed. Mixing server-side state and local state seems ideal at first (one place for all states) but can lead to problems when you need to figure out which data is fresh versus which is stale and when to update it.
  3. Jun 2021
    1. StatelessWidgets are useful when the part of the user interface you are describing does not depend on anything other than the configuration information in the object
    1. Mocking is a form of global state like others (including ENV sharing), which will cause difficulties here (more with threads, a bit less with forks).
  4. May 2021
    1. Wellenius, G. A., Vispute, S., Espinosa, V., Fabrikant, A., Tsai, T. C., Hennessy, J., Dai, A., Williams, B., Gadepalli, K., Boulanger, A., Pearce, A., Kamath, C., Schlosberg, A., Bendebury, C., Mandayam, C., Stanton, C., Bavadekar, S., Pluntke, C., Desfontaines, D., … Gabrilovich, E. (2021). Impacts of social distancing policies on mobility and COVID-19 case growth in the US. Nature Communications, 12(1), 3118. https://doi.org/10.1038/s41467-021-23404-5

  5. Apr 2021
  6. Mar 2021
    1. The reason Final Form does this is so that pristine will be true if you start with an uninitialized form field (i.e. value === undefined), type into it (pristine is now false), and then empty the form field. In this case, pristine should return to true, but the value that the HTML DOM gives for that input is ''. If Final Form did not treat '' and undefined as the same, any field that was ever typed in would forever be dirty, no matter what the user did.
    1. Unlike the latter, however, the neurosciences are extremely well funded by the state and even more so by private investment from the pharmaceutical industry.

      More reasons to be wary. The incentive structure for the research is mostly about control. It's a little sinister. It's not about helping people on their own terms. It's mostly about helping people become "good" citizens and participants of the state apparatus.

    1. It is much easier to track what is going on within the activity. Instead of transporting additional state via ctx, you expose the outcome via an additional end event.

      Note: It's only super easy to see what's going on if you have the benefit of a diagram.

  7. Feb 2021
    1. (b)(1) A representative form of annual or special meeting is a meeting of members elected by district to exercise the powers vested in the voters of the town to act upon articles. However, the election of officers, public questions, and all articles to be voted upon by Australian ballot as required by law or as voted under section 2680 of this title at a prior annual or special meeting, and reconsideration of articles under section 2661 of this title shall remain vested in the voters of the town. (2) An organizational resolution to adopt a representative form of annual or special meeting may be made by the legislative body of the municipality or by petition of five percent of the voters of the municipality. An official copy of the organizational resolution shall be filed in the office of the clerk of the municipality at least 10 days before the annual or special meeting at which the vote whether to adopt the organizational resolution shall take place, and copies thereof shall be made available to members of the public upon request.

      Town Representative Form of Local Gov't. Only Brattleboro has this.

    1. If the criminal justice system is to move toward racial equality and liberation, this change will have to start with the states.

      This idea is repeated countlessly throughout the text (I have highlighted every time it is explicitly stated) and is in the title of this article. His view on this topic is abundantly clear and he uses repetition to drill this idea into his audience's head.

    1. TRAILBLAZER-WORKFLOW is another dream ‘o mine come true. It allows creating long-term processes (or state machines) based on BPMN diagrams that can be modeled using our editor.
    2. A major improvement here is the ability to maintain more than two explicit termini. In 2.0, you had the success and the failure termini (or “ends” as we used to call them). Now, additional ends such as not_found can be leveraged to communicate a non-binary outcome of your activity or operation.
    1. The rationale is that it's actually clearer to eager initialize. You don't need to worry about timing/concurrency that way. Lazy init is inherently more complex than eager init, so there should be a reason to choose lazy over eager rather than the other way around.
    1. Encapsulation is used to hide the values or state of a structured data object inside a class, preventing direct access to them by clients in a way that could expose hidden implementation details or violate state invariance maintained by the methods.
    1. DSLs can be problematic for the user since the user has to manage state (e.g. am I supposed to call valid? first or update_attributes?). This is exactly why the #validate is the only method to change state in Reform.
    2. The reason Reform does updating attributes and validation in the same step is because I wanna reduce public methods. This is to save users from having to remember state.

      I see what he means, but what would you call this (tag)? "have to remember state"? maybe "have to remember" is close enough

      Or maybe order is important / do things in the right order is all we need to describe the problem/need.

    3. My only concern with this approach is that if someone calls #valid? on the form object afterwards, it would under the hood currently delete the existing errors on the form object and revalidate. The could have unexpected side effects where the errors added by the models passed in or the service called will be lost.
    4. My concern with this approach is still that it's somewhat brittle with the current implementation of valid? because whilst valid? appears to be a predicate and should have no side effects, this is not the case and could remove the errors applied by one of the steps above.
  8. Jan 2021
    1. § 3-303. Alteration, amendment, or repeal of charter This charter may be altered, amended, or repealed by the General Assembly whenever the public good shall require.

      Burlington

      State Legislature has ultimate authority

  9. Dec 2020
    1. React will update state throughout the user’s session. localStorage won’t change.When the user ends their session, save whatever the state is at that time to localStorage, making it available for hydrating in the next session.

      Is this safe/reliable to defer saving until then? What if browser crashes? I guess that's why onbeforeunload is needed. Hopefully onbeforeunload is reliable and can't be skipped (unless browser crashes?).

    2. So rather than continuously keeping localStorage in-sync with React state, let’s simply save state to localStorage whenever the user ends their session, either by leaving the app (‘unmounting’ the component) or refreshing the page.
    1. This is the accepted way to handle problems related to authentication, because user data has a couple of important characteristics: You really don't want to accidentally leak it between two sessions on the same server, and generating the store on a per-request basis makes that very unlikely It's often used in lots of different places in your app, so a global store makes sense.
    2. But Svelte 3 doesn't have global stores that are passed around in quite the same way.
    1. Our large project is going to need highly structured and predictable state management, and Svelte’s flexibility scales from trivial projects up to our big one. We’re looking at statecharts and XState to wrangle this problem.
  10. Nov 2020
    1. This means that there needs to be a ‘focus’ state for a button to show that it is ‘clickable, but not clicked yet’.
    1. Frontend frameworks are a positive sum game! Svelte has no monopoly on the compiler paradigm either. Just like I think React is worth learning for the mental model it imparts, where UI is a (pure) function of state, I think the frontend framework-as-compiler paradigm is worth understanding. We're going to see a lot more of it because the tradeoffs are fantastic, to where it'll be a boring talking point before we know it.
  11. Oct 2020
    1. Mine requires that dirty and pristine be "calculated properties".
    2. This is a philosophical issue, I think. People (and presumably form libraries) have different definitions of what "dirty" means. Yours: "The field has ever been edited" Mine: "The value of the field is different from the initial value"
    3. Personally, I rather like the idea of typing into a field, backspacing to undo what you just typed, and having the field (and form) go back to being pristine. Aside from that aesthetic difference, my definition has the practical implication that it lets you know if you need to save the record or not.
    4. We could potentially have another flag that was your definition of dirty, but then we run into the hard problem in computer science: naming things.
    1. 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.
    1. There may be times that required owned elements are missing, for example, while editing or while loading a data set. When a widget is missing required owned elements due to script execution or loading, authors MUST mark a containing element with aria-busy equal to true. For example, until a page is fully initialized and complete, an author could mark the document element as busy.

      "busy" here seems to = "loading" in most other programming contexts

    1. The graphs of ground state confinement energy againstsize (radius) for zinc sulfide nanoparticles in Figure 14 showthe dependence of confinement on the size of quantum dots.The result shows that ground state confinement energy is

      Las graficas de la energía de confinamiento en su estado fundamental en contra del tamaño (radio) por nanopartículas de sulfato de zinc en la Figura 14 muestran la dependencia de confinamiento en el tamaño de los puntos quánticos. El resultado muestra que el estado fundamental de energía en confinamiento es inversamente proporciona al tamaño (radio). Por lo tanto, cuando uno incrementa su radio (tamaño) la energía de confinamiento decrece pero nunca llega a cero. Eso es, el energía mas baja posible para el punto quántica de muestra no es cero. El confinamiento comienza cuando el radio del punto cuántico de muestra es comparable o del orden del radio exciton de Bohr.

    1. Instead of using classes and local state, Deku just uses functions and pushes the responsibility of all state management and side-effects onto tools like Redux.
    1. It's easy to persist the entire application state in a way that is backwards-compatible, so persisted states can survive application changes.
    2. We can treat navigation as a first-class concept, even encoding state transitions in links.
    3. State changes flow from the roots of this graph (which we call atoms) through pure functions (which we call selectors) and into components.
    4. Recoil defines a directed graph orthogonal to but also intrinsic and attached to your React tree.
    5. Component state can only be shared by pushing it up to the common ancestor, but this might include a huge tree that then needs to re-render.
    6. For reasons of compatibility and simplicity, it's best to use React's built-in state management capabilities rather than external global state.
    1. use Xstate which offers a finite state machine that adheres to the SCXML spec­i­fi­ca­tion and provides a lot of extra goodness, including vi­su­al­iza­tion tools, test helpers and much more
    2. The $ contract for auto-sub­scrib­ing is lovely in its sim­plic­ity and flex­i­bil­ity. You can adapt your own preferred state-man­age­ment pattern or library, with or without Svelte stores as helpers. Svelte does not fuss about how you want to manage your state.
  12. Sep 2020
    1. React Stately is a library of state management hooks for use in your component library.
    1. Provides state management for tree-like components. Handles building a collection of items from props, item expanded state, and manages multiple selection state.
    1. So why don't we extract the shared state out of the components, and manage it in a global singleton? With this, our component tree becomes a big "view", and any component can access the state or trigger actions, no matter where they are in the tree!
    1. There is interactive state as well. What about modals that come up because something is clicked? What is the active tab? Is this menu open or closed? What scroll position are they at? There are infinite permutations of this. Imagine a warning bar that shows up seven seconds after the user logs in to warn user about their expired credit card which contains a custom styled select menu which can be in an open or closed state, but only on the user settings page.
    2. Remember the timing thing? We might think of timing as one generic form of state. There are countless other things that could be state related. Is the user logged in or not? What plan are they on? Is their credit card expired thus showing some kind of special message? Do situational things like time/date/geolocation change state? What about real-time data? Stuff from an API?
    1. Slide 13:

      “No man ever steps in the same river twice, for it's not the same river and he's not the same man.”

      ― Heraclitus

      Of course it’s not the same river — the river, is, what? The water flowing past your feet? The sound that it makes? These things are different at every moment. Our idea of ‘the river’ doesn’t correspond to anything in the real world. Understanding this concept means getting closer to an understanding of reality itself — once you fully absorb the impact of this idea, it changes you, from a person who didn’t have that understanding into one who does.

      And as you bask in your newfound zen-like enlightenment, you discover an almost spiritually calming effect — the world as it is right now is the only thing that matters, not the state of the world as it was yesterday or as it will be tomorrow.


      Slide 39:

      “No man ever steps in the same river twice, for it's not the same river and he's not the same man.”

      ― Heraclitus

      And I think Heraclitus probably understood it all along. There’s a paradox contained in this statement. If the concept of identity over time is meaningless, then what do we mean by ‘it’ and ‘he’?

    2. It turns out that even the length of time an element has been mounted is an important piece of state that determines what pixels the user sees. And some of this state can’t simply be lifted into our application state.

      What this means is that our desire to express UI using pure functions is in direct conflict with the very nature of the DOM. It’s a great way to describe a state => pixels transformation — perfect for game rendering or generative art — but when we’re building apps on the web, the idea chafes against the reality of a stateful medium.

    1. While I am not homosexual, I have always felt that discrimination against homosexuality is completely ludicrous because I think people should love who they love. This belief that I have has giving me an idea for my research topic for my bibliography project where I look over the state of homosexuality in 2020. I decided to annotate this article because it gave a lot of good information about the state of homosexuality in 2020 and it has some links to other articles about homosexuality.

    1. Stores are global state. While context is local state.
    2. Notice it's not related to components. Another crucial difference is that it's accessible from outside of components. And good way to determine where goes where is to ask yourself, can this particular state and functionality still makes sense outside of the displayed component?
    1. Statecharts are a formalism for modeling stateful, reactive systems. This is useful for declaratively describing the behavior of your application, from the individual components to the overall application logic.
    1. The state is a data structure that starts with a default value when a Component mounts. It may be mutated across time, mostly as a result of user events.

      The state is a data structure with a default value at the start which can be mutated based on user events.

  13. Aug 2020
    1. How to Get into Flow States, Quickly

      1.Relax

      2.Coffee/Caffeine

      3.Something that inspires your work

      4.Warm-up - get your brain primed for the activity

      5.Sends chills down your spine - Watch something that Inspires you e.g. David Goggins

      6.Avoid distraction - Put phone away and noise cancelling headphones

    1. Safari sends following order application/xml (q is 1) application/xhtml+xml (q is 1) image/png (q is 1) text/html (q is 0.9) text/plain (q is 0.8) \*/\* (q is 0.5) So you visit www.myappp.com in safari and if the app supports .xml then Rails should render .xml file. This is not what user wants to see. User wants to see .html page not .xml page.
  14. Jul 2020