I have so many unreasonable demands of my computers "Do not occasionally power off for no reason" "Do not vibrate my skull" "Do not bulk collect my personal information and transmit it to a UFO cult in San Francisco"
@joeo10@millions@miah I think I found a corporate support option by which you'll be able to pay extra to keep using Win10 with security updates past the 2025 cutoff. I am likely to do this because I am *absolutely* willing to pay extra to avoid "AI" integration
Deeply unpleasant space opera setting where every species has just the one defining attribute and the defining attribute of humans is "the species with bones"
For the last two years I've been semi-daily posting "What I'm Listening to Today" links here. Mastodon has some problems with threads containing hundreds of posts, so I re-create the thread once a year.
Or, alternately, every song from year two in the least practical format possible: A 301-song, 38-hour YouTube playlist (note: video #1 contains flashing):
You've heard of the "Shepard Tone", right? That's a sound design trick where a sound appears to continuously increase in pitch without ever retreating back down to give itself space. There's a variant of that for drum beats called a "Risset Rhythm".
This song, from a Telafon Tel Aviv/Belong collaboration, uses the Risset trick plus some seriously weird production to make a dreamy, alien, not-quite-danceable dance track:
Decided to try making a higher-quality encode of the "music video" I made and uploading it to Vimeo. Discovered Vimeo now has a "weekly limit" of 500MB upload unless you upgrade to a pay tier, which effectively means it is totally impossible to ever upload a video of larger than 500MB unless you pay. Even the "just okay" encode was 720 MB. (The high quality one, which I'm not sure I picked efficient settings for, is like 3GB.)
@tsrono It's definitely weird that they punish uploading one 3GB video every seven years and reward uploading one 500GB video every week. OFC the point is to make it just inconvenient enough you upgrade
@hikari@rf@whitequark so like in the case of Rust the language is very tightly coupled to the "ABI" and if you generalized the ABI it would no longer capture what is useful about the language. Part of what's captured in a Rust function call is who is responsible for freeing any given piece of memory. How many languages even have a concept of someone being responsible for freeing memory, much less designating who it is?
@hikari Like, I want to be writing Rust, but there are a lot of things in it that come down to "this is a bad thing that was situationally necessary in order to achieve some other goal" and you want to figure out ways to cope with the bad thing and someone's coming along trying to convince you that the bad thing is Good Actually and it's just exhausting and unhelpful.
The only positive thing I can say on this front is I've also interacted with the Go community and they're even worse about this.
@hikari The "if Rust does it a certain way, it must be right" attitude is infuriating and never more so than when you're actually trying to write Rust. It leads to really shallow thinking about the language.
What's really weird is I've stumbled into interacting with the actual Rust core devs and/or inventors a few times and they're all really nice, humble people who *don't act like this*. You ask about an odd decision & they either talk about complex tradeoffs or are like "oh that was an error"