Quotas we barely ever use anymore, to the extent they exist they tend to be integrated into applications if there's a point to them. Wasting employee time is extremely expensive compared to disk. Most systems support snapshots on multiple levels already, from OS/LVM and virtualization layers down to the SAN/NAS. ACL's, after 30 years, managing probably about 10k unix systems, I have run across a handful of situations where it would have been useful, and exactly zero cases where the cost benefit ratio would have made it economically viable. Most modern filesystems support them, but for applications that need that access granularity, the functionality tends to end up in application or database layers. Minor cache improvements pale in comparison to simply throwing the entire performance demanding application on flash-only, FusionIO or NVME disks.

Boot environments like that have been done in various ways for as long as I can remember, where the earliest were basically the diskless NFS based clients where you could simply copy the filesystem and run the update on that. After that, any simple disk mirror could be split off and cloned for a snapshot system to work with. Thankfully, such functionality is approaching irrelevance as well, as application design is growing up enough to actually build redundancy into the application layer so you can take any number of servers offline at any time. Snapping a root filesystem isn't exactly necessary when the application is built to live on a server instance that will disappear and be replaced with a fresh disposable instantiated image on next reboot...

And yes, most features mean pretty much raid, compression, caching, deduplication, snapshots, etc.

It's not that it's a bad filesystem, it's a quite good one. But the problems it solves are becoming legacy issues of less relevance in an industry where the discussion is shifting toward whether there will be an OS as we know it underpinning the application infrastructure at all.

Making ZFS incompatible with linux was the whole point of putting it under the CDDL from the start.

That said, having run ZFS since pretty much the start on Solaris servers here, it has to be the most overhyped piece of software ever released. Initially it was pretty much unusable for things like database loads, it was unstable as hell and had serious memory usage issues. These days, the glaring problems are largely fixed, but in an enterprise environment most of its features are of limited use as most of the storage will be on centralized SAN/NAS arrays anyway.

The whole discussion is one of those that gives me flashbacks to the 90's, same as when some database guy specifies that they want their volumes on this many striped spindles...

There's a reason why Sweden has one of the highest rape rates in the world and it's not because there are that many actual rapes going on.

But it is somewhat amusing to watch the racists and the feminists fight over it, as the racists claim it's because the immigrants and the feminists have to constantly switch their realities back and forth between 'it's only a statistical issue' and 'but rape is everywhere!', depending on the situation...

But yes, if you read the original police documents, the purpose of going to the police was to force an STD test. That the US was involved I rather doubt, as any borderline chargeable offense will automatically be pushed by the police and prosecution whether the supposed victim wants it or not it's quite enough that an activist prosecutor like Marianne Ny smells some publicity and the opportunity to 'send a message' to start that chain of events and completely screw up the victims life far beyond the original issue. Hopefully Ny's utter incompetence in this has put a permanent black mark on her career.

'In some way or another' probably refers to the various general social security systems that are in place. Technically it pretty much should be hard to starve in many European countries. In practice, many 'normal' will probably kill themselves rather than go through the hoops necessary to ensure payout, while exploiters can make a very decent living off abusing the systems.

Personally I'm in favour of universial basic income, provided all other benefits are removed at the same time. You get what you get, and no, that won't let you live in a decent area of a major city, there won't be any extra payout for special needs, etc.

I think the reason it won't end up done in Europe for a long time is simply that the welfare dependents, their organisations and the welfare administration workers will oppose it. Far too many special interest groups who'd stand to lose a lot.

And if docker means you're going to spend more time managing OS level instances, then any savings on hardware are often eaten within weeks of deployment. Shared systems are a PITA if there's any need to coordinate between multiple users of those systems at all.

The fact is, I suspect the only way to avoid triggering manpower costs while implementing docker currently in a large company is basically to deploy it on a one-container-per-OS-image basis. Basically as an application packaging method. Which of course means there won't be any cost reduction on hardware at all. But then again, nobody cares about that, which should be obvious from the lack of optimization in the actual software running.

If you need to live patch your kernel you've got a misdesigned application. Failures happen and if you can't design your application for redundancy, don't expect uninterrupted service.

If you need to live-patch kernels in your cloud infrastructure, you need to go back to the drawing board because you don't have a cloud, you have a SPOF.

I'm not saying it can't happen, I'm saying that when exercising good judgement, even humans drive to allow leeway for such things. If there's a car that weaves or sways, if it drives close to the lane separator, drives too fast, too slow, etc, you keep enough distance to be able to deal with any random behaviour by that car safely. When you know there are difficult short on-ramps and the lane beside you is free you switch lanes to let other drivers on without any risk of causing a problem situation. Humans do it when we're doing things right. An autonomous car could be programmed to always keep the optimal freedom of action.

"The difficult problem is that sometimes you don't get the luxury of doing that, and unexpected situations can be created faster than you're able to react."

Yes, but the way most traffic situations are designed, it's our big saver that it requires usually not one, but two persons making a mistake for an accident to happen. I've been saved from the consequences of being an idiot by someone else not being an idiot and planning for me being an idiot. And I've saved many others by noting that they're not paying attention and increasing distance, leaving them space to be stupid. Not to mention the number of lives that have been saved by traffic planners saying 'humans are idiots, lets make a roundabout here'. So, if an autonomous car can be programmed to not do the stupid things we do, what are the situations where the best response isn't simply 'make sure it doesn't get into such situations'? And could a human deal with them?

I mean, some things are impossible to deal with. You're not going to be able to handle things like a car going through a guard rail on the overpass and landing in your lane. Some things are more probable, but very hard to deal with as well, like someone deliberately arranging for a frontal collision in a higher speed countryside road. There simply aren't any safe trajectories or distances, so that can't be planned for, but that's not really a difficult decision but more trying to avoid the frontal, where the autonomous car would probably have an edge in reaction time and more accurate sensor feedback providing all viable physically possible options.

It's an interesting problem, but it's not entirely easy to figure out situations where our more complex reasoning skills will actually do us any good once the actual shit hits the fan, or if all situations where such reasoning skills may be of use are actually due to failing to use them earlier.

Yep. But the autonomous car wouldn't, and I wouldn't care as I'd be downing a beer and watching TV on my way from work.

Indeed. But in that case you have planned your driving so you have, like you say, plenty room in front and behind of you, so you can safely brake or accelerate out of the way of the merger. You don't need to sideswipe someone, because you'd planned for such a situation. You avoid accidents by deliberately planning to be able to deal with dangerous, but physically possible, movement of everything else in the environment.

If your options end up being only really bad ones, you've made at least one, and probably a whole sequence of really bad decisions that have limited your possible actions. That's very human to do, I fiddle with the stereo while driving too fast with not enough distance in rush hour traffic with a lorry to the side with the best of them. But it's not something an autonomous car would have to do, so when comparing human driving with autonomous car driving it's better to use situations that an autonomous car would be as likely as a human to actually get in to, rather than the ones caused by our own bad judgement.

Why is there a car in the adjacent lane in a high-speed situation with objects that can conceivably exhibit behaviour that could cause in impact faster than you can do a controlled break? Sounds like you're driving too fast and tailgating someone while you're passing someone else. How about, you know, not doing that? Accident avoided.

The trick to avoid serious accidents is not to be able to make complex judgement calls in an emergency, humans suck at that, and life isn't Groundhog Day where you get to practice a dozen times 'til you get that call right. The trick to avoid serious accidents is to do your best to ensure you're in a controllable situation as much as possible. You should be keeping enough distance to be able to break when someone more than slams their breaks. You should keep enough clearance to be able to accelerate or decelerate if someone starts moving into your lane. You should keep excessive distance to cyclists or pass them at a controllable speed.

An autonomous car can keep safe margins far better than a human can, and it's much more capable to actually keep the situation within the actual limits of what it can deal with. Because, above all, it wont delude itself into thinking it can actually make perfect complex judgement calls within fractions of a second.

If a child can run into the street from a blind spot faster than you can break, you're driving too fast. The autonomous car will not drive too fast to break in such a situation.

If the child is deliberately hiding in a place it shouldn't be, near a higher speed road and manages to quickly cross what should usually be a wide clear area around such roads (or in an unpopulated area), then there won't be time for a human to react at all. An autonomous car could probably cut down the speed a bit, but avoiding people who deliberately try to throw themselves in front of traffic simply isn't doable or even something to care that much about. You're not going to be able to avoid jumpers, or the human cannonball either, nor is an autonomous car. As the other reply pointed out, whether it's wildlife or people, usually the best option is to simply do a predictable controlled break unless it's basically a slow-motion situation playing out over many seconds (such as road conditions making braking very ineffective, while speed isn't particularly high).

Libertarianism doesn't require faith in that. The mix of people actually enjoying acting out of altruism and the situations where people acting for their own good inherently results in the good of the commons (competition, efficiency improvements) is enough for a lot of things and is quite demonstrable without any faith needed.

Well, if you pave the area that the livestock occupies at least. Well, no, that doesn't work, you still need that area to catch carbon through vegetation. But you can't let something else eat the vegetation or they'll crap, breath and dissipate it again. So you need to sequestrate the vegetation. Better drench it in pesticides too so no insects consume it.

Hang on... that sounds like it's actually one of those ecological cycle thingamajiggies, it just could be that the actual problem is the input of sequestrated materials into the cycle rather than the particular point at which a specific carrier is recycled, as that will just get replaced by another carrier/emitter if the consumption point is moved.

When you're writing scale-on-demand cloud applications, the boot time of a new vm is most of the latency of additional capacity coming online.

Yeah, you know, if you ask a human in 50000 years whether 'noon' means 'midday' or 'midnight', he'll say "zxyathslthe?" "blortpmi?".

With changes in the range of thousands of years, language will change orders of magnitude faster than the specific number we ascribe to 'noon'.

And yes, it is something you can easily ignore, as unless the human lifespan stretches into thousands of years, it's not like anyone's actually going to notice during their lifetime.