Gregory's Server
 @neauoire I really like doing backups and going back through logs, metrics and read lists every New Year "I sense we are in moments of descent. " ASCII having ( and ) next to each other, but every other types of brackets having something inbetween is kind of a pain. @neauoire you know what really is a pain? having to read those endless mails on the @ietf lists about ASCII, its history, how it didn’t get registered appropriately, etc. and, especially, all those dudes being so convinced their version of the story is the truth and nothing but. https://mailarchive.ietf.org/arch/browse/art/?gbt=1&qdr=m&q=ASCII Faircamp  "Going through Patagonia"  @neauoire Apple Maps was like this in its early days: Cairo? Sure, that's in USA somewhere. Memphis? Also in the US! Europe? Yup, here's a US town called Europe! I haven't used it since those days.  Cruising the Glaciers of the Beagle Channel
Show previous comments
@neauoire it's interesting that you started implementing that after you worked a bit with LISP *modifies self-hosted compiler directly, braces for impact*  I wonder what we should do with the Wiktopher manuscript with all the corrections. It's a thick stack of paper, storage it? Is there any point in keeping that. Feels weird to just throw away.
Show previous comments
  @neauoire if you have a local town with a library and an ephemera collection, donate it there? Or you fave uni's ephemera collection.  @neauoire I think it's easy to decide answering: Do you think in 20-30 years time you will like to find it in an old box?  Fun little documentary on the design of the Newton Shared a day with an old friend from Montreal who's visiting and our little winter sailing community. We went to watch the waves crash violently on the ocean side for a bit. We made tourtiere gyozas for dinner, it was fabulous, we took some pictures and some notes, so we can turn it into a recipe. I hope everyone is having an enjoyable end of year. @neauoire 😱 I am now salivating at the notion of "tourtière gyoza", that may be the perfect fusion dish. Put some music, made some buckwheat tea, hid under the blanket and implemented a little base1 arithmetic system(church encoding) in purelisp.  An abstraction inversion is the phenomenon that happens when "a simpler notion is defined in terms of more complex notions". The cost of abstraction inversion is paid by high-overhead in implementation, difficulty in semantic analysis and proofs, mismatch of development tools, general bloat, complexity and unsafety. @neauoire That's a good list of costs. Where I work there is a general habit of sending in very large and complex data structures as input to functions (Java), not because the function needs all that data, but because the caller generally already has that data structure prepared. The long-term problems that the code experiences because of this habit pretty much correlates exactly with your list of costs... I ought to take some of this and turn it into evidence. Sopor Aeternus bringing the cheers  |
