It's Google analytics, and the meta/twitter/etc tracking pixels. Almost every site uses them because they provide useful data to the site owner and they are free.

the images in OPs post appear to be designed to match their site theme, meaning umatrix wouldn't even block them, because they are being served from the sites actual domain/CDN and not from Facebook/Google's tracking domain.

The buttons don't do any tracking just from existing. They only exist to encourage a miniscule number of people to repost your content on social media, and in the event a share comes from that, they may include affiliate info

All the useful information comes from the tracking scripts, which developers are also placing themselves because they are infinitely more useful. They tell you where visitors are coming from, how/if they are converting, everything they are viewing/interacting with on your site, and what the ROI of your ad spend is. In addition to telling you if someone clicked the share button.

Tracking pixels have been decoupled from the "share" buttons for at least 10-15 years

Just loading the "share" icon from the social media website allows them to see that you are reading that specific article

The buttons aren't necessary for this though. They can do that with a

<script>

<img>

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)

Gilmore girls isn't mentioned in this article but it's been measured before, it's less than it's always sunny

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.

Wouldn't there be an argument for a kettle, where as you heat it some heat (including steam) is lost through the top?

Yes, but evaporative cooling happens in a microwave too.

The microwave has an enclosed cavity that captures this loss and so reduces future loss as the water heats.

Microwaves don't have an airtight seal. If they did you would be able to blow the door off if you heated a large enough bowl of water.

Also, the kettle heats a certain quantity water of which only some is used. A mug in the microwave would heat only the water you use.

You don't have to fill kettles up to the top to use them

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

Microwaves don't generate heat directly, they produce ionizing radiation, only some of which gets absorbed by the thing you are heating. Energy is also lost as heat in the coils, and from spinning the plate. Microwaves are only between 50-75% efficient

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