bjorney @ bjorney @lemmy.ca

Posts

0

Comments

275

Joined

2 yr. ago

Yes, it was hyperbole, but saying "CodeWeavers does contribute back" is really downplaying it, many, if not most of the wine development is done by CodeWeavers employees (including Alexandre Julliard). Mac users buying crossover was pretty much the main economic driver turning the gears of wine for the 10-15 years before Valve started sponsoring it as well.

still can’t trust them long term because profit

The company is an employee owned trust (co-op) if that lessens the blow

The "Paid app" he is referring to is wine for anyone too lazy to read the article

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)

They are right - the mod is 100% abusing their privileges, don't know why they warranted the downvote

It absolutely improves with practice, and once you have settled on an aesthetic you like you can simply reuse the code, e.g. store all your color/line properties in a variable and just update each figure with that variable

My thesis had something like 30 figures, and at multiple points I had to do things like "put these all on a log scale instead" or "whoops, data on row 143,827 looks like it was transcribed wrong, need to fix it"

While setting everything up in ggplot took a couple hours, making those changes to 30 figures in ggplot took seconds, whereas it would have taken a monumental amount of time to do manually in excel

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

I run a half marathon 1-2 times a month, and the costco poutine (2000+ calories) really hits different when it's guilt free

You should try scrolling up and looking at what the context of the discussion is. Someone asked what was being subsidized, I answered, you swooped in with a bunch of self righteous off-topic remarks.