There is a projected "Property Graph Query" extension of SQL, and the pgSQL folks have expressed some interest in it. Not sure how it will relate to Cypher, but the feel will probably be similar.
Depending on how one views "postgres", there are at least two extensions that allegedly do it: https://age.apache.org/ and the AgensGraph from which AGE derives
Many of these companies are having to choose control and the ability to continue to make profit from their intellectual property vs they're games effectively being free in a historical archive.
Wonder if any of them would be willing to partner with a company or non-profit (such as the IA) if they offered to archive the code and artifacts for safe keeping but not automatically release it unless legally allowed to do so. Some things would probably stay under wraps for a long time, but at least it wouldn't be lost that way.
Yes, perhaps more than some other fields. However don't underestimate the number of decisions which must be made with less than adequate information and sometimes multiple outcomes can be chosen which are supported by available data. Also there are times when someone's experience can help them understand how a stream of data will change over time and they can use that to get ahead of the change rather than being purely reactive.
I'm not disagreeing with you entirely, just proposing that it isn't usually so black and white in our industry.
Original oss licences were developed in a world where software was distributed and the licenses were developed based on that model. Business models shifting largely to XaaS wasn't accounted for in the original license mindset and this is being taken advantage of the fullest extent my commercial entities (as they would be smart to do). The differences between the original oss philosophy and the realities of software in the current world seems to be causing some stress on the system as envisioned by oss advocates. Will be interesting to see how this develops.
Not sure why this needs fancy branding. This sounds like what any ops organization is supposed to be focused on. I agree that there are plenty of places out there that approach ops poorly, but to me what they outline here doesn't sound like HumanOps it just sounds like the way you are supposed to approach ops in your engineering organization. All of the big name tech places I've worked at have had this attitude. I have interviewed at some other large tech places that do not deal with ops his way and I choose not to work for a company with what I view as a "broken" approach to operations.
It needs fancy branding only because the kind of people who generally prevent these basics from happening (read: management, who don't have to feel the pain of their decisions) also tend to latch on to Manifestos and Systems and Techniques and so on...that have fancy branding.
It's packaging up common-sense humane workplace policies in a way that people lacking common-sense or humane approaches can swallow.
Another often practical approach is to change the situation in some way that allows you to solve an easier problem instead. This isn't always possible but can be more often than you might think.
I thought the way that sunspot counting works is that you point a magnifying telescope at the sun, and the image projects on the floor. You look at the image on the floor.
He did have a valid point. For the data to be consistent across a 300+ year data set, he had to use the same method as his predecessors.
However, you could use technology to augment the manual count. They could use the same k-factor adjustment they used to compare multiple human counters, and use the same k-factor adjustment when technology changes.
A dark filter of some kind ? Can be as simple as smoked glass. The ones manufactured for modern photography are called Neutral Density filters, and they're available in a variety of f-stops, but the intensity reduction is insufficient for observing the sun safely. Higher reduction filters are built for astronomy.
