i have written a compiler 
Q.U.I.N.N.
@icedquinn@blob.cat
My heart is cold and dead.
Read your fedi timeline in mutt: https://git.sr.ht/~icedquinn/pleromabox
Banned by Amazon 2024-11-16 :ablobcat3dverified:
nim programmer. trackball enthusiast.
Read your fedi timeline in mutt: https://git.sr.ht/~icedquinn/pleromabox
Banned by Amazon 2024-11-16 :ablobcat3dverified:
nim programmer. trackball enthusiast.
Posts
Latest notes
No posts yet.
[CW]
Content warning
slop
Show
Hide
Content warning
slop
watching a robot utterly fuck up one line fixes is astounding.
watching a robot turn a basic "please decode the event stream from the iterator and stack up a recursive document model from it" in to an entirely correct implementation is astounding.
technology is truly confusing.
watching a robot turn a basic "please decode the event stream from the iterator and stack up a recursive document model from it" in to an entirely correct implementation is astounding.
technology is truly confusing.
@sun all the effort the state spends on terrorizing people out of crypto when crypto people are just unable to function all on their own.
@coolbean @phnt @vic the problem with XML is that it makes sense within the SGML lineage which is not how most people experienced it.
SGML was this massive gigaspec where the culture developed a self awareness that you kind of cherry pick which parts fit your budget. it had a lot of human aids to make ex. writing recipes easier. but because it was a gigaspec, and not everyone implements all of it, they decided what if we removed a lot of the customization and just made a dialect with a lot of fixed decisions that people could implement as an exchange format.
that format is XML.
the correct use of XML per greybeards is in the middle of conversion tools. like i posted last year, its like this:
- my cool key checking daemon only supports a single hardened XML parser for configs
- some domain specific language gets used to actually configure it or a GUI
- a translator turns the cool human version in to the XML document, after processing out all of the aids in to a single verbose document that is plainly (if tediously) understood
Sun didn't follow instructions and everyone else met XML through Sun. Thus begins the generational trauma to reinvent XML-but-Worse (JSON) or XML-but-cute (KDL)
SGML was this massive gigaspec where the culture developed a self awareness that you kind of cherry pick which parts fit your budget. it had a lot of human aids to make ex. writing recipes easier. but because it was a gigaspec, and not everyone implements all of it, they decided what if we removed a lot of the customization and just made a dialect with a lot of fixed decisions that people could implement as an exchange format.
that format is XML.
the correct use of XML per greybeards is in the middle of conversion tools. like i posted last year, its like this:
- my cool key checking daemon only supports a single hardened XML parser for configs
- some domain specific language gets used to actually configure it or a GUI
- a translator turns the cool human version in to the XML document, after processing out all of the aids in to a single verbose document that is plainly (if tediously) understood
Sun didn't follow instructions and everyone else met XML through Sun. Thus begins the generational trauma to reinvent XML-but-Worse (JSON) or XML-but-cute (KDL)
@vic i had an anneurism seeing this. the spec for json is like 1 page.
if you must go whitespace then consider nestedtext. it doesn't have embarassing issues like the norway problem.
if you must go whitespace then consider nestedtext. it doesn't have embarassing issues like the norway problem.
@coolbean @vic afaik the big crime with that is that people are parsing the json as-is and the ld tags are just for show. which means its basically not ld, since namespace resolution isn't being done, which is also basically what happened to xmlns.
there is more spec than i like to json-ld but its also basically working around json's lack of metadata and trying to tape namespacing on in a couple ways, so.
if it were up to me we would just store the triplets and maybe a prefix reference.
there is more spec than i like to json-ld but its also basically working around json's lack of metadata and trying to tape namespacing on in a couple ways, so.
if it were up to me we would just store the triplets and maybe a prefix reference.
do not use yaml. do not support the propagation of yaml. say no to 300 page specs for fucking plain text storage god damnRE: https://w3c.social/@w3c/116216070362563670
your honor i swear i was only stealing the complete works of anime to train an LLM in my basement 
what if we listened to the .xm and .it files near the nostalgia farm
@sun funny part is it would be entirely legal to just ask the nsa politely to bring gnat up to parity, stated goal accomplished and the cost is less than the DOD loses in their couch daily.
DOD: 
please make a programming language for us that doesn't explode constantly
Ada:
[15 years later]
White House:
we gotta embezzle millions on Safe C initiatives! programming is horrible! all the shit crashes constantly!
DOD:
imagine actually bothering to know what shit your institutions actually do
please make a programming language for us that doesn't explode constantlyAda:
[15 years later]
White House:
we gotta embezzle millions on Safe C initiatives! programming is horrible! all the shit crashes constantly!DOD:
imagine actually bothering to know what shit your institutions actually do
@lain gagron literally joining the w3c to just declare mastodon is now the spec.
they've truly learned from google
they've truly learned from google
@sun nostr
@phnt @feld @SuperDicq @sun systems admin is one of the worst jobs to use the "i won't learn to code excuse" considering half of unix administration is bash scripting.
@phnt @feld @SuperDicq @sun where we failed as a field is programming has been stuck in the 1970s forever. we briefly reached out in the 90s with stuff like clickteam and hypercard and the RAD stacks but we've fully regressed back to the 1970s and this makes me very sad.
you're not supposed to be writing C code these days you're supposed to be opening up your object browser, slapping some widgets together and writing a few message sends. this is the future xerox left us. and we just.. walked away.
you're not supposed to be writing C code these days you're supposed to be opening up your object browser, slapping some widgets together and writing a few message sends. this is the future xerox left us. and we just.. walked away.
@phnt @SuperDicq @feld @sun basically "i can write bad code faster with chatgpt" is like when ford said if people asked they would just want a faster horse.
everyone forgot we could also just use a plane.
everyone forgot we could also just use a plane.
@sun @phnt @feld @SuperDicq lain saying it codes as good as them is an indictment of lain being a bad coder, at least until i see a coding model do an actually good job of something in person.
i've been seeing a lot of academic reports that the people who benefit most are simply bad at their jobs, and people who are very good use them very selectively or not at all. after dealing with both beads implementations being steaming piles of trash yesterday i'm not inspired
but i might still be willing to drop 10$ on a GLM sub for a month as one final "hate only in knowledge."
i've been seeing a lot of academic reports that the people who benefit most are simply bad at their jobs, and people who are very good use them very selectively or not at all. after dealing with both beads implementations being steaming piles of trash yesterday i'm not inspired
but i might still be willing to drop 10$ on a GLM sub for a month as one final "hate only in knowledge."