A bit off-topic, but in a shell pipeline like that, if you put your pipe chars at the end of the line you don't need backslashes and you can comment out bits of the pipe for devving.

This little change was mind-blowing for me so I always try to share when I can :)

thanks :) i prefer to have the pipes on the new line so it’s more clear how the data flow works, but that’s a cute trick.

> You should be rejecting the PR because the fix was insufficient

I mean they probly could've articulated it your way, but I think that's basically what they did... they point out the insufficient "fix" later, but the root cause of the "fix" was blind trust in AI output, so that's the part of the story they lead with.

Not that weird. Idle desktop isolates the effects of the change to get a worst case scenario. Would be interesting to see a light activity test too though - see if you still get a noticeable difference.

If I were someone who ran ChatGPT then yeah, I'd have something to improve. But most of us aren't, and can't do anything about it - so might as well make lemons into lemonade instead of getting hung up on the obvious and unchangeable fact that our future is filled with AI garbage.

Because it was written in ALGOL 60, none of the mainframe devs are willing to touch that code, and the dozen other clients probably depend on the broken functionality.

I have. Better than FaceID and under screen but I still prefer on the back. It had other benefits and just felt nicer than in the lock button

If it doesn't have to be on the back, he can just buy a phone with a fingerprint reader on the side today.

I see what you mean now. Having owned both kinds (and under-screen), I think they still have a point though - on the back was (slightly) better and I wish they'd come back.

I would personally rank a traditional iPhone home button sensor and the backside sensors on certain Android devices as equally great for unlocking while sliding the phone out of a pocket and general convenience.

Side button sensors work OK, too but I have much more misses on my supposedly more "modern" side button sensor phone than I ever had on old Pixels or any old iPhone with a home button sensor. I assume this is due to the size and general shape of a side button in comparison to an iPhone-style home button or old-Pixel-style back sensor which are bigger, indented and finger-guiding.

I submitted a patch for an annoying terraform provider once. It took about a week to fix and almost 3 years for them to merge it upstream. I got to learn Go and gained a much more solid understanding of how terraform works. I gained more from undertaking the project than from the actual fix.

> Consider the way you think it should be done is not the only "right" way and you'll open more doors for yourself.

Absolutely.

Had this exact experience and why I don't bother anymore and fork if it's absolutely necessary.

Sealed interfaces and records allow you to effectively build sum types. Switch expressions with type based pattern matching really streamline certain patterns. Type inferred vars are massively welcome. Streams and lambdas are pretty old by now, but they are much more widely embraced in e.g. frameworks and std libs which is nice.

Independently none of these are game changing, but together they provide much improved ergonomics and can reduce boilerplate. Now if only we had null safe types <3.

> one of the few therapeutic skills that are generally offered to men and that genuinely considers the problems that men face.

These things are not OFFERED to men, they are available for the taking if one is so inclined. Your options do not depend on your gender, but many will reject them as if they do. Therapy? It's not just for sissies. If men are so tough, why do they need society to OFFER solutions to their problems?

They say exactly why they want it... "I wanted to reduce write-wear on my ssd"