what if we simply made the programming language out of markdown

[pixel@oldbytes.space]

@joe hmm. I don’t hate it.

[brunoph@breakpoint.cafe]

@joe mmmm Turing-complete markdown parsers

[jkohlmann@mastodon.social]

@joe Don’t be silly, Joe, we already have Yaml

[brooke@bikeshed.vibber.net]

@joe oh you're *baaaaaaaad* joe

[isaiah@mastodon.social]

@joe that’s basically my vibe coding prompt and specification workflow.

jokes aside, it could be a lot worse.

[be_far@social.treehouse.systems]

@joe haaaaate that. Looks like a new shell language

[aburka@hachyderm.io]

@joe lispdown

[inthehands@hachyderm.io]

@joe
The fun part is it will give 1980s C a run for its money in the implementation-dependent parsing contest

[kylebshr@mastodon.social]

@joe ooh then maybe something could convert it to executable code without a large language model in the middle!

[lenary@types.pl]

@joe looks like MIR to me

I did wonder how much of a language one could do just using KDL. Didn't get further than thinking though.

[beccadax@soincredibly.gay]

@joe Joe, this idea is cursed even by your standards

[jrose@social.belkadan.com]

@beccadax @joe is it really worse than programming in XML, a thing people were doing in earnest in the 00s

[beccadax@soincredibly.gay]

@jrose @joe I mean, two things can be cursed at once, Jordan.

[bri7@social.treehouse.systems]

@joe yaml?

[maccatalan@techhub.social]

@joe reminded me of LamdaTalk: http://lambdaway.free.fr/lambdaspeech/

[xavierlowmiller@hachyderm.io]

@joe LISP now has tables and emphasis?

[bruceiv@tenforward.social]

@joe if it weren't for the fact that most markdown software sucks at dealing with multiple levels of nesting I'd actually like it.

You should totally use backticks for comments, though.

[krzyzanowskim@mastodon.social]

@joe is it thread safe?

[atax1a@infosec.exchange]

@joe lisp s-expressions for the web 2.0 era