Cidan

You don't really need to tmux at all for Claude Code CLI. Claude Code CLI supports streaming json input, and streaming json output; you can use stdin/out as a pipe to control Claude Code CLI.

I'm doing this today in https://github.com/Cidan/ask -- works great.

Yeah, agreed. This isn't even close to true, not sure where he got that from.

Also, the PM's are going to do an AMA for this on reddit tomorrow:

https://www.reddit.com/r/googlecloud/comments/vy8hx3/ama_wit...

Come join us! Also, hi Moles :)

Googler here.

We have very strict and very well engineered data retention systems. When we say data is deleted, we mean it. Various levels of automation ensure the data is purged, and all data is tracked meticulously for violations across every datastore.

It's one of those systems I wish we talked about more -- it's a marvel to behold just how much work goes into retention policies and the automation that drives it.

Many years ago, I worked for a contractor where we required clearance. We hired this one sysadmin "stick it to the man" type of guy that was extremely well educated and talented.

When he got to the part of the form that asked if he has ever consumed drugs, he said "yes" as he should have by being honest. The follow up question asks something along the lines of, "If yes, will you ever consume drugs again?"

The jack-ass decided to answer "I won't not do them again..." We fired him a few days later.

BigQuery on GCP does this as well, without any extra work.

(Disclaimer: I work for Google)

(I too work for Google Cloud)

I agree. One of the most amazing things about watching this project unfold is just how quickly it went from 0 to 100 with minimal overhead. It's amazing to watch companies and individuals push the boundaries of what is possible with just the push of a button.

It already is! It's available in open beta for all customers, with a GA release coming in the near future.

Disclaimer: I work for Google Cloud

Take a look at Google Cloud IAP -- it's essentially a stripped down version of BeyondCorp for public use on Google Cloud. I've used this as a customer of Google's with great success, it really does just work.

Disclaimer: I work for Google Cloud.

https://abc.xyz/investor/other/google-code-of-conduct.html

Literally the first three words.

Let's make towns have downtowns, with beautiful brick roads, scenic ponds with some ducks, perhaps a waterfall, some nice cafes, a lawn with benches, some parks, some nature, trees, live music, a library and museums.

You would think! I live in Santa Monica, California, and we have exactly that in our downtown area. The retail shop turnover is insane -- a large amount of shops come and go from the area, despite the massive amount of foot traffic the area sees every weekend (and most weekdays during the summer).

Vendor lock-in is most certainly not the only competing point we have against AWS. From BigQuery, to BigTable, to Spanner, to our private network, to our live migration of compute, to our hosted Kubernetes, the list goes on and on.

AWS does a lot of things right, and we're more than happy to go toe-to-toe with them in the areas they have us beat. Competition is a sign of a healthy economy where everyone benefits. How can you compete if you don't even try to match the people you are competing against?

Disclaimer: I work for Google Cloud.

Came here to post this -- moving our infra from AWS to GCP was the best decision I've ever made.

We've accomplished much of the same by using GKE and making artifacts out of containers. New instances scale up within a few seconds (and less than a second if we pre-pull the image).

It's pretty amazing.

Second this. We just moved our sizable infrastructure to GCP for more or less the exact same reason. GCP makes all of this a breeze -- I don't understand why other providers can't do the same.

You can already adjust the load distribution algorithm when creating the LB, so I imagine this doesn't really change anything.

I haven't done this in AWS yet, but I've been growing mounted block devices/disks Google Cloud for a while now. It's more or less just like growing a disk on a SAN.

You still have to grow the filesystem it self though, so if you're trying to grow the root mount, using a partitioned disk, and not using an abstraction like LVM you will need to reboot to be able to use the full disk.

Glad to see AWS catch up in this area.

https://www.lhup.edu/~dsimanek/neverwrk.htm

Pardon me here, but I don't understand what you mean by "the docker image most people use is unofficial."

I was under the impression that everyone used the fully featured official docker image (https://hub.docker.com/r/gitlab/gitlab-ee/). We've been using this for over a year without issues now. Is there a reason you need the unofficial version? Does it do something different?

My initial thought before reading the article was "Well, Spotify did just move off of it..."

"...8-node DC1.8XL Amazon Redshift cluster for the tests."

Well, yeah. That's 28,108.80 a month if you're running queries on demand and don't want a delay/coordination in Amazon instance creation/destruction.

BQ may or may not be as fast, but it's truly a managed service; I give it our data and it just works. I don't have to worry about instances, boot up time, maintenance, hourly costs, etc. It's silly to focus just on query speed when there's a whole layer of management and cost that comes with it.

Yep; these are very specifically crafted situations though, which is why I said most and not all.

Federal legislation can not weaken state legislation in most situations where a state legislation is stricter. A good example of this is minimum wage at the federal and state level.

If legislation at the federal level were to apply a weaker standard for who can not be covered by a non-compete clause, a state can still expand coverage to all jobs.

There's a difference between supplying the infrastructure for a service, and writing the software for a service. Just because Google was able to supply the infrastructure for Niantic, that doesn't mean their software was designed in such a way that they could handle the load.

To be clear, vendor directories are still optional to use, you just don't have to enable them by default.

We use a unirepo for all of our Go work, and being forced to use the vendor directory would be a massive headache.

We use RethinkDB for our home grown monitoring system; it's incredible. We have several hundred clients connected, inserting monitoring data and doing some pretty complex queries. In the ~2 years we've been using RethinkDB, we have never experienced a failure.

If I could go back in time, I would use RethinkDB for our actual product.

We've been in the EFS preview for quite a while now, and we are incredibly pleased with it. We do a few different things using EFS, including using it as an output for some of our Spark jobs.

It's really a top notch product; couldn't be happier.

"Solus is a Linux-based operating system built from scratch for the modern desktop and targeting the x86_64 architecture."

In the linked page.

I wouldn't worry too much about what the community thinks. TSDB fits the bill and works great. That being said, I've also heard wonderful things about druid.io (http://druid.io/), however I've yet to personally try it. We're going to start testing and throwing data at druid early next year though.

What sort of work are you referring to when you say it's a lot to keep up?

We've been using OpenTSDB here in an extremely high traffic setup for about a year now, with absolutely no issues at all. It took a few hours at most to setup and figure out scaling.