AChampaign's comments

On: A list of changes to make it easier to build beautiful and walkable places

[AChampaign]

The focus on ground-level retail as opposed to multi-story retail is a bit disappointing. This Substack post from Noah Smith does a really great job explaining why density for retail is also an important part of creating walkable neighborhoods: https://www.noahpinion.blog/p/a-better-way-to-build-a-downto...

On: Cloud Run GPUs, now GA, makes running AI workloads easier for everyone

[AChampaign]

I think Lambda is more or less the AWS equivalent.

[icedchai → AChampaign]

It's not. Cloud Run can be longer running: you can have batch and services. Lambda is closer to Cloud Functions.

[ZeroCool2u → AChampaign]

I think Cloud Run Functions would be the direct equivalent to Lambda.

[hn_throwaway_99 → ZeroCool2u]

I agree, but in the GCP world, a lot of these things are merging. My understanding is that Cloud Run, Cloud Run Functions (previously known as Cloud Functions Gen2) and even App Engine Flexible all run in the same underlying cloud run infrastructure, so it's essentially just some interface differences that to me now seem more like historical legacy/backwards compatibility reasons than meaningful functionality differences (e.g. Functions can now handle multiple concurrent requests).

[yegle → hn_throwaway_99]

FWIW, App Engine Flexible is a different product that runs on GCE VM.

Other products (App Engine standard, Cloud Functions gen1, Cloud Run, Cloud Run Functions) share many underlying infrastructures.

[hn_throwaway_99 → yegle]

Oh, thanks! I guess I had it backwards - I thought App Engine standard was the one on a different infrastructure.

[AChampaign → ZeroCool2u]

Oh, you’re probably right.

[shiftyck → AChampaign]

Eh idk Cloud Run is much better suited to long running instances than Lambda. You would use Cloud Functions for those types of workloads in GCP.

[weberer → shiftyck]

For those who don't know, AWS Lambda functions have a hard limit of 15 minutes.