13 Matching Annotations
  1. Oct 2020
  2. Sep 2020
    1. Since re-rendering in Svelte happens at a more granular level than the component, there is no artificial pressure to create smaller components than would be naturally desirable, and in fact (because one-component-per-file) there is pressure in the opposite direction. As such, large components are not uncommon.
    1. Personally, I think class is too blunt an instrument — it breaks encapsulation, allowing component consumers to change styles that they probably shouldn't, while also denying them a predictable interface for targeting individual styles, or setting theme properties globally
    1. We also believe that this explicit API should be relatively granular and work at the selector or value level, not at the element level. This is why we think classes are "a blunt instrument", as Rich put it. Exposing even a single class gives you a clear entry point to the entire component's markup allowing complete control over every aspect. We need a more granular way for a component to define an explicit style interface.
  3. Mar 2020
    1. An example of an extended consent form that allows users to give consent in a more granular manner – i.e. selectively for a number of processing purposes (analytics, remarketing or content personalization)
  4. Oct 2018
    1. Instead of continuing the millennia old search for the universal ontology, different types of ontologies have been proposed in computer science. [.] [C]lassification of ontologies [is] based on their granularity and [their] thematic scope [differs] into top-level, domain, task, and application ontologies ... (Hitzler, Janowicz, Berg-Cross, Obrst, Sheth, Finin, Cruz 2012)
  5. Aug 2018
    1. Sen. Mark Warner of Virginia told the AP it is “frustratingly common” for technology companies “to have corporate practices that diverge wildly from the totally reasonable expectations of their users,” and urged policies that would give users more control of their data. Rep. Frank Pallone of New Jersey called for “comprehensive consumer privacy and data security legislation” in the wake of the AP report.
    2. “If you’re going to allow users to turn off something called ‘Location History,’ then all the places where you maintain location history should be turned off,” Mayer said. “That seems like a pretty straightforward position to have.” Google says it is being perfectly clear. “There are a number of different ways that Google may use location to improve people’s experience, including: Location History, Web and App Activity, and through device-level Location Services,” a Google spokesperson said in a statement to the AP. “We provide clear descriptions of these tools, and robust controls so people can turn them on or off, and delete their histories at any time.”
  6. Apr 2016
    1. federation of easily remixable content

      Granularity of the content itself can matter quite a bit… Part of the reason the focus on textbooks may mislead us (apart from the difficulty of teaching from a textbook) is that the “monolithic” assumption behind the textbook model makes reuse more difficult. Sure, we can take textbooks apart and reuse individual items. But the high degree of integration between parts of a textbook makes it less likely that people will split the book apart.

  7. Jan 2016
    1. export books as apps

      On top of the whole debate between native apps and the Open Web, there’s a debate between apps and books. We might not reach the “Write Once, Publish Everywhere” dream, but there’s something to be said about having building blocks which are easy to adapt to different contexts.

  8. Dec 2015