ttymck

St Brendan's Isle

Looks really pragmatic and I'd be glad to see this succeed.

Is anyone able to credibly comment on the likelihood that these make it into the standard, and what the timeline might look like?

> See where I’m going with this?

No. Could you elaborate?

It's 22 years ago, roughly

And what's the typical variance (from "actual") for a "usual" reading?

> Kotlin is really cool and arguably better than Java. But the language is very hard to read ('easy' to write)

I had the same immediate reaction. This style of code is something the Scala community used to be in love with, and was criticized for it. The community has largely moved away from this style, so it's interesting to see history possibly repeating itself with Kotlin.

Surely you can't be serious. Say, in this fantasy world, my car appreciates $3k. Can Fred still pay $18k before I have a chance to re-assess?

"allow anyone else to buy any of those assets for the declared value"

How would this work?

Sure. Looking at the output would make clear which properties are actually recognized, and it could be commited to version control to avoid confusion

Right, I am suggesting a feature to disable the idleness check during a window of the day

Scale to zero makes me think it might be useful to specify a time window (cron?) where scaling to zero is allowed, i.e. 6pm-8am it can scale to zero but during the work day never fully scale to zero. Makes me wonder if this is a common pattern.

Perhaps a tool that processes a k8s manifest and produces a modified manifest containing only the attributes that are supported?

The next logical question is how they define smoker, and how they enforce it.

Does this imply there's a massive opportunity for Japan to encourage learning English to attract business, or are the economics not aligned?

Ocean's Eleven

Interstellar

> passing laws.

As if that's any less of a complicated technical solution.

Got it so to own up to it that have to change the culture... Overnight?

I'm not sure what your definition of "own up to it" is, but they issued an apology day-of.

> but so far not much in the way of lawsuits

It hasn't been that long? The situation might be that there hasn't been sufficient time to yet gather evidence to commence lawsuits.

99% of users don't need kubernetes. Just deploy to heroku, and you'll have a much better developer experience.

Sure, an operator is likely to use a wide array of APIs.

But, to reiterate, everything uses APIs. The *betavX APIs are of course likely to be deprecated and replaced with stable APIs after a few versions.

That's great. I guess I've somehow been making things harder than they need to be.

Any cluster extension. Helm is a good example.

https://helm.sh/docs/topics/version_skew/

Istio: https://istio.io/latest/docs/releases/supported-releases/#su...

Literally every kubernetes manifest that hits the server uses a k8s api:

    apiVersion: apps/v1

It doesn't do everything for you. You still need to update applications that use deprecated APIs.

This sort of "just" thinking is a great way for teams to drown in ops toil.

You'd have to define "stupid".

Isn't it also possible that this sequence of decisions is "game theory optimal"?

I don't think everyone subscribes to sentiocentrism

It looks pretty similar to what's available in Google search console. What's the advantage of this dashboard?

And it seems to confirm, although not completely explicit, that there was _not_ a canary facility in place.

Thank you! I'm surprised this didn't get more coverage in my social media sphere. I'm still seeing memes and jokes.