Or at least I do.

There’s just something extraordinarily relaxing about going from the high heat (though obviously not too high) until one can’t bear it, then transitioning to a cool off.

My phone charge lasts longer than 30 minutes. And it’s provably water resistant to tub depths.

I certainly don’t code in the tub. Strictly reading and discourse.

Sometimes posting on Hackernews.

It’s one of the high points of my day (the soak, not the posting).

This “I wonder” just screams lazy thinking.

The community makes the system and decides what’s tolerable. That is to say, the community decides the type of users it expects to serve.

When your own example of laziness is to provide a script and someone fails to run a script; you’re comparing to a time when RTFM was the Linux norm. But those days where RTFM to newbies were tolerable are long gone.

So OpenBSD was the friendlier community then; it’s a niche and insular community today.

So while I agree it’s not a terrible community, I also wouldn’t say it’s inviting.

> I meant what I wrote, that I find the community to be the opposite of "notoriously terrible and unwelcoming to newbies," by which I do not imply newbie-friendliness in a kindergarten sense.

I mean, it’s not inviting to newbies either; which is the plain reading and understanding of “opposite” of what the OP stated.

Instead it’s “tolerant”, a term which for some reason you don’t seem to like.

I’d ask if you’re Theo, mainly due to the strange back and forth we’re having over semantics and a concern over the OpenBSD community reputation.

Why do you believe pointing to the manual is newbie friendly?

In the Linux world, it took ages before it was newbie friendly (thinking Ubuntu and Mint).

OpenBSD serves an important niche, but to brand it as newbie-friendly does OpenBSD a disservice.

Or perhaps you mean newbie tolerant?

OpenOffice is by far the better name and has a potential brand recognition that LibreOffice never will.

That’s nearly the exact opposite of welcoming newbies.

To be perfectly honest, that’s fine: OpenBSD demands a steep learning curve and that you know what you’re doing.

> They found that on average, the gloves imparted about 2,000 false positives per millimeter squared area.

> Clough prepared the substrates while wearing nitrile gloves, which is recommended by the guidance of literature in the microplastics field. But when she examined the substrates to estimate how many microplastics she captured, the results were many thousands of times greater than what she expected to find.

The reason this is important is that one flawed dataset reports a hopeless situation; the other at least provides a “if we stop now” message.

Businesses aren't incentivized to maintain it and hoping that the community can support it by opening it is perhaps necessary, but it's far from sufficient.

Either the business or maintainers need to be sufficiently incentivized--whether it's through funding, reputation, or something else (graduate-student torture).

Who ensures the maintainers for these routers are incentivized to do this competently and in a timely fashion?

You haven’t answered these key questions, which are equally or more important than whether a community firmware can be applied.

How does one ensure the support for the devices is funded?

When COM rolled out, every product was very much on board.

The need for Maui in-house is for…what?

Microsoft politics. Someone who’s aware please confirm but I want to say it’s something like…

Different orgs jockey for power and you can see when the wrong orgs and initiatives influence different products.

What I can’t tell is whether it’s established teams scrambling to stay relevant. Or if it’s new teams and products imposing their influence where they shouldn’t.

But the Windows team doesn’t want to see Linux get traction, so they’ll do their part to hamper any OS shims or any native-first functions in Office.

The Office org wants to expand beyond Windows but for political reasons, the only add-in tech without platform lock-in is JS so they ally with the Azure/Cloud team to allow third parties to create add-ins.

Because of this partnership, rather than making a streamlined add-in store, publishers are required to learn the full complexities of Entra and the Partner centers.

I imagine the UX and .NET orgs are caught in similar political battles; but without any direct income or product to influence.

If I had to guess, they were in the Windows team at one point; but with the platform-independent initiatives (good) it’s been a shitshow over the past 20+ years for desktop developers (bad).

It’s not the knowledge and tech, but manufacturing-of and at-scale-use of renewables that matters here.

We can’t just-in-time install infrastructure a across the entire country in a matter of weeks or months.