130 karma · joined October 2, 2016
We have lot of open roles in engineering. We're fully remoo. We have people in 17 countries right now. I'm personally hiring SRE in APAC (we need coverage in those timezones) and Infosec.
Check us out: https://redpanda.com
Jobs page: https://redpanda.com/careers/
I think the article paints a picture of the rise of hate groups and the appropriation of a commomly used and innocuous hand gesture. Hell, as a diver, I now have to think about the fact that some Bad Actors have taken what I use to indicate that I'm fine and turned it into "I support genocide."
What he did was make a statement. He made it clear to the Chef _company_ that he can not,non good conscience, contribute code to organizations that he feels are working with extremely bad actors. This is his way of protesting. Chef is able to (and in fact already has) ignored him and restored a copy of his code and formed it under a new name. (Citation needed but I believe that was a statement from Seth I'm Twitter.)
To everyone snubbing Seth for doing this, let's go "Nazi" with it. If Chef did a deal with the Aryan Nation and FOSS contributors pulled their core and support, would people feel the same? Probably not, right? Well, to many, what ICE is doing is _literally_ along the lines of what the Nazi party did. (I'm not asking that anyone agree with that sentiment, just that they acknowledge that it exists.)
So, Seth exercised his right to free speech and right to protest by publicly pulling support for an organization that he has helped significantly. This is a loss for the Chef org and the Chef community. It has also been quite effective because this isn't the first place where I've seen this conversation and it won't be the last, in the next few days.
The batch of phones going out in 19 days is not a finished product. It's expected to be loose fitting, not have endcaps on the switches, not have properly functioning power management and updates have to be done using a terminal. That's beta hardware, at best.
The next few iterations are improvements on the beta hardware but still not yet a finished product until Evergreen. That speculatively Q2 2020 but they've been off by miles with all the previous delivery dates so I won't hold my breath. Until that hardware comes out, which is what a consumer grade product should be, the only hardware delivered will be various levels of beta/release candidate.
By then, you might as well wait a few months for the hardware refresh. I appreciate the goal and the work done and if the hardware was polished and all the pain points were software, I'd be singing a different tune. Software can be fixed after the fact but poor fit and finish on hardware is forever. (And I've been Linux-as-a-desktop since the latter half of the 90s, so I can take a lot of pain. I'm all in on a Linux phone but I'll go buy a dumb phone while I wait for v2.)
Perhaps it's just me but I haven't found an xorg problem in my life that's fixed in wayland but I've had a few problems in wayland that don't exist in xorg. My display needs are rudimentary though, so perhaps I'm not the target audience.
Putting wayland aside... is exactly what I've done. I don't need wayland, so I don't use it. With systemd, not only do many of us have problems but we don't really have a choice. I could run my world on Slackware but then I'd be a SPOF (much like systemd) and that's a bad way to build architecture.
Two of the three components in your list that are mearly mandatory came from the same engineer. Why we do we keep accepting his code?
FWIW, the desktop world is less important and I run Linux as a desktop. The nightmares I get from systemd are all about my servers. If we could have left servers alone, people like me wouldn't even have cared. As it is, I have to get out the kid gloves when I'm dealing with my service platform because Bad Decisions are now system standard.
Doesn't that just feel terrible? I bought noise cancelling headphones because of the open office concept. When that wasn't sufficient, I moved and am now remote. When Slack came in, I used the IRC bridge and setup ignore rules for all the botspam. Now that's gone and I found a web plugin that would do it. Slack changed their code and that no longer works. Every effort seems to be going toward a more disruptive world. 15 minute chunks are no sufficient to do quality work, in my opinion.
We shouldn't spend our days screwing around and our nights on work. If I have to work nights to be productive, I shouldn't have to show up during the day. Even if I didn't have a kid, I'd have a personal life.
Synchronous chat is spam and we need to be better about understanding the productivity hit that cokes with always-on comms where we expect instant response.
Password expirations are insufficient and it has always been a game of cat-and-mouse with people who hate them. Good security is something people willingly use or don't know they're using, so they don't try and work around it.
You're right, we can't restart this service. These people are dead. They were shot. To death. We can never solve their problem but if we don't learn from it and try _something_ then we can't avoid the same thing from happening again. And again. And again. And again. (Repeat a few hundred times.)
But don't let me stop you. Solve for allthethings and let us know when you're done. In the meantime, a bunch of us are going to fight to solve for this current problem.
Show a link between games and hate crime fueled mass shooting by sad white boys and we can put it on the list of things to worry about. Until then, perhaps making it harder to get guns could help...
When we've solved for the current problem, we can address the next worst thing. We won't know what that is until it happens.
We could also solve for knife and sword attacks because there was that one time in Japan where someone murdered a bunch of kids or chainsaws because of that other one time that guy had a chainsaw but we do more by staying focused.
More important, as it's not a factor in the current incident, it's irrelevant.