listennexttime

It's okay, neither does the blog author. Despite their only value-add being a PM-role, they aren't doing a good job of that either.

As evidenced by the fact that they've basically just resorted to doing tons of retrofit to bring benefits that already exist in Wayland to a legacy, deprecated, aging stack. (literally every single change listed). Also, it's no longer just about improving the touchpad (since libinput is already pushing the envelope there), and instead ... X11 Gestures? Okay? (Good luck to those brave enough to install a patched X11 from a PPA!)

I feel sorry for the people who thought there was enough substance to donate. How this project progresses with increasingly less clarity and continues to be celebrated here deeply confuses me.

Another argument that largely hinges on calling me a name; amusing considering I'm normally considered the annoying-bleeding-heart-softie. And you know, the part where I said parents deserve a break in my reply that you ignored.

Parents deserve extra flexibility.

So do single people working from their bedrooms, 50 hours a week, thinking about alternatives to this existence regularly because they have literally nothing else going on and don't have the vacation to take to get away.

So do people in relationships who are trapped in tiny, tiny SF apartments with no room to breathe in, when OH ALSO, your city is constantly filled with the noise of sirens because your police department keeps gassing your neighborhood.

Everyone deserves extra flexibility right now. Acting like your kid is some exception while calling me entitled is something else.

Nice of you and others to ignore:

>I absolutely think parents should get a break during the pandemic. I think everyone should.

I am alone. I am completely alone. Completely socially isolated. And being expected to work 50 hours a week, as always, in my home. I get no extra time off. I get no allowances for a screaming kid in the background.

I THINK PARENTS SHOULD GET A BREAK. And I think everyone should equally.

Point-of-fact, only parents are the people in this thread demanding something and acting entitled and the fact that no one can respond to the arguments without resorting to name-calling just drives that point home.

I'm a low empathy technocrat because:

(1) I chose not to have children, and

(2) I find it unfair that I'm expected to work longer hours for the same compensation/work profile.

Is that it? ... No, that's not it. Your position assumes that:

(1) Child-rearing is some a-priori, guaranteed good, and

(2) That it apparently should be subsidized by employers,

(3) and (both implicitly and explicitly, from you and others) at the expense of their non-child having coworkers.

Am I getting something wrong, or missing something?

I absolutely think parents should get a break during the pandemic. I think everyone should. The work people are doing here to act like we should worship the ground parents walk is easily the most shocking thing I've witnessed.

Honestly, it's not at all a stretch to say you basically insist parents get extra compensation (in the form of extra paid vacation). Call me whatever name you want, but people are well within their rights on this, of all places, to raise an eyebrow.

---

The other generous interpretation is that there is some base assumption that we ALL (parents and non-parents) should running ourselves at 90+% capacity. And that children are an accept caveat since parents are usually at 100% capacity. What a terrifying dismal way to look at life. I hope that's not it.

How tedious to have to constantly refute FUD when it's easy to find the answers with Google.

Anyone involved in Kubernetes, near CoreOS at the time, or really anywhere in the space at the time (instead of looking back at it with anger), knows this all to be false. CoreOS was setting direction for etcd, and understandably adding features for one of its bigger users (and in fact, some of those features are used by things of larger scale than k8s).

Kubernetes itself was started by Googlers, many of whom are still there or left to go... do Kubernetes at Red Hat (IBM) or as a startup, or at Microsoft. But to act like it was an outside project started by people who had previously quit, or are somehow unqualified to work on an orchestrator, is just an an angry untruth. Every major committer to Kubernetes besides a handful of RH folks were at Google when Kubernetes 1.0 came out. I'm happy to be corrected but I know it's hip af to hate k8s (just like two days ago https://news.ycombinator.com/item?id=23807556)

I don't know the author, or Denis, but Denis in the comments is right. This is exactly the kind of pseudo-intellectual, inflammatory contrarian opinion that I'm unsurprised to see upvoted.

This article completely conflates containers, orchestrators and schedulers in every aspect of discussion. Something will schedule and orchestrate these microVMs. Something with orchestrate secret manifestation inside those VMs. Something with operate on the host to supervise the VMs (which necessarily will have access to the guests).

So far, every microVM platform with any adoption uses Kubernetes to orchestrate. I don't know, maybe someone is running Kata on Nomad or something, but I've not heard of it. And so far, most (all?) microVM implementation utilizes namespaces and cgroups either inside/outside the VM or both. This includes Chromium's use of OCI in Crostini (their Linux-VM-on-ChromeOS).

Whatever comes along and replaces Kubernetes will push the envelope and will reduce the default blast-radius, will undoubtedly entirely rethink how authorization and namespacing work. The core would be much more minimal. And thousands of lines of generated Go would be replaced with <use your imagination>. And progress will have happened.

I get it. Hating k8s is cool. I hate it too, for a whole myriad of reasons. But it's actually frustrating how bombastic and off the mark that article manages to be. And it's too bad, if it had just stuck with "Kubernetes isn't the future, and actually understood the problems with it, it could've been a decent rant. As-is, I think it does a pretty poor job of justifying the title. (And so far, microVM workloads look to be worse for "image" security than Docker, as the tooling (outside of Nix|Guix) is somehow even worse.)

So what changed in the last few days? What is playing out is EXACTLY what epidimiologists, scientists, mathemeticians, the US intelligence agencies, and the WHO have been saying for over a month at this point. This has ALL been predicted and no one fucking cared or listened until it is BY DEFINITION TOO LATE.

I've even been saying this for weeks now, and I get challenged on it. Even though every single day we continue to just follow or beat the worst trend lines from the worst affected countries BECAUSE WE'RE NOT DOING ANY OF THE THINGS WE KNOW WORK.

What's going to be different next time? Are we going to have a global conversation about our inability to plan more than 2 days out? Our inability to grasp truly horrific facts and accept them, instead of letting fearful human brains go "That could never happen in America" (lol) even in the fact of raw statistics? Or is this just another thing I'm going to be eye-rolled at and told "it's just how it is". A global pandemic and economic slump (I'm metering my predictions here because this site doesn't seem to be able to handle realistically gloomy predictions for the future) still isn't enough to get us to ask how we got here?