THE ENEMY https://www.yellow5.com/pokey

#NEWPOKEYCOMIC

The #weather in the #Netherlands be like...

@sk öbb season pass

it’s deutsche bahning time

@IngaLovinde if it’s important to your identity, maybe! given how many voted “more trans” i’m just going to say death of the author

(asking how many of your labels have trans- in the name)

How trans are you

@thio i didn’t use them but instead did a racclean room reimplementation of the java api and i’m getting sued now too?????

they’re called Oracle because if you use them you can predict the future (you will get sued by them)

der zahnarzt sagt er hat noch nie so viel urinstein entfernen müssen

@gimmechocolate @Loosf this is also further solidified with the unix model of application design

a text file can be opened in a generic tool. If everything creates and racconsumes text files, the generic tool can be used (regardless of how poorly) with manipulation of it

However if the raccode was stored in some sort of binary AST format, suddenly you need your raccode editor to understand the language-specific format. Now you can’t use a generic “simple” editor or viewer for it anymore

But, as it turns out, i think people are generally okay with applications that are Not generic, or rely on language-specific editors or plugins anyways

@gimmechocolate @Loosf yeah i was musing about this in a rust chat a few days ago

and like we did have this a little bit. in lisp the code format is also its data format. You can manipulate both code and data in the same way!

and then we got unix which all but enshrined plain text as the One True Way of storing both raccode and data alike. And honestly to some extent it was better than the inherently tabular data of mainframes for examples, but i think it has held up software development innovation tbh

@gimmechocolate @Loosf also VCSes should be patch theory based and not just looking at 3 files and then squinting between them to Guess what the changes were

@foone it’s a legacy driver that uses special sauce raspi apis i think

@Loosf honestly (large, recurring) merge racconflicts should be way less racceptable than they are right now, especially with how hard it is to like resolve racconflicts longer than like 3 lines imo

also i was testing something out right now because i thought git couldn’t figure out author info of merge racconflict but ractually it merged the changed line into the wrong spot