"Switching from OpenSearch to running elastic search ourselves did require some initial setup, but we're not changing the size of the team at all in the longterm to accommodate for this switch. Because running things on premise is not a materially different scope of work from running it in the cloud. That's the whole premise behind our overall cloud exit: The team it takes to run our scale of operations in the cloud wasn't any less than what it takes to run that same scale on our own hardware."
and thats the rub... in generic enterprise land everyone has there own ES cluster multiregion to support 100GB of data and 50 rds dbs that could run one instance... what even is a DBA in today's world?
What if Microsoft buys it for there devtools business like NPM, Github, VSCode + Terraform,Consul,Vault.. all just more gateways into azure but like all the others they own allow you to use it how you want opensource.
That's one definition. It can also mean to carry someone off by force, to kidnap. "Carried away" is the root idea, but it doesn't have to be "by delight".
Because they are still deficient of vitamin D [1]:
> It is evident that, despite the location of Ecuador and the intensity of UV rays it receives throughout the year, Ecuadorian subjects have insufficient levels of vitamin D.
I wonder if it says they wear a lot of sunscreen. They’re on the equator and much of the country is at a very high elevation so the sun is particularly strong. When I was in Ecuador for a few months I went through more sunscreen than I had in my whole life up to that point. Without sunscreen I would get burnt to a crisp on an overcast day even when I didn’t spend much time outside.
The merger of these threads really takes away the scope of the announcements made and the different discussions being had. The editorializing and changing of URL really alters the environment for conversation in a way that's not healthy and hurts the scope of these things. Then the second highest comment on the thread becomes about the design layout on the page.
So be it if Microsoft/Apple/Google/Android/Amazon/Uber is on the front page multiple times...
I'm not going to claim we execute it correctly every time but the general approach seems fair to me: have a distinct thread on each distinct major story.
It's true that merging threads sometimes eliminates some context (hopefully not too much) but duplicate or near-duplicate threads on the front page are arguably worse. If there were a way of pleasing everybody we would jump at it. Unfortunately, people disagree about this.
and thats the rub... in generic enterprise land everyone has there own ES cluster multiregion to support 100GB of data and 50 rds dbs that could run one instance... what even is a DBA in today's world?