It’s not “people vs persons” but “those people vs they”.

Conversationally, “those/these” distances you from the group you are talking about, which is humorously weird when it’s your family you’re talking about.

It’s not the meaning of the words, but habitual (and often fleeting) attribution around them that tripped you up.

PS: “People” are uncountable, “persons” are countable. That’s basically the whole difference between the two plurals. Although it’s rapidly disappearing, as “ten people” won’t raise a single eyebrow in a conversation.

In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.

Considering that git doesn’t need federation, and email is the grandfather of federation, sourcehut has a working version of it this very moment.

Oh yeah, please do imagine there is no such thing as a time zone.

On an ellipsoid!

Teeth cannot produce enamel. Enamel is not a living tissue and it was produced by cells outside of the tooth in a coral-like manner. In order to grow a new tooth, you need it to be fully surrounded by specialized living tissue for the whole growth cycle.

PS: I honestly expected something like this to come out of bioelectric computation research, but progress seems slower there. Or rather knowledge and techniques in other fields is reaching critical mass, giving us these advances.

I could write a long tirade on the terrifying flaws of this logic, but instead I’ll just share a reminder that barely anyone is the villain of their own story.

Sorry, but you don’t get to claim groupthink while ignoring state of Apache when Nginx got released.

Apache was a mess of modules with confusing documentation, an arsenal of foot guns, and generally a PITA to deal with. Nginx was simpler, more performant, and didn’t have the extra complexity that Apache was failing to manage.

My personal first encounter was about hosting PHP applications in a multiuser environment, and god damn was nginx a better tool.

Apache caught up in a few years, but by then people were already solving different problems. Would nginx arrive merely a year later, it would get lost to history, but it arrived exactly when everyone was fed up with Apache just the right amount.

Nowadays, when people choose a web server, they choose one they are comfortable with. With both httpds being mature, that’s the strongest objective factor to influence the choice. It’s not groupthink, it’s a consequence of concrete events.

On the other hand, if it works in Firefox, it’s likely to work everywhere else.

I use Firefox for development and then, barring some weird chrome bug, things just work everywhere.

Sourcehut

Thorium reactors have a cleverly dumb failsafe. If reactor control fails, there’s a plug that melts and drains the contents into a container that’s not fit for runoff neutron generation.

That’s an example of a failsafe that fits its purpose. It’s still possible to fuck it up, but it would take a lot of effort to do so.

And if there’s a bug in that code, you’re fucked.

Safety features should work if everything else fails. Their failure mode can’t be “fuck it, it didn’t work”. Which is directly opposite to the failure mode of a subscription based service.

Wealth itself is a stronger predictor for future wealth than individual performance.

That quote of mine doesn’t talk about success, nor wealth itself for that matter. You’re ignoring everything in the message to argue against a statement that was never made in the first place.

Please reflect on the fact that until you joined the discussion, we didn’t talk about equating success to luck.

Afterwards, you will likely notice that your jackpot argument reinforces mine.

Millionaires often worked for their money. Billionaires often worked for their first millions too. Problem is, difference between a billion and a million is about a billion.

On the other side of the argument, the amount of people that work harder and smarter than any given billionaire and have nothing is simply staggering. If it wasn’t down to luck, they’d all be billionaires.

So yeah, it is dumb luck. Randomness is not uniform, and someone ends up being close to the time and place of a local spike.

Turns out, I do need therapy.

Nope. You just grow confident to not notice the blunders, and learn to recover fast enough to not persist when it would be detrimental.

Native speakers making mistakes or not caring to stick to the rules is one of the forces behind languages’ evolution.

Seems to me, you’re dealing with a micromanager.

Personal recommendation - put things into writing. When you get your assignment verbally, write it down with assumptions you have to make to fill the gaps, and send it to the person who gave you the assignment, with the person responsible for your teams’ results in CC. Basically an “I heard you, and I’m starting the work as described below”.

Communication is one of the most important skills in software engineering, and this way you get to practise it while probing the social waters of dealing with management.

Try it, see how it goes, adjust accordingly.

Sourcehut. The answer is sourcehut.

You don’t even need an account to submit patches, just configure git send-email.

I mean, Comic Code is pretty damn good.

What irks me is people swearing by vinegar like it’s better than anything

Ah, so vinegar was never the issue.

Stop listening to people that talk too confidently and live your life. Hell, recommend they use vinegar as drainage unblocking agent with the same gusto, just to have fun. It might even work for them.