10 Matching Annotations
  1. Oct 2021
    1. # And this is the bytecode benchmark translated from Squeak

      Muy interesante cómo traducir código de un entorno al otro ayuda a aprender el otro. Podría usarse para mis propios procesos de aprendizaje

  2. Apr 2019
  3. May 2018
    1. While Simula was not unique in developing in this direction, we can observe in thismovement a moment in a larger divergence between math and programming. Despite theinitial design plans, they quickly moved away from thinking of the language in terms ofmathematic


      Within computation, there are those such asNygaard and Dahl, who see programming breaking with mathematics, while there are thosewho stress the mathematical nature of computation.

      Interesante como esto atañe a carreras como Informática-Matemática, desafortunadamente extinta por la miopía de un exdirector del Departamento de Matemáticas en la Universidad Javeriana.



  4. Nov 2016
    1. Corporate practices can be directly hostile to individuals with exceptional skills and initiative in technical matters. I consider such management of technical people cruel and wasteful. Kierkegaard was a strong proponent for the individual against “the crowd” and has some serious discussion of the importance of aesthetics and ethical behavior. I couldn’t point to a specific language feature and say, “See, there’s the influence of the nineteenth-century philosopher,” but he is one of the roots of my reluctance to eliminate “expert level” features, to abolish “misuses,” and to limit features to support only uses that I know to be useful. I’m not particularly fond of Kierkegaard’s religious philosophy, though.

      Interesante ver cómo el lenguaje de programación es diseñado como una prevención contra la cultura corporativa.

    2. TR: In retrospect, in designing C++, wasn’t your decision to trade off programmer efficiency, security, and software reliability for run time performance a fundamental mistake?BS: Well, I don’t think I made such a trade-off. I want elegant and efficient code. Sometimes I get it. These dichotomies (between efficiency versus correctness, efficiency versus programmer time, efficiency versus high-level, et cetera.) are bogus.What I did do was to design C++ as first of all a systems programming language: I wanted to be able to write device drivers, embedded systems, and other code that needed to use hardware directly. Next, I wanted C++ to be a good language for designing tools. That required flexibility and performance, but also the ability to express elegant interfaces.
    3. And without real changes in user behavior, software suppliers are unlikely to change.
    4. People reward developers who deliver software that is cheap, buggy, and first. That’s because people want fancy new gadgets now.
    5. Software developers have become adept at the difficult art of building reasonably reliable systems out of unreliable parts. The snag is that often we do not know exactly how we did it: a system just “sort of evolved” into something minimally acceptable. Personally, I prefer to know when a system will work, and why it will.
  5. Nov 2015
    1. To draw an analogy with computer coding, we might say that financial instruments are analogous to ‘high-level’ programming languages such as Java or Ruby: they let you string commands together in order to perform certain actions. You want to get resources from A to B over time? Well, we can program a financial instrument to do that for you.

      Interesante analogía. Habría que mirar cómo las prácticas cooperativistas pueden impulsar flujos de A hacia B y estar sustentandos en varios sustratos materiales, algunos con poca tecnología (monedas locales) y otros con alta tecnología (bitcoins, ethereum, etc).