> PURRTRAN allocates all variables to an arena called the "Litterbox". The Litterbox must be manually emptied at least once a day by the user, or Hex's cleanliness and love will decrease. The Litterbox can overflow, which will cause Hex to become very displeased and may lead to unexpected program behavior, as Hex will begin storing variables in your source code text buffer instead of the Litterbox until it's cleaned.
I'm cackling like a madman, thank you for this op.
> There is no way to observe Hex's internal state directly. You must infer how he is feeling based on his behavior and the lints he provides. This makes it difficult to diagnose issues with Hex's performance or behavior.
> If you look closely, those aren't angle brackets, they're characters from the Canadian Aboriginal Syllabics block, which are allowed in Go identifiers. From Go's perspective, that's just one long identifier.
Thanks for the kind words and keeping the joke going, I laughed at many of these responses. I think they'll make it in to v2.0 which should be out by 4/1
It makes sense that the first thing I'd get to the front page of HN is what amounts to a bad joke :P
> Hex will let you know when he is bored by interrupting your work with a note in your terminal
Cats routinely initiate attention grabbing denial of service attacks by blocking access to hardware so this needs proper emulation to increase the realism. I have a few recommendations:
Mouse trapping - when cat pops up the mouse cursor should be limited in motion as if you turned the sensitivity down to near 0. This emulates a cat who lies directly on top of your mousing hand while using said mouse.
Keyboard injection - after cat pops up all further typing results in cat-on-a-keyboard output. This emulates a cat sitting or walking across your keyboard.
Screen jacking - The screen has a cat shaped blank spot that obscures most of your working environment. This can also be paired with cat-on-a-keyboard typing. Emulates cat sitting in front of monitor, likely on top of keyboard.
Once hardware denial fails they move on to destroying your personal items:
destruction of personal items - USB solenoids strategically placed behind any object that you either a. cherish or b. do not want spilled. "That nice book you were just admiring - now it has coffee all over it because I am need something."
I could go on but these are a good starting point.
Seems more of a productivity killer rather than an aid but cats are great marketing. I see no reason not to submit this for YC funding in the next round
Not gonna lie this makes me want to learn Purrtran, you have to feed HEX, clean up after them and play with them or else it will misbehave or even die. Hex needs to be happy to help with code, I love it great way to make programming fun! Also pretty cool that they added print and for loop structures that are easier to use.
"In the following example, Hex leaves you a dead baby bunny rabbit because you have unused variables in your code"
…but with intentionally weird semantics picked for its humour rather than legibility.
It might not be a challenging language, but it is designed more for art than utility.
This firmly makes it an esoteric language.
Whereas Purrtran has conventional semantics. The cuteness of Purrtran is in the documentation rather than the language design. The esoteric part is really more in the story telling rather than the language semantics.
I'm cackling like a madman, thank you for this op.
this is deep
https://old.reddit.com/r/rust/comments/5penft/parallelizing_...
> type ImmutableTreeListᐸElementTᐳ struct { ... }
> If you look closely, those aren't angle brackets, they're characters from the Canadian Aboriginal Syllabics block, which are allowed in Go identifiers. From Go's perspective, that's just one long identifier.
It makes sense that the first thing I'd get to the front page of HN is what amounts to a bad joke :P
Cats routinely initiate attention grabbing denial of service attacks by blocking access to hardware so this needs proper emulation to increase the realism. I have a few recommendations:
Mouse trapping - when cat pops up the mouse cursor should be limited in motion as if you turned the sensitivity down to near 0. This emulates a cat who lies directly on top of your mousing hand while using said mouse.
Keyboard injection - after cat pops up all further typing results in cat-on-a-keyboard output. This emulates a cat sitting or walking across your keyboard.
Screen jacking - The screen has a cat shaped blank spot that obscures most of your working environment. This can also be paired with cat-on-a-keyboard typing. Emulates cat sitting in front of monitor, likely on top of keyboard.
Once hardware denial fails they move on to destroying your personal items:
destruction of personal items - USB solenoids strategically placed behind any object that you either a. cherish or b. do not want spilled. "That nice book you were just admiring - now it has coffee all over it because I am need something."
I could go on but these are a good starting point.
The famous cat-in-the-middle attack
Nyawww!
I think that's a brand new sentence
"In the following example, Hex leaves you a dead baby bunny rabbit because you have unused variables in your code"
https://en.wikipedia.org/wiki/LOLCODE
It might not be a challenging language, but it is designed more for art than utility.
This firmly makes it an esoteric language.
Whereas Purrtran has conventional semantics. The cuteness of Purrtran is in the documentation rather than the language design. The esoteric part is really more in the story telling rather than the language semantics.