Post · bonfire.cafe

Post

Piko

@piko@chaos.social · 2 weeks ago

We are slow, but we are having *a lot* of fun!

An assembly programm that waits for input and then prints the input. It's more than 20 lines and has a lot of comments

Piko

@piko@chaos.social replied · 2 weeks ago

OMG it was so good!

Screenshot from the website of advent of code: "You are one gold star ... Part Two". This means we solved the puzzle – with assembly!

Piko

@piko@chaos.social replied · 2 weeks ago

The program is not even *that* long!

Screenshot of unreadably small assembly code in vim

Piko

@piko@chaos.social replied · yesterday

We solved the fifth day of advent of code – in nu shell script!

It's a very friendly shell where all data is structured. It worked really nicely for an advent of code task.
We even managed to use recursion, although the default recursion limit doesn't seem like it's intended to be used. :3

#AdventOfCode #nuShell

Screenshot of a terminal window running nu shell. There are happy and intense colors.
First you see some lines of the end of a table with numbers. In the last line, the headings ("from" and "to") are repeated. Then there's a prompt with a file path, and the command "source 05b.nu". This is followed by an error message, which is expressive and beautifully formatted. Then another prompt with the same command (one can infer that the error has been corrected in the meantime), and a table with numbers. — Screenshot of a terminal window running nu shell. There are happy and intense colors. First you see some lines of the end of a table with numbers. In the last line, the headings ("from" and "to") are repeated. Then there's a prompt with a file path, and the command "source 05b.nu". This is followed by an error message, which is expressive and beautifully formatted. Then another prompt with the same command (one can infer that the error has been corrected in the meantime), and a table with numbers.

Piko

@piko@chaos.social replied · 3 hours ago

The most romantic thing we did with @teamtype [1] is writing lisp :>
One opens the brackets and the other one closes them. Not that fitting for polyamorous folks though.

[1] https://teamtype.org

d@nny disc@ mc²

@hipsterelectron@circumstances.run replied · 3 hours ago

@piko @teamtype you can open multiple

Nils Goroll 🕊️:varnishcache:

@slink@fosstodon.org replied · 2 hours ago

@hipsterelectron @piko @teamtype i had to think back to linguistics courses at uni: matching parentheses can be expressed as a context free grammar, but for "polyamorous parentheses" we might need different pairs intermixed, such that, for instance, <[{]>} would be valid, but <[{>} not because of the missing ]
i wonder how (if?) this could be expressed in a formal grammar and where in the chomsky hierarchy it would live.

2 more replies (not shown)

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.7 no JS en

Automatic federation enabled