brianaker

Only if they are used by janitors.

Create an open Xfinity Wi-Fi network, as well as an AT&T one. See if the TV connects to them.

This is probably obvious to most people, but I will mention just the same: do not install the antenna that the TV comes with.

A propane generator will not buy you much time or output.

If the home owner has natural gas? They should could get a natural gas generator, that way they have a continuous supply of fuel if the grid fails.

Grid and gas failure? That happens only after a significant event, like a major earthquake. Not much you can do about those sorts of events. ( The person lives in Ohio… so not as much concern. )

Cost-wise? They would be better with a dual fuel system for heating. They live in Ohio, they probably have AC so moving to dual fuel when the AC system needs to be replaced is the smarter option.

While in the US making a bathroom a "wet room" is rare, it can be quite common in other countries.

You can totally remodel bathrooms to be "wet rooms" in the US, it is well worth it.

Kids flooding the bathroom via the tub? Not a problem. Toilet overflowing? Gross, but not a problem.

I wish I would have made all the bathrooms in my home wet rooms.

Trees are wonderful for a number of reasons, and the need for them for local climate, which includes shading and their contribution to local humidity, is important as well.

They are not, though, a significant sequestration for CO₂.

A helpful way to think about this is to consider coal. To produce coal the energy input comes from time, pressure, etc over tens to thousands of millions of years.

The significance of trees is for the local climate, or global if you are considering one of handful of rainforests.

The funny part is that people think that Zigbee and Matter are open :)

All three of them have their shortcomings. Matter requires an unsecured IPv6 network to operate; I have my doubts about it having any longterm future.

A mixture of threads and processes that can be used to match processors, disk I/O, and network interfaces.

A very long time ago, there was once a feature called "Data Blades" which tanked a commercial database vendor. A badly behaving blade could bring down the entire database. Most anyone who has been working on databases for a few decades remembers this and makes a point of either not introducing these sorts of features or making use of processes over threads.

I have not looked at the code referenced in the mentioned project, but thus far I haven't seen a model that could craft a complete SQL parser on its own.

There are a number of problems, and design decisions, that a developer decides on when writing a database that I don't see any current models… just because you have the ingredients does not mean that the stew is edible.

Why not use a crossover driver?

The loudspeaker would have used one; a driver is both cheaper and of higher quality.

If you don't need to manage cooling?

Then you are likely needing to manage humidity.

It does have its use cases :)

"I’ve noticed that we just don’t have outdoor cats in our neighborhood"

Stop neutering cats, encourage alley cats.

You obviously have not been following Subaru, while what you are saying was once true, it has not been true for several years now.

Google "Subaru battery", read about all of the additional electrical problems that are the result of Subaru being unwilling to fix a problem that is the end result of them selling your data.

Subaru stopped making reliable cars somewhere around 2014.

US Law, i.e. Federal Law, for e-bikes is 15 U.S.C. 2085(b) and additionally Title 28 Chapter I Part 36 Subpart A § 36.105.

Pedaled vs throttle is an ablest issues; not everyone has picked up on this.

MySQL never had a problem with scaling to multi-core systems; Linux on the other hand did have a problem and its problems became everyone's problems. In the early 2000's the answer to multi-core Linux issues was to buy a system running one of the commercial UNIX. By 2006 or so this became a non-issue for Linux ( for the most part ).

Postgres uses an old design model which predates threads; I have no idea if they have made any progress in updating their design. In the past I have heard the core devs talk about how difficult it would be to do this.

Oracle Database moved to a hybrid process/thread model at some point, this is the superior solution ( I have no idea if it was done well or not, but from standpoint of how to achieve better leverage of CPU vs IO, this is the way ).

If the PG devs had enough time/money, I am sure they would move towards a hybrid model where the focus would be on processor affinity with IO being all tied to events.