Deprecated associations is nice, though. Stitch Fix had our own implementation that worked, but wasn't great, and it would've been nice to have first party support, so that's nice change!

Job continuations…I'm not sure about. I would have to use it in anger. Nice idea, but how observable is it?

The structured event thing is nice, I guess, but it feels like another NIH thing that should've used a standard like OTel, providing instant integration for all apps with all vendors out of the box, first party. Nope.

NGL, I think Apple's overall design team is a bunch of men whose spouses or parents handle all of their daily lives for them and so it never occurs to them that a phone call or text message might actually be important

I guess at least if I see a call I can answer it - with an Apple Watch on, I cannot. I also can't delete the phone app from the ipad, even though I will never in a million years take a phone call there - I think I disabled it but what a nightmare.

The only time I've been there for anything else was to find out which TV's UI was the least horrible (winner was some LG that I had to spend an hour disabling thirsty google engagement crap)

My guess is that it's what most people do which is to use React or whatever and not even bother with Hotwire and friends. And to the extent Rails makes that difficult, I bet devs move away from Rails to e.g. python or JS-based frameworks.

Did…someone try to assassinate you?!?!

We even talked to a dev who maintained one of the libs we used and they asked about issues we had they could help with - there were none! We just used the lib as designed and stayed within public API boundaries. Said lib was mature, so not buggy.

Option 2 is a good idea - at a previous job the CTO was all-in on supporting OSS work, but the problem was that we used all our tools in vanilla ways - they worked and didn't need updates to accommodate us. Just donating money would've made more sense

My takeaway is that you should never ever give GH or RubyGems ownership of your projects to anyone that you don't 100% trust to carry for the project in your absence. The RG/Bundler teams either didn't do that or misplaced their trust or both. (This doesn't excuse the actions taken of course)

I swear to god the amount of admin required to prevent someone from getting something they are not "entitled" to is a lot - and I do not have exec function issues at all and am good at grinding/admin. I don't know how someone with a stressful job could deal much less more serious issues.

Is this the thing you are using for Inline RBS? Or is there a more formal definition?

github.com/soutaro/rbs-...

I’m surprised it uses optionality as a concept at all - seems more “ruby” to say NilClass is one of may return types - there’s very little special about as compared to other langs.

vim, to me, seems intuitive once you learn the concepts. My only ever exposure to emacs is that it seems like you just have to memorize a lot of stuff. Lots of examples like this.