1,038 karma · joined August 22, 2010
Postgres generally is great -- so many great features and optimizations and more added all the time. But its query optimizer still messes up, often. It's absolutely not the engineering marvel some would have you believe.
I assume you are talking about stopping spread, which could be accurate. I further assume you are not referring to reducing illness severity, because they obviously are effective at that. But that benefit extends beyond the individual insofar as it reduces strain on the overall healthcare system -- ensuring that even those who have injuries or illnesses that have nothing to do with the disease in question receive adequate care. Therefore a vaccine mandate (or restrictions placed upon those who aren't vaccinated) can still be justified.
Wonder if they will be or have been subject to copyright complaints / lawsuits.
> but you lose a lot of money on management fees that way.
(It's just not you paying the fees at this point in time.)
I edit application code on my (relatively underpowered) laptop, and automatically mirror it to the instance where the running services picks up any changes, and recompiles and relaunches as needed. It's a fairly chunky app code-wise so moving the CPU usage off of my laptop is very helpful.
When and if the instance shuts off early, I just relaunch it and reconnect. This amounts to one click of the mouse in the GCP UI, one locally run terminal command to connect, and one remote terminal command to (re)start my app. No work lost, and the cost savings are worth the minor inconvenience. Usually the instances last the full 24 hours anyway, and I usually shut it down when I'm done working, so interruptions are very rare.
I can understand that in the context of a larger company with more resources, a dev would be put off by this. But it works very well for my uses.
This would be easy to work around, but nonetheless could lead to unexpectedly high charges if you were relying on this behavior only to have it silently change.
Hypothetically, what happens in a drought, when there is no water for anyone? Have your rights been violated? If so, by whom?
If it's rather described as a right to nondiscrimination in the distribution of clean water (with respect to some set of properties, which could include wealth or ability to pay, but likely couldn't include large-scale geographic location due to distribution logistics), then that actually starts to make sense and can be realistically debated.
The UDHR is an aspirational document that has no legal force in and of itself.
I'm most familiar with relational databases and the way in which their data is stored is generally dictated by the schema.
At a minimum, to be consistent with this patent we'd be talking about a database that accepts arbitrary groupings of predefined sets of fields, which then on-the-fly determines how best to pack these individual sets together with other sets belonging to other groupings. The fact that we are talking about two types of collections (one nested in the other) is key -- that is, the nesting of fields within the sets ("components" in ECS terminology), and the nesting of these sets within the groupings ("entities" in ECS terminology).