13 Matching Annotations
  1. Nov 2022
    1. Genealogy Garage: Researching at the Huntington Library

      <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/0f2j2K6JWGg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
      • Julie Huffman jhuffman@lapl.org (host)
      • Stephanie Arias
      • Anne Blecksmith
      • Li Wei Yang
      • Clay Stalls cstalls@huntington.org

      ECPP

      Huntington Library

      Visit checklist

  2. Jun 2021
  3. Feb 2021
    1. Now if you think about it, PJAX sounds a lot like Turbolinks. They both use JS to fetch server-rendered HTML and put it into the DOM. They both do caching and manage the forward and back buttons. It's almost as if the Rails team took a technique developed elsewhere and just rebranded it.
  4. Oct 2020
  5. Sep 2020
    1. The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.
    1. The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)
  6. Oct 2018