studmuffin650

Citus is probably the best way to do it today as it will handle most of the work for you.

essentially giving an additional signing bonus if referred by an internal employee. Wonder if they would still offer that if you just reached out directly to the company.

I think they only lost a half million users (which wouldn't even show up as a blib on that number)

Seems like a lot of people are missing the piece as to probably why they need the money (and where they're pointing the company in the future). Future of 1Password: https://www.future.1password.com/

the only issue really left is that volume mounts don't work with podman machine as of yet. The issue has been live on github for awhile, but its finally getting traction. Likely because of the recent Docker for Desktop changes.

EDIT: github link: https://github.com/containers/podman/issues/8016

One issue still apparently is that it can’t mount volumes. Though I haven’t had to do that yet. When you attempt to mount a volume it will attempt to do it from within the virtual machine not your machine.

Just need something like this for postgres and we would jump on it. Citus is close, but all the features that are important are behind their exceptionally tall paywall.

Full Disclosure: I do not work at Uber but at another large enterprise that is at Ubers scale and is almost 100% Go across 100s of micro services.

Inside an enterprise, there’s more to a language then just the performance (though that is a large factor). You also have to take into account existing tooling (both internal and external), developer experience, whether you can find enough developers to code it and source code maintainability, as well as many other common concerns with a language. Most languages will do well in a few cases but none are best in class in all cases (or everyone would use it). Go does well enough in the performance category while also doing moderately to extremely well in other categories. In CPU bound tasks that don’t rely on CGo, go does extremely well in my experience. I think in general though, for most enterprises, Go strikes a happy medium and makes the right trade offs that most developers are willing to make.

Part of the issues with Kubernetes is that it started as a Java project and then it became a Go project. If anyone started a large Go project with that mindset it would look messy no matter what you did.

I would argue that Kinesis is not the way to go for quick POC unless you're tied to the JVM.

Pulsar is still niche in most enterprise.

Kafka is not dead, there are many enterprises (including 2 successful ones I've worked at in the past 5 years) that have built POCs and successful products on Kafka. Its supports all language performantly and has tons of community support. I would argue there is nothing better to build a POC on.

I think most of these are settings that can be changed in the advanced settings menu. Zoom changed the defaults, but you can still change the settings to what you prefer them to be

Jim Keller strikes again. I swear every place this guy goes, groundbreaking chip architecture work is done.