Super cool, excited to see innovation here

super interesting

Larry da big OG

i view the marketing as showing they care about product and users here

I don't. If they did, they'd recognize the fact that the entire concept of "Apps", collaboration, etc..., are examples of ways human beings assemble tools to interact.

Terminals are one of the most direct ways to interact with hardware. If you need to share your hardware with someone else, then you share your screen or a recording. If you need to share your environment or she'll settings, you share scripts.

There's nothing to terminal use to be gained by trying to shoehorn in more net connections, and more uncertainty by merging in more sources of input. By cramming that in you are doing the opposite of caring about users. You're introducing extra elements that can break, decreasing the overall learnability of the system.

Yeah, I mean maybe I'm overreacting -- I'm all for a better terminal, and there's some genuinely cool stuff here -- it's just undermining its own case by overselling IMO.

> Yeah, I mean maybe I'm overreacting

No, you're reaction is perfectly reasonable for such nonsensical hyperbole.

unbundle or die trying

democratize access to webhooks -- love dat energy

Rob and team have been working hard to ensure m3db is a long term winner. love to see it.

For those of use who love trying before buying, would love to better understand the moving parts and their responsibility --- querying engine, coordinator, and datastore (etc) --- and how they evolve as your scale the systems.

Hey jaren hope things are well at Robinhood. Good question, there's a diagram on what a default deployment looks like alongside the M3 v1.0 announcement https://medium.com/chronosphere/m3-v1-0-released-a-productio... and in depth documentation on the website https://m3db.io/docs/overview/.

Storage, aggregation and compute are all separate and scale up/down independently. The coordinator and query services are both stateless and you just add more instances, DB nodes do not do compression/decompression for instance all this happens as part of computation on the query service.

M3DB for storage has a k8s operator that can manage clusters (expansion, etc), and the M3 aggregator can be deployed as a stateful set in k8s and also can be independently expanded.

I am on the west coast and my parents are in south.

When the pandemic hit, braid made it really seamless to ensure she had last minute spending money for the expensive and unexpected trips to the doctor, groceries, and gas station.

Momma dukes loves the in app chat too.

I see a lot of centOS and RHEL in big corporation production these days... always felt like most open source issues are solve in the debian world first ... in my experience at least -- didn't know if that was something big corp did but maybe smaller didnt' ... just thinking out loud