There is no honor amongst thieves.

From the beginning, my comparison to on-premises enterprise servers vs. cloud-based servers has been a fundamental premise of the cloud sales teams and the assumptions (based on those assertations) of the customers in how they would be used. In a testing and development environment, the ability to turn servers off and on based on need and thereby lowering the costs is essentially true, assuming the development and testing teams are not global (requiring most or all of the servers to be on). The production servers, on the other hand, which must be on all the time, have costs which are typically higher than on-premises servers, even when the on-premises servers are utilizing cloud storage with their high cost to transfer data back from the cloud. The real value of cloud servers is the ability to extend processing power, especially horizontal extensions (multiple dynamic nodes) and the nearly automatic cloud storage continuity. If we look at cloud vs on-premises using the "car purchase" model: on-premises is a purchase (generally) like purchasing a car; hybrid systems (servers on-premises and in the cloud) would compare with leased car pricing; and finally, the all-in cloud would be similar to rental car pricing. Over simplifying, I know, but the model has worked for me over the entire time "cloud" has been around. Some specialty clouds a la IBM Mainframe and Oracle on-premises clouds may have a different pricing dynamic but I have not seen a ton of those (more specialty Oracle applications with specific applications than IBM).

Scattershooting: They are expensive. They rely on software updates to continue to function. They require your biometrics. What if, at the moment you need it, the battery dies? Will they have tracking enabled? Why can't you try it before you buy it? What if you are disabled from the attacker and you hand it off to your spousal unit to protect your home? The questions are endless. The market will unlikely support it.

You can't cut off the top of a blanket and sew it on the bottom to make it longer. Daylight is the same way. Just stop messing with it and let's move on. DST is my vote.

The ongoing notion is the EV is "clean," regardless of the source of the electricity it feeds upon. Sure, a lot of it is solar and wind, but a significant percentage - at least in the US, is still natural gas and coal. The other issue I see is the impact to the roads. How are they going to tax an EV for road usage? Our gas (petrol) cost includes taxes with which to repair roads. Where is that tax going to be collected on EVs? I've never heard an answer to this and they wear out the roadways too.

Anyone believing production workloads can be run in the cloud for less than in a privately held or co-lo environment doesn't have all the facts. Cloud provides Opex vs. Capex and, in development/testing environments a potential to reduce costs (assuming the systems aren't running 24x7).

Given the fact that daylight can't actually be "saved," why can't we just revert to the standard time zones? I'm not excited about permanently going to work, and having schoolchildren going to school, in the dark.

Not to mention that 1000Mbps is rarely what you get on average. The upload and download speeds can vary a lot, typically downward. The other pieces to this include lag, latency, and jitter.

Annual revenue, net value, and purchase price are all usually different. An unnamed company that I deal with at work is a $200MM annual revenue company and the CI who bought them paid over $400MM to acquire.

So freakin' awesome!

Shouldn't the effects of multiple G's of force during takeoff and landing be counted as affecting the wine? Just wondering...

non-criminals are opposed to smartguns (or AI) also. I certainly don't want an AI preventing from saving my life, or someone from my family, by mistake.

That's not entirely true. Narrow scope here but as an example, Microsoft 365 runs on Windows or on Mac and you can repurpose the licenses whenever you change platforms by uninstalling on one and download/installing on the other.

That's called a "caucus" in Iowa.