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"?

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.

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.

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.

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.

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'.

- Phone apps from the jump - Easy ability to upload files - Search includes the content of those files - Editing

Slack is way more than that, though.

My recollection is that even the initial version of Slack was more than that.

At this point, it's enough that "let's extend ircd" isn't exactly a practical answer. Either they maintain their own incompatible fork of ircd or they try to force their business desires into the irc protocol.

There's plenty of things that are "just X plus some paint" if you don't look at them deeply. That usually does an extreme disservice to the difficulty of the "plus some paint" part, and often represents a failure to understand the features involved.

Unless I find a big chunk of time today, I'm 0/4 on a resolution to write a post a month this year.

Expecting people to build content in their spare time builds in some hefty assumptions on how much spare time and energy they have.

I took a deep dive at one point into understanding concurrent transaction behavior in MySQL and its ramifications. Probably go back and reference that post about once a month...

Just set your phone on permanent DND w/ exceptions. It's literally the same thing, except you're not going through annoying contortions to "stick it to" someone that is probably a robot...

What gives me pause here is all the anecdotes in this thread about other engines getting results right. If the real answer is "PageRank has been successfully flooded by bots", then everyone would have bad results.

What I suspect, off nearly no evidence, is that Google is using ad tracking to inform a notion of search relevancy. My nearly unjustified belief is that that system is the one being flooded by bots.