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.
The reasons why we chose the current path were explained in detail in the blog posts.
Touchpad gestures was the most popular feature to implement. In order to do that we needed a good reason why all the other project maintainers would want to spend time discussing a feature with us. Wayland is the future, yes, but currently a lot of users are still on X which makes our argument much less convincing. Now we can say that touchpad gestures will soon be available everywhere and get their attention this way.
I agree that X is legacy platform. Unfortunately it may still be used for quite some time. Core functionality such as screenshots and input record/replay is not universally available on Wayland. So X will still be used for significant amount of time.
Please tell me what else I could explain to increase the transparency of the project and I'll try my best to do so. Thanks!
> Core functionality such as screenshots and input record/replay is not universally available on Wayland. So X will still be used for significant amount of time.
This is exactly my case. For me it's the difference between earning money or not working: I do some screen sharing with my customers every day. Wayland is not an option for me yet.
Did you actually talk to other project maintainers and get feedback that they would only be interested if it were also available for X before starting down this path?
I haven't asked this question unfortunately. Adding touchpad gestures needs changes in every GUI toolkit library except GTK and every application we would like to support. So I trusted my own experience of seeing the amount of effort needed to contribute an improvement for niche use cases. To make matters worse, an initial OK from a maintainer often does not really mean a lot. What matters is the actual time commitment to discuss design and review patches. Issues that increase the amount of effort needed for long-term maintenance and end-user support tend to decrease maintainer engagement a lot. Wayland-only touchpad gestures splits the user-base long term and thus fits this criteria very well.
At this moment I'm not really sure if I would go the same path had I knew all the information I know now. Having said that, we've only spent around a single man-month of effort working on this. In the grand scheme of things this detour is tiny.
(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.
> I find it unfair that I'm expected to work longer hours for the same compensation/work profile.
When you say "longer hours" do you mean "longer hours than I worked before COVID" or "the same amount of hours, but longer than parents will be working during COVID"?
If you mean the former, then you need a better employer, because agreed, you should not be required or expected to increase your work hours due to COVID, for any reason, and certainly not to pick up the slack caused by parents losing productivity.
If you mean the latter, then this just sounds like entitled whining. Your life has not changed because parents get more flexibility. It's exactly the same as it was before.
Parents don't get to stop taking care of their kids. I know quite a few working parents, and I guarantee you that they don't want to take time away from work for child care right now. But they have no choice. You are incredibly lucky that you aren't a parent right now; take that blessing as your "subsidy" and stop complaining about things that don't actually affect you.
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.
> When you say "longer hours" do you mean "longer hours than I worked before COVID" or "the same amount of hours, but longer than parents will be working during COVID"?
Reading these threads, I think the conversation has blurred COVID and non-COVID times. COVID has highlighted how much leeway parents get in general, regardless of whether people think they should/should not get it.
Come on. This whole thread was kicked off by a single person complaining how they might possibly have to help otherwise high performing colleagues out by covering for them some during an unprecedented pandemic. I can’t recall a single time in my time in HN (since it started, literally) I asked or thought this was a more appropriate thing to say.
children are an a-priori good for society and they massively subsidized the childless in the long run. Anyhow, try the empathy thing out. Put yourself in the shoes of a hard working parent that up to this point, possible for 10+ years of child-rearing carries the same load as everyone else. Now, COVID has happened an unprecedented pandemic since the Spanish Flu. Maybe they have their hands a little full right now? Employers in general should be helping everyone out right now, not just parents, but I am sure you can see where I am going here? Some people are stuck in a 100% capacity spot for whatever reason. It’s not what I would prefer, but it’s how society is set up.
> they massively subsidised the childless in the long run
How, exactly? It feels like the glass-makers fallacy every time this point is expanded on.
> Anyhow, try the empathy thing out
empathy means "the ability to understand and share the feelings of another"; you assume this isn't the case because others draw a different conclusion to you own. What If others understand perfectly well? From my perspective the phrasing "try the empathy thing out" is pretty patronising, leading me to conclude you either lack empathy on that point, or else wanted it to be that way; it's possible to be (if not act) empathetic while acting vindictive.
>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.
Tell that to all the children born into poverty with parents who don't want them/are indifferent to them, and to the communities they inhabit who bear the fallout.
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)
Thanks. I just wanted to know what the author meant; it wasn't obvious that I needed to Google the quote to figure out the meaning. I certainly hope that I wasn't adding any FUD to the discussion.
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?
There could surely have been faster responses (testing, movement restrictions...)
But hospitals? They are by definition too late when people die from lack of Hospital capacity. Doesn’t hurt to have some margin, but from what I have heard it doesn’t sound like NY has run out of capacity just yet.
A quite worrying turn that rate of cases is ramping up so quickly in US. Don't know what else to say. And there isn't really that much you can do as an individual, if the other people are not taking it that seriously. Just yesterday I saw a child with his parent cough with a rattling sound in a supermarket without covering his mouth. It is these types of small actions of neglectedness that compound, making this virus so hard to stop from spreading.
Hopefully you at least build antibodies when you get sick. Otherwise this will never stop spreading until we get a working vaccine.
Note that the number for the current day isn't yet necessarily complete. For example, as of this writing, Washington and Illinois were not yet in the table [1].
Washington numbers get released at 3pm PST [1] and Illinois numbers don't specifiy an update time [2]. It looks like the number should end up around 8.5k today, so better than yesterday's 14k.
Of course, with all the back-and-forth on test availability, comparing numbers day-to-day is challenging, since more testing is likely to reveal a higher absolute number of cases.
You should not worry about the current low approval ratings.
I'm sure it will easily go >50% once people see results coming - like field hospitals, hydroxychloroquine available to treat patients, etc.
Even below 50%, everyone seems to comply and follow up on the lockdown at the moment. I don't know about the precise situation in Europe, but I've been told France had to go to martial law because people were not complying with the voluntary lockdown.
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.