bjorney

Fair - point still stands though - the application only has a single breakpoint defined at 600sp from a cursory glance, the lack of an ultra-wide specific layout is just because it hasn’t been implemented rather than a shortfall of GTK (though I’m not sure you would even want to make the message view wider, as it would impair readability)

That looks like it’s just wrapping a WebView, is it not?

It looks like the CSS is just capping the container class width at 1440px, which has nothing to do with GTK

I was like you, until my mid-30s hit

Now buffalo wings will have me waking up at 3am with acid reflux even though I didn’t even register spice while I was eating them 6 hours earlier

There are low powered FM transmitters you can get for your car

FM transmitter plugs into cigarette lighter for power

iPod connects to FM transmitter via AUX cord

You tune your cars radio to whatever frequency the transmitter is set to, and it plays whatever your iPod is playing

But AMD has been making leaps and bounds improving their GPU software

They are still largely shitting the bed here. Their ROCm installer won’t run on Ubuntu 25.04 last time I checked, and the 9070xt won’t work on OSs that ROCm DOES support because the kernel and graphics stack is too old.

ROCm has been “almost ready” to be a drop-in replacement for CUDA for almost a decade. I feel like it literally would take nvidia ceasing to exist to give them the critical mass to push it over the finish line

It’s the best time I’ve had with a game since BG3 - gameplay is ‘just’ good, but the story and design are next level

Sounds like a prank I would have pulled on a roommate back in college (e.g. change desktop background to a screenshot of desktop, and then delete all the shortcuts)

Not an American, but basically decide how much risk you want to take on - then depending on that answer set aside money (0-40%) for safe investments - things like bonds (guaranteed returns) or potentially gold (lower volatility). The rest goes into a 80/20 (or 60/40, or 90/10, no one can say what’s best) split between domestic and international index funds. Things like the S&P500, Dow, and US whole market index, and then some into EU, Asia/Oceana, and emerging market index funds.

OP said it was to notify you when an alarm went off, not when it ran out of batteries.

You seem content to entirely gloss over the issue, which isn’t the pros/cons of a particular writing style, it’s that the maintainer could have said ANY of the things you said, but he didn’t

If I was the maintainer, I too would probably reject the PR because it didn’t remove the gender entirely.

Cool, but that isn’t what happened here. The PR was closed immediately because the maintainer considered using gender neutral pronouns “personal politics” - he had ample opportunity to clarify his stance, or simply comment ‘resubmit in passive voice’, but he didn’t. Clearly the problem wasn’t the active voice, it was the summary of the change, because when that exact same PR was re-submitted much later with a commit message of ‘Fix some minor ESL grammar issues’, it was accepted with no discussion

As an aside, I absolutely disagree with the use of passive voice. It’s more verbose, and harder for the reader to comprehend. It’s why every style guide (APA, Chicago, IEEE, etc) recommends sticking to active voice, especially in the context of ‘doing things’.

If goes against established norms here

What’s the established norm here. All people compiling software by source are male?

he said politically motivated changes aren’t welcome

What’s politically motivated about changing “he” to “they”. As you said, gender doesn’t apply here, so the neutral word is literally preferable.

Yes, I’m sure that PR would have been accepted instead /s

But you’re right, it doesn’t matter at all, the reasonable thing to do would have been for the guy to spend 3 seconds clicking the accept and merge button, or 6 seconds making your change. instead he wrote a comment stating that inclusive language has no place in his project

https://github.com/SerenityOS/serenity/pull/6814#issuecomment-830793992

Really?

This screams “women not wanted” to me

it’s literally easier to do on a technical level

I wouldn’t go that far. It’s still trivially easy, and arguably best practice, but it’s certainly more complicated than issuing an in-place update

If the code doesn’t change, the resulting docker image will have the same hash, and a new image won’t be created

https://github.com/jackett/jackett/releases

Jackett is literally just releasing a new version every day

and I’ve encountered zero bugs so far

This is my only complaint - it crashes a lot for me

The content of the email is very laissez-faire, e.g. "we legally have to send these ¯\_(ツ)_/¯ "

I collect these like pokemon 🙃

An absolute bastard of a workout will use up maybe 100 on top of that

An hour run burns like 600