some0x80070005

The poster was referring to the Model 3 Highland refresh and allegedly the upcoming Model Y Juniper refresh. That is where the turn stalk was replaced with capacitive touch buttons on three steering wheel.

While I’m not going to shed tears for gas stoves, I also think that your argument is flawed. Everything in life is unsafe to some degree. Kids drown in pools of water, yet pools aren’t being banned. Electricity can be very unsafe, yet we allow our homes to be wired with it. Storing fuels or certain chemicals can be very dangerous, but we don’t outright ban it. Why?

Because we manage risk. We manage risk by forcing appropriate containers, safety measures, building codes, etc. Gas stoves have a risk that can be managed as well if we want to. Last I checked, labs work with far more dangerous vapors yet have no problem because they use proper fume hoods. Here, there’s nothing that would stop you from going for a compromise solution demanding that all new gas stoves are installed with a fume hood capable of X amount of CFM with automatic sensors to detect the presence of either CO2 or particulates.

I’ve heard somewhere between 300-400 kilograms gas per second. The pipeline has already been shut off for weeks, but it’ll take days for all the gas that’s already in the line at elevated pressures to leak out. It’s an enormous amount of gas.

You are not wrong. It’s a feat of engineering to have a roughly 1200 km pipeline operate smoothly with no safety or reliability issues over 10 years just to get blown up. Billions of dollars just down the drain.

Unfortunately, that is such a huge economic burden to run hydraulic umbilicals the entire length of the line. It’s simply not feasible to control in the middle of such an enormous pipeline. Perhaps, ROV operated valves could be a solution, but generally, with such high pressure fluid on the inside, the valves and areas around the valves would be the relative weak points and would need leak monitoring whereas the current system doesn’t require that.

Leak has not be flared, and the Russian side has been shut in for weeks already. However, there’s 1200km or so of pipe that had gas somewhere around 107 bar average inside, and that must now leak.

Due to the special inside coating to reduce friction, seawater ingress would mean the abandonment of the pipeline. It’s just not possible to fix the line without just replacing the entire thing. I theorize it’s possible to run at severely reduced flow rates if they were able to get the water out, but that seems unlikely since the receiving facilities are not designed to handle the tremendous amount of water that would be in the system.

It’s one thing to suggest the Socratic method may not be the best learning strategy, but it’s quite another to suggest that questions are overrated. Questions are so fundamental to increasing our knowledge in an intuitive way - just look at Stack Overflow, Quora, etc. for the success in helping people find answers (of decidedly varying quality). There is no limit to creative questions a group of people can ask but there is a limit to how much a single human thinks they know about a subject or can write in a single lecture, article, or book.

Generally speaking, this situation does not seem confusing for many native speakers. The question mark indicates uncertainty about the statement instead of asking “<Statement>. Can anyone refute this or provide insight to the original significance?”. In this case, the author drew a conclusion about other data which seems to make the original article seem less important or less significant, but instead of declaring it as a fact outright, the author is choosing to mark it with uncertainty instead which will invite a discussion if they are wrong on some aspect of it.

It’s great that podman serves a good role for you, and I’m not going to argue that. My points:

1. Docker containers absolutely can be run without root. Yes, it’s not the default policy, but containers can have a user ID. If you are referencing the daemon-less root-less nature of podman, that’s a clear advantage of podman vs Docker. 2. Docker containers also have a restart policy which I use to also have them startup on machine reboot. By graceful, you must mean sending SIGTERM to the containers which Docker does as well.

Perhaps podman does these things better, but I want to point out that Docker does have many features for better or for worse.

I suspect AVEVA PI (formerly OSIsoft) is what they are referring to. PI is excessively popular in Enterprise scenarios either OT or IT.

Fully agreed on having that SQL experience guiding you on a totally reasonable solution.

However; our problem space is not high cardinality data; it more closely aligns to the first performance comparison with 10 devices and 10 metrics. The ease of getting high performance with pre implemented functions is great for us. Reliability is obviously a concern, and I can agree that if data is sacred, then choosing something built on Postgres is going to be a better thought.

Again, this is just our problem space; small scale deployments on many machines with no preexisting RDMS, low cardinality data, etc. I think it’d be a different story if we were huge, but for us, InfluxDB provides some seriously handy feature and is worth consideration if your problem is similar.

I guess this is an unpopular opinion, but I’ve found InfluxDB to be superb for being trivial to get going in a high performance way. I have never touched InfluxDB Cloud - always just InfluxDB either as an arbitrary process or container. Examples of where I’ve found InfluxDB to be more pleasant:

* InfluxDB has way better documentation on functions. For example, look up moving average by time (not points) on TimescaleDB vs InfluxDB. We use these more complex queries and have no problem on Influx. Going further, the number of functions built in is impressive with the same ability to define new functions.

* InfluxDB containers are totally self contained which is great for simple architectures. As a process, InfluxDB is a single executable thanks to Go.

* This is extremely subjective, but I find Flux easier to comprehend as a separate query vs. the use of SQL to do higher complexity functions; however, I am sure this is due to my lack of experience and know how to write said queries in SQL.

I can’t tell if this is satirical, but rockets have not proven their reliability much better than 94% for an unmanned rocket and 99% for manned. Airplanes have reliabilities on a per journey basis around 99.9999%. Even if SpaceX is full of 10x engineers who can produce rockets 10x safer than before, that gets them to 99.9% reliability.

The airline industry, for all of its faults, is multiple orders of magnitude safer than rockets. Perhaps rocket based vehicles are the future, but rocket failures must first become drastically more rare or at least less prone to everyone dying onboard in the case of a failure to be used in lieu of traditional airplanes.

Rockets - https://space.stackexchange.com/questions/8566/what-is-the-s...

2020 Airline safety - https://www.reuters.com/article/uk-airlines-safety/aviation-...

App