abeld

A reasonable requirement which leads to "run everything in VMs" is the need to support on-premise deployments. Often data-security and compliance requirements can be handled most reasonably (or at all) by allowing the enterprise client to pick where to deploy a single-tenant copy of the service. For this, I think the most reasonable approach is to only require VMs and do all the configuration yourself (preferably in some scripted / automated manner).

Of course, in this case, (unless you install a private cloud), you forgo all the convenience and advantages of a cloud infrastructure (so one can argue that this wouldn't really count as 'cloud agnostic'), but since such on-premise deployments should only be required by big enterprise clients, they should have deep enough pockets to pay for it.

You make the owner responsible. I.e. if the driver can be identified (or the owner identifies the driver) then you can fine the driver, otherwise you fine the owner.

The type of ventillators required by the most serious cases are much more complicated: as I understand it, it involves push a tube down to the lungs, and the machine breathing instead of the patient, i.e. it has to carefully monitor and regulate the pressure etc. Already the "push tube down to the lungs" part is quite a challenge: avoiding damage to the vocal cords, or to the lungs, etc.

Any suggestions for MDM for Linux laptops? Most device management solutions I have seen are for either Windows or Mac, but is there one that is accepted by auditors and is not utter garbage UX wise for the user on Linux, where the user is most likely going to want and have full admin access to their own laptop? (I.e. since the user in question is a developer, I feel a strong aversion to not trusting them to do system administration on their own laptop.)

I would assume the "engineers vs accounts" is due to the output not being intended for the coders, but the managers. I.e. you only have accounts for the managers, but you price based on how large a team they are monitoring.

(This is just a guess, I have no connection to haystack)

An easy solution to that is to find a homeless person nearby and use fake IDs -- i.e. bribe someone else do the transaction instead of you

Every experiment will be based on some sort of theory: without that, you can't design the equipment, and you wouldn't be able to interpret the data that is generated.

If by "so far have shown nothing for all their effort" you mean that no new results were found, that isn't due to the current theories being bad: in fact, it is due to them being too good: they describe the results too well and thus there is not enough difference between the current theories and current results that would require a new theory.

Someone mentioned before (in a comment on another similar news item) that although the rocket is tall, after landing most of its mass is at the bottom: the engines are heavy, while the rest of the rocket is mostly empty fuel tanks. Hence it is feasible to keep it upright with the relatively small legs.

Two aspects one might consider when designing a tax is to make sure that it affects each person slightly, so that it won't be worth it for them to protest against it from a cost-benefit standpoint (which also means spreading the tax over as large a population as possible), and to ensure that it can be collected efficiently, that it is easy to enforce and hard to evade it.

Such an internet tax can be considered actually pretty good from these aspects: assuming it is capped (as was announced after the initial uproar) its fairly small compared to the cost of the subscription, and it is essentially collected by the ISPs, who already have the billing mechanism set up and need either licences for the frequencies they use for mobile internet, or right-of-way for the cables they use for the wired internet service and thus can easily be coerced by the government to collect this tax. (for example, income tax will be collected much less efficiently, due to tax evasion, etc.)

Of course, another aspect is what behaviour the given tax will reward / punish, and from this viewpoint such a tax (in any form) is catastrophic, but these two aspects can a lot of the "artificiality" of certain taxes.

Without knowing more about the data, one possible cause might be sim cards that are not used by actual humans, but for example by smart meters, security equipment, etc., which only have to report to one central location and thus have only one contact.

When using mobile phone data, filtering out such "artifacts" can be a big issue and it might not be possible to do accurately