24 Matching Annotations
  1. Oct 2020
    1. One of the primary tasks of engineers is to minimize complexity. JSX changes such a fundamental part (syntax and semantics of the language) that the complexity bubbles up to everything it touches. Pretty much every pipeline tool I've had to work with has become far more complex than necessary because of JSX. It affects AST parsers, it affects linters, it affects code coverage, it affects build systems. That tons and tons of additional code that I now need to wade through and mentally parse and ignore whenever I need to debug or want to contribute to a library that adds JSX support.
    1. The important goal here is that if we're going to introduce different semantics between classes and function components, we need to know before calling them which semantics we're going to apply.
    1. The worst answer I can imagine is the one Pope Gregory VII gave for refusing to let the Holy Scripture be translated out of Latin: “... [I]f it were plainly apparent to all men, perchance it would be little esteemed and be subject to disrespect; or it might be falsely understood by those of mediocre learning, and lead to error.”

      I'd push back on this a bit by saying that there are huge swaths of people looking at English translations, of Latin translations, of Greek, Hebrew, and Aramaic translations. Not only is there some detail lost in the multiple levels of translation, but many modern Christians are actively mis-applying the stories in the Bible to apply to their modern lives in radically different ways than was intended.

  2. Sep 2020
  3. Aug 2020
  4. Jul 2020
    1. Words are not simple tools to be applied and used.

      To try to use words in life as uniform instruments with preconceived uses would be to use a jackhammer to repair a swiss watch.

      To repair a spider-web with one's fingers.

      Denial of atomistic picture of linguistic meaning. Real words, live words, don't work as singular referents.

      TS Eliot - words do not sit still.

  5. Apr 2020
    1. Apache Stanbol's main features are: Content Enhancement Services that add semantic information to “non-semantic” pieces of content. Reasoning Services that are able to retrieve additional semantic information about the content based on the semantic information retrieved via content enhancement. Knowledge Models Services that are used to define and manipulate the data models (e.g. ontologies) that are used to store the semantic information. Persistence Services that store (or cache) semantic information, i.e. enhanced content, entities, facts, and make it searchable.
    2. direct usage from web applications (e.g. for tag extraction/suggestion; or text completion in search fields), 'smart' content workflows or email routing based on extracted entities, topics, etc.
    3. Apache Stanbol provides a set of reusable components for semantic content management.
    1. This graph view is the easiest possible mental model for RDF and is often used in easy-to-understand visual explanations
  6. Mar 2020
  7. Jan 2020
  8. Nov 2019
  9. Aug 2019
    1. AI relies upon a bet. It is the bet that if you get your syntax (mechanism) right the semantics (meaning) will take care of itself. It is the hope that if computer engineers get the learning feedback process right, a new transhuman intellect will emerge.
  10. Jan 2019
  11. Jun 2018
    1. In “Getting Real,” Barad proposes that “reality is sedimented out of the process ofmaking the world intelligible through certain practices and not others ...” (1998: 105). If,as Barad and other feminist researchers suggest, we are responsible for what exists, what isthe reality that current discourses and practices regarding new technologies makeintelligible, and what is excluded? To answer this question Barad argues that we need asimultaneous account of the relations of humans and nonhumansandof their asymmetriesand differences. This requires remembering that boundaries between humans and machinesare not naturally given but constructed, in particular historical ways and with particularsocial and material consequences. As Barad points out, boundaries are necessary for thecreation of meaning, and, for that very reason, are never innocent. Because the cuts impliedin boundary making are always agentially positioned rather than naturally occurring, andbecause boundaries have real consequences, she argues, “accountability is mandatory”(187). :We are responsible for the world in which we live not because it is an arbitraryconstruction of our choosing, but because it is sedimented out of particular practicesthat we have a role in shaping (1998: 102).The accountability involved is not, however, a matter of identifying authorship in anysimple sense, but rather a problem of understanding the effects of particular assemblages,and assessing the distributions, for better and worse, that they engender.
    1. Text is not going away, but if we really want it to be understood and remembered, we should integrate it better with physical and emotional experience. This convergence may happen with the “physicalization” of the digital world, where digital experiences become part of our physical life.

      Como nos filmes, será que um dia a Web vai extrapolar o digital e ir para o mundo físico?

  12. Feb 2014
    1. What is missing is a space between the $( and the following (, to avoid the arithmetic expression syntax. The section on command substitution in the shell command language specification actually warns for that:

      This is a very good example of why shell scripting does not scale from simple scripts to large projects. This is not the only place where changes in whitespace can lead to scripts that are very difficult to debug. A well-meaning and experienced programmer from another language, but new to bash scripting, might decide to clean up formatting to make it more consistent-- a laudable goal, but one which can lead to unintentional semantic changes to the program.

      Flat, short bash scripts are extremely useful tools that I still employ regularly, but once they begin creeping in size and complexity it's time to switch to another language to handle that-- I think that is what (rightly) has driven things likes Python, Puppet, Ansible, Chef, etc.

      Despite the syntactic horrors lurking in shell scripts there is still a beautiful simplicity that drives their use which is a testament to the core unix philosophy.

  13. Jan 2014
    1. I regret that the documentation does not focus on what is most relevant; by focusing on a largely irrelevant implementation detail, we enlarge the importance of that implementation detail and obscure the importance of what makes a value type semantically useful. I dearly wish that all those articles explaining what “the stack” is would instead spend time explaining what exactly “copied by value” means and how misunderstanding or misusing “copy by value” can cause bugs.

      Documentation should focus on semantically useful descriptions; another accompanying document (or annotation) can provide relevant implementation details upon request, but that deeper level of detail should be left out by default to avoid enlarging the importance of less relevant things.

    2. Surely the most relevant fact about value types is not the implementation detail of how they are allocated, but rather the by-design semantic meaning of “value type”, namely that they are always copied “by value”.
  14. Oct 2013
    1. For there are who read and yet neglect them; they read to remember the words, but are careless about knowing the meaning. It is plain we must set far above these the men who are not so retentive of the words, but see with the eyes of the heart into the heart of Scripture. Better than either of these, however, is the man who, when he wishes, can repeat the words, and at the same time correctly apprehends their meaning.

      Semantics/paradigmatics needed.