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?