You have to explicitly check if the return value is an error and propagate it. You write the same boilerplate if (err) return err over and over again, which just litters your code.

That’s only true in crappy languages that have no concept of async workflows, monads, effects systems, etc.

Sad to see that an intentionally weak/limited language like Go is now the counterargument for good modeling of errors.

Right on. Ignore wedge-drivers.

Can you link to the original?

Performance is the major flaw with microkernels that have prevented the half-dozen or more serious attempts at this to succeed.

Incurring context switching for low-level operations is just too slow.

An alternative might be a safe/provable language for kernel and drivers where the compiler can guarantee properties of kernel modules instead of requiring hardware guarantees, and it ends up in one address space/protection boundary. But then the compiler (and its output) becomes a trusted component.

Yes, it is a huge pain, especially if you want to have round-trip interoperability with humans using markup. Wikipedia had a major challenge with this when they decided to add a rich text editor alongside wiki markup.

Prices have been going down around here.

yeah, communities should have subject tag sets. I don’t care for anime or sports or video games - i should be able to turn off those tags. Not block 50 different game communities ad hoc

This isn’t true at all.

Just as quick examples, under Democrats, gay people got the right to marry. The Affordable Care Act was passed. And real pay has gone up under Biden.

That’s not mentioning the major climate and infrastructure legislation, dismissal of student debt, rights for DACA holders, etc.

Surge suppressors do not drop extra voltage to ground. They selectively short out surges between whatever two conductors have a high potential between them.

No ground conductor means there cannot be a high potential between it and anything else!

he does love the cellular automata.

If your company is using story points to “measure” developers, they are completely misusing that concept, and it probably results in a low-teamwork environment (as you describe).

The purpose of story points is so a team can say “we’re not taking more than X work for the next two weeks. Make sure it’s the important stuff.” It is a way to communicate a limit to force prioritization by the product owner.

And, in fact, data shows that point estimation so poorly converges on reality that teams may as well assign everything a “1”. The key technique is to try to make stories the same size, and to reduce variability by having the team swarm/mob to unblock stuck work.

Who creates these tasks? They need to close the year old items, reevaluate the work and break it down into sub-5-day chunks. If there are so many unknowns that it’s impossible to do that, the team needs to brainstorm how to resolve them.

fyi the NeXT OS is called NeXTSTEP.

honestly, I don’t want established Reddit supermods land grabbing topics in the Fediverse. The right people will find it organically based on their own motivation (as simple as searching for “reddit alternatives”).

Especially don’t want the shallow, low-quality content from default/“top” subreddits.

By definition, the 1% are the top 1% of earners in the population, so there are 8,100,000,000 * 0.01 = 81,000,000 of them, not 400.

The richest 400 are the 0.000005%.

The 1% line in the US is at $819k a year, and $60k worldwide.

along these lines, you should also know about the condensate drain from your air conditioner – since water drips out of it all summer, it has a tendency to grow some algae or mold, and if it plugs up your air conditioner may flood and ruin your ceiling/walls/floor.

it’s worth paying that AC guy to come by every couple of years even if you’re not on their service plan.

for what it’s worth, coolant is not consumed by an air conditioner – the same initial charge can last 20+ years. Low coolant either means a leak, which the technician should have investigated and fixed or ruled out, or improper initial installation.

“prove it wrong”? “as we’re told”? Do you start conversations this way?

Bro, if you don’t like it you don’t have to use it.

For most organizations, the cost of paying programmers far exceeds the cost of CPU time; benchmarks really should include how long the solution took to envision/implement and how many follow up commits were required to tune it.