Cassandra Granade 🏳️⚧️
Contacting Cassandra Granade 🏳️⚧️
Federation handle:
@xgranade@wandering.shop
Cassandra Granade 🏳️⚧️'s Information
Cassandra Granade 🏳️⚧️'s Bio
Sometimes I write intimate eschatologies or words about technology and math. Sometimes I make things by burning them with light or squeezing them through a small, hot tube. Sometimes I push water with a stick while sitting in a tiny boat.
Cassandra Granade 🏳️⚧️'s Posts
Cassandra Granade 🏳️⚧️ has 7 posts.
Cassandra Granade 🏳️⚧️
In response to this post@FediPact Mirrored shares.
Mentions: @FediPact@cyberpunk.lol
Likes: 0
Replies: 0
Boosts: 0
Cassandra Granade 🏳️⚧️
If you're deleting your WhatsApp account, please consider using Signal instead. WhatsApp is basically Signal wrapped in Facebook nonsense anyway, so it'll be pretty familiar, and also benefits from being end to end encrypted.
Please don't let your very valid and necessary anger at Facebook push you to unencrypted or poorly encrypted messaging systems.
Likes: 0
Replies: 0
Boosts: 1
Cassandra Granade 🏳️⚧️
@nora There's a lot of critiques of Ubuntu out there, much of it valid and necessary, but I do think it's a pretty reasonable Linux gender to go with. Even if only because so many things target Ubuntu for support.
(FWIW, I'm typing this from an Ubuntu install.)
Likes: 0
Replies: 0
Boosts: 0
Cassandra Granade 🏳️⚧️
@samir I'm meaning something incredibly minimal, treating parentheses as a kind of static assertion that can be safely ignored when interpreting the program, but that provides context to the reader.
Likes: 0
Replies: 0
Boosts: 0
Cassandra Granade 🏳️⚧️
In response to this postBasically, I personally find Lisp hard to read because all parentheses appear the same way, even though the semantic importance of said parentheses are not always equal. If there's a principled way to make parentheses optional but useful and correct when present, that could be really neat.
@xgranade I once started working on a Lisp preprocessor that let you write in indented (Python-ish) style, and compiled to parentheses. You could still use the parentheses yourself if you like.
Didn’t get too far but I still think it’s a decent idea.
Is that also kind of what you’re describing, or am I missing something?
I can see an alternative approach that would use knowledge of the symbols to decide what to do, but that would require types, and likely preclude variable arguments.
by samir, hibernating ;
Likes: 0
Replies: 1
Boosts: 0
Cassandra Granade 🏳️⚧️
That is, parentheses would be completely and totally optional, but could be included to help readability of code, with the compiler ensuring that they are not actively misleading but rather accurately represent the structure of the code.
Basically, I personally find Lisp hard to read because all parentheses appear the same way, even though the semantic importance of said parentheses are not always equal. If there's a principled way to make parentheses optional but useful and correct when present, that could be really neat.
by Cassandra Granade 🏳️⚧️ ;
Likes: 0
Replies: 1
Boosts: 0
Cassandra Granade 🏳️⚧️
Inspired by @mcc's threads on Forth, I'm curious about the idea of a language in which parentheses are not grouping constructs, but a kind of compiler-enforced linting.
E.g. if you have * + 2 3 5 in an RPN-based language, that you could write * (+ 2 3) 5 where ( means "the next token is an operator, and there is a matching ) somewhere forward of this (," and where ) means "an operation and its operands were just popped from the stack, and that operand was denoted by a (."
Likes: 0
Replies: 0
Boosts: 1