chaps

It's more that the default is to overuse tools that cast too-wide nets like pgrep and pkill. And it doesn't know how to use the output well enough. Like, when these systems do ps, it identifies random processes in the list instead of identifying the most recent process that it, itself, started.

It's as if some SRE-type person decided to hard code pgrep and pkill because it's their personal preference.

You're right that things are significantly worse now, but it's important to recognize that what came before was still bad and in many ways is the foundation for where we are.

https://slate.com/business/2013/11/double-down-obama-said-he...

These aren't challenging things to do for an experienced human at all. But it's such a huge pain point for these models! It's hard for me to wrap my head around how these models can write surprisingly excellent code but fail down in these sorts of relatively simple troubleshooting paths.

Wish someone would wipe my memories of that game so I can play it again.

And there's a lot of truth to that which a lot of people need to reconcile with.

The fact that we don't have DACA solidified into a path towards citizenship by now is just sad.

About ten years ago I took a three day cross-country Amtrak trip where I wanted to work on some data analysis that used mysql for its backend. It was a great venue for that sort of work because the lack of train-internet was wonderful to keep me focused. The data I was working with was about 20GB of parking ticket data. The data took a while to process over SQL which gave me the chance to check out the world unfolding outside of the train.

At some point, mysql (well, mariadb) got into a weird state after an unclean shutdown that put itself into recovery mode where upon startup it had to do some disk-intensive cleanup. Thing is -- systemd has a default setting (that's not readily documented, nor sufficiently described in its logs when the behavior happens) that halts the service startup after 30 seconds to try again. On loop.

My troubleshooting attempts were unsuccessful. And since I deleted the original csv files to save disk space, I wasn't able to even poke at the CSV files through python or whatnot.

So instead of doing the analysis I wanted to do on the train, I had to wait until I got to the end of the line to fix it. Sure enough, it was some default 30s timeout that's not explicitly mentioned nor commented out like many services do.

So, saying that things are "much better in every way" really falls on deaf ears and is reminiscent of the systemd devs' dismissive/arrogant behavior that many folk are frustrated about.

You're making a lot of assumptions about how people use their computers, their understanding of their own devices, and the banality of building argumentation around what someone should have done or should not have done in the face of how reality works.

I realize it's not a court order, but just want to add to the stack that there are examples of them being requested to provide something within the public's interest in a legal context (a FOIA lawsuit) where their counsel pushed back by saying no.

But, friend, with love -- shit talking about what people are doing or not doing is not the answer. Lead by example.

Most of the datasets I work with are indeed <10GB but the ones that are much larger follow the same ETL and analysis flows. It helps that I've built a lot of tooling to help with types and memory-efficient inserts. Having to rewrite pipelines because of "that one dataframe API" is exactly what solidified my thoughts around SQL over everything else. So much of my life time has been lost trying to get dataframe and non-dataframe libraries to work together.

Thing about SQL is that it can be taken just about anywhere, so the time spent improving your SQL skills is almost always well worth it. R and pandas much less so.

It.. is not. I suspect that you have some fundamental misunderstandings of firearm safety and I would not feel safe at a range with someone who thinks this way.

Am I right to say that your argument can be summarized as, "She didn't deserve it, but her actions were deserving of it"? Or maybe "merited"?

I'm genuinely confused by what you mean by "deserves".

(just to be explicit, the disagreement we have here is very much about what the word "deserves" means rather than anything productive)

My mom's dad was shot and killed by police. Absolutely nobody in my family knows anything about it, but the default is "he was a bad person and deserved it" or, "he probably did something wrong." The coroner's report shows his death as a suicide, despite police shooting and killing him. This was a time before cameraphones and before I was even born, so it's impossible for me, let alone anyone else to know what happened.

A lot of how you approach this discussion reminds me of the side of my family that defaults to thinking that the police did nothing wrong, or that their actions were justified or within policy, even without knowing the full facts (or, any; it's willful ignorance out the wazoo), plus a handful of assumptions. And, just -- a person died and that's all you can muster? Callousness and an air of benevolence?

You can do better, friend.