this can cause unintended behaviors when this memory address is accessed, such as blushing, wagging, keysmashing, or awrawrawring
I got this wonderful piece of art from @email@example.com
with myself and my partner @68kHeart. I love how it turned out!!
I would be like "oh, this is probably some .NET stuff they have to work around", but if the solution is legit just "make it a function that takes unit", that's something the compiler could just abstract away for you. And yet,
Trying to do a project in F# because I'm likely going to need .NET fuckery down the road. It…sure is a language! I love that they're like, "yeah, we wanted an OCaml-style language because of the safety it provides, but also you shouldn't try to capture all failures and represent them as types and instead throw exceptions", like ??? doesn't that defeat the purpose of choosing an ML-style language to base your work off of??? Even Haskell devs are like "yeah, exceptions were kind of a big mistake"
There's an experimental try-block syntax that does address the issue of capturing errors from the question mark operator. But that's like, great, now we're back to wrapping everything in try blocks again because error handling is a problem!
You have many useful functional programming concepts, like .map() and .and_then() at your disposal, but then you have to define lambdas for operations because everything is methods — oops!
The question mark operator really drives home how much of an issue this is. But even then, it's still very hard to use in a way that lets you handle and structure errors nicely.
I'm trying Rust again and I think I realize why I keep hitting a wall with it:
1. It uses a lot of concepts from category theory and already established functional programming languages, and then…just doesn't use them in a way that's helpful; and this is made worse by
2. Lots of macro magic, either by crates or by the compiler, that is not always intuitive and opaque in how it works.
just snuggled up under the covers, cuddling some plushies, and casually reading the FontForge manual before bed
as one does
Typography on the web problem:
I have a font that consistently needs to be scaled by a factor of 1.25 to match most other fonts at the same size. I’m leery about having to scale up the body font, and then scale back down inlined bits in case a visitor replaces the fonts I choose.
I would use font-size-adjust instead of explicit sizing, but it doesn’t have good support.
My other thought is I’d have to manually edit the font to adjust the sizing, but I don’t know how easy that would be. :/
still better than Adobe Illustrator tho tbh
*Due to increased bot signup, manual approval is required. Please write some applicable request text on signup.*
This Mastodon instance is for tech workers, academics, students, and others interested in tech who are LGBTQIA+ or Allies.
We have a code of conduct that we adhere to. We try to be proactive in handling moderation, and respond to reports.
We're not a free speech absolutist. We're not interested in Nazis, TERFS, or hate speech.
This instance is meant to be a friendly, welcoming space to all who are willing to reciprocate in helping to create that environment.
If you’re ever unsure, ask first. Use CWs where required.
If you’re accused of causing harm, either take some responsibility or ask moderators for help.
Our moderators are here to listen and respond to reports.
This instance is funded in part by Patreon donations.