The real "deeply depressing" bit here is how many of us would rather focus on pulling down the top crab than question why we're all in this bucket to begin with.
Beyond all of the hype and drama, I'm not sure I have good information about what's going on at Twitter and if the conditions are sane or not.
Are employees being told, "sleep at the office for the next week or you're fired"?
Or are employees having the luxury of knowing that at least some layoffs are coming and have a choice to try and deliver something special to make their case? That's arguably incredibly privileged as most people never have foreknowledge about pending layoffs and don't get any last opportunity to show the value they can bring.
Which is it? Why are you now equivocating over this instead of being able to answer for your own conclusions?
Clearly you think the working conditions of Twitter aren't that bad, that was literally the thesis of your first post. Clearly you think that there exists a set of working conditions that are deeply immoral and deserving of at least complaint. That was also the thesis of your first post.
So where does that line exist? When do working conditions go from "not deserving of complaint" to "complaints are fully justified"?
Especially in a fog-of-war sort of situation with a lot of drama where it's hard to tell what claims might be real and fake, I don't know precisely what Twitter's working conditions are like. But even not knowing some nuanced details about life at TwitterHQ right now, I'm very comfortable in saying that the worst case scenario working at Twitter is miles better off than the best case scenario say down in an iron mine.
> So where does that line exist? When do working conditions go from "not deserving of complaint" to "complaints are fully justified"?
Everybody is entitled to complain and voice their opinion no matter how rich or powerful they are, but I did take a bit of issue with the "deeply depressing" language that was used.
If the tweet had said "On a human level, it's upsetting to see my coworkers stressed out over the impending layoffs" or something to that effect, I can totally empathize. But "deeply depressing" is a bad phrase for this situation.
I don't think you should feel narcissistic at all. Family is one of the prime places where we share our wisdom and values. Where we pass on the results of our mistakes in the hopes that the next generation avoids them. Don't feel bad for trying to do that, it's one of the fundamental elements of human progress.
It also implicitly discourages you from asking yourself if you should be accessing the thing you are. IMO a lot of the tight coupling in Rails codebases begins with being able to grab literally anything and use it with no one the wiser unless the read that specific line of code.
IMO this bit right here is worthy of highlighting again:
> Especially when you consider that during the build the workstation is belching hot air and screaming like an airplane about to take off while M1 is whisper-quiet with barely warm air coming from its exhaust.
I have never run a significant amount of compilation on any machine that didn't hit heat issues. So either the M1 is doing very well at managing heat, or Clang is doing incredibly poorly at exploiting the full system. In either case this makes the M1 look like something special.
"Competing" in this sense is delivering similar user experience (battery life, performance, seamless hardware interactions) that Apple is achieving through their top-to-bottom control of the hardware and software.
It's not enough to show off Intel/AMD SoCs and call that good when the other components and software force subpar UX.
As far as performance, MacOS has been slower than both Windows and Linux on the same hardware for as long as I can remember. I see no reason why both operating systems won't achieve better utilization of these upcoming systems than Apple does with their M1.
https://www.phoronix.com/scan.php?page=article&item=macos101...
The M1 operates in a unique and valuable space right now, but the claim that it will be effectively impossible for the rest of the industry to move into that space doesn't hold water.
IMO it's a bit much to decide what "the right thing" is there. Blindly assuming that someone attempting to edit credentials didn't mistype a file name isn't exactly safe and sounds like a great way to cause problems based on believing you updated something you did not in fact update.
Kinda seems like you are, mate.
There's ways I'll insist that Python is the best at [x], and ways I'll concede some other language is better at [y]. But it never amounts to anything close to a debate about what language I should use
Anyways I should know better then discuss Python
You mean like that "setup software" Comcast spent ages trying to pretend I had to install just to get things running?
I ran Linux in those days, which always meant a little extra support time but I never had to install jack.
> Chrome does not perform pin validation when the certificate chain chains up to a private trust anchor. A key result of this policy is that private trust anchors can be used to proxy (or MITM) connections, even to pinned sites.
> Late on December 24, Chrome detected and blocked an unauthorized digital certificate for the "*.google.com" domain.
https://security.googleblog.com/2013/01/enhancing-digital-ce...
Literally the only way to "mix this up" is to not read anything, ignore package managers and build from source, then somehow decide to use 'x-pack' over 'elasticsearch'.
Let's wait for the results of this case it will make it clear that if someone wants to use ELK, they should purchase a license or use Amazon version (as they will fight the case, a small startup can't have budget to even defend).
For a small development firm its better they use really open source product like Solr, Vespa or Lucene directly with OpenJDK, not the oracle JDK. Looking at this can only say Richard Stallman is a visionary and saw this when he defined Free Software and accompanying licenses.