ra’s avatarra’s Twitter Archive—№ 38,905

  1. i have a prototype of a feature of jn that i am pretty sure is a terrible idea. names in the .NET framework are CamelCased but names in lisp are kebab-cased. idea is: you can opt into automatic conversion on a per-namspace bases and treat .NET like a giant lisp library! thoughts?
    oh my god twitter doesn’t include alt text from images in their API
    On twitter.com Twitter logo ra’s avatar ❤️ 2 Favorites Mood 0
    1. …in reply to @ra
      cons: - added complexity for no real gain. .NET names are perfectly usable as is - extra magic to keep in your head - docs/errors will use real .NET names and not lispy names - makes different names mean the same thing e.g. DateTime and date-time
      Permalink On twitter.com Twitter logo ra’s avatar ❤️ 2 Favorites Mood +2 🙂
      1. …in reply to @ra
        pros: - it looks really nice!!! - avoids clashing naming conventions in a single file - its opt in and localized, so it shouldnt take you by surprise and you can ignore it if you like
        Permalink On twitter.com Twitter logo ra’s avatar ❤️ 3 Favorites Mood +3 🙂