Very few franchise dealerships would ever sell a car with problems knowingly. It does happen, because people trade in cars with intermittent problems without telling the dealership.
Compared to Craigslist where there is no shortage of people selling cars directly with current problems, intermittent problems, hidden problems, and massive paperwork issues that can stop you from registering the vehicle all together until resolved.
This only leaves the potential for massive paperwork and back due fee issues. Surprisingly common on craiglist. A spare current registration sticker gets slapped on that belongs to another vehicle of theirs, and you buy the car not knowing it has 3 years back due fees totally $1000, probably approaching $2k if it's a pickup truck (atleast in California).
My gut feeling is that most people mostly like their documents just being everywhere and being accessible everywhere. Office 365 storing things in the cloud, that's pretty much the case, you don't really need to understand where a file is (it's "in Office") or how to move them. Another bonus is not having to worry about what's been deleted. It's only based on anecdotes, but I suspect this is a lot more important to people than most other aspects of the software.
Yeah... No. Not gromking filesystem location is creating an entire generation of computer users illiterate in basic computing concepts, or even being capable of mapping through technical abstractions to answer silly things like "where are the bits you desire now?"
This is not a good thing at all, as it's creating a form of indoctrination to learned helplessness that isn't easy to get past. At least nowhere near as easy as it was in the past.
You're right that it creates that, however it's the "better UX" of not having a filesystem that leads to the use of those features, which leads to users not practising the skills, which leads to that "illiteracy".
While I personally think a filesystem has great UX for my purposes, never accidentally losing a file is a much better UX for most people. As much as it causes friction to not have these basic computer skills now, I suspect it's less "illiteracy" and more _progress_. We don't criticise people for not knowing how to ride a horse today, because we have public transport and cars. We don't criticise computer users who can't use a 5.4" floppy drive because we have USB sticks and cloud storage.
> computer users illiterate in basic computing concepts
What’s a “basic computing concept” anyway? My 4 year old granddaughter doesn’t know a bit from a byte or a file from a folder, but was able to pick up an iPad and intrinsically start using it to do far more powerful things than I would have been able to do at 4 years old on a IBM Model 370 back in the 70s
It was a neutron detector that stored the the position, energy, and time stamp into the database. The design spec was 10,000 neutrons per second, so that was the origin of the time limit.
Of course, half those neutrons arrived within a 20ms window, so we had a buffer to handle the load. However, however, if the average remained above the limit, the buffer would fill up. There was a brief discussion of just ignoring events when the buffer was full, but that could introduce systematic errors in the data that would be impossible to detect, so it was better for the database to just crash.
The solution was to tighten the slits on the neutron beam to lower the count rate to the point that we never filled the buffer. Granted, we were testing a high flux technique that, so that was a bit of a disappointment. Everything else in the instrument could handle an order of magnitude more neutrons, except this database.
By the way, to be fair to the database designers, they were working with Clinton era tech and were probably told that the flux rate would never be a SUSTAINED 10,000 events per second.
