Kotlin shortens the name of its integer type to "Int" but does not shorten the name of its boolean type, it's "Boolean". This feels wrong. At some primal level I do not like it
I feel like "don't freak out it's just a proposal" should hold no water when A Modest Proposal exists. Not that the type of tech bros that came up with the browser DRM thing have clearly ever read a book
@eniko the proposal isn't made in a vacuum, and all being goog employees most certainly means there's been 20 meetings about it already, there's no proposal, there's a plan to execute
I have filed a feedback/issue on Github Issues (that is, the part of Github for filing issues) requesting that their Markdown parser should stop incorrectly interpreting Mastodon handles as email addresses https://github.com/orgs/community/discussions/61284
It's important to have a pride flag in my Google Meet background, so that I can point at it whenever any coworkers mention considering any cludflre services
@foone ooh, this was Australian animal? I was thinking of the other Nazi site that cloudflare only stopped supporting because "the CEO was done with all the drama"
anyway, that sucks even harder, I hope you're safe
Wrote some Rust and found myself typing a function as returning Option<()>, which is just absolutely the silliest type, just because returning bool locked me out from using ?.
I am now torn between wanting to argue ? should be available to short circuit return false in functions returning bool; and my long standing belief that Result<> and Option<> should be merged into a single type, like Option<T> should be Result<T, None> or something, and the failure to do this is Rust's biggest falling
a few years ago i've avoided mastodon/fediverse because i didn't like the interactions i had here, and stayed on twitter because i thought the interactions there were fulfilling
well... these days i get the same kind of fufilling interaction on here, and on twitter i get ~nothing
just what is the industry standard for dockerizing programs that have to be run in MS-DOS?
QEMU is the most "standard" virtual machine, but it'd have a pretty difficult interfacing step, since you have to manipulate FAT filesystems to get data in and you can't easily just get output back out, unless you redirect to files & read FAT again, or do screen-scraping
Starting to really appreciate the "broke stack" (self-hosted postgres + gitea + woodpecker CI). it's relaxing knowing I'm not being billed for existing/trying stuff.
