Pxtl

I was confused why the github file browser was falling over.

Right but the travel pattern they used to determine that this person was a smuggler is "frequently drives to/from the rez", as if there's no legit reason to be doing that.

Now I'm wondering what it's like for people whose lives naturally involve "suspicious travel patterns" but aren't actually doing anything suspicious.

Like, how often do people who live on that rez get pulled over?

> the reference implementation.

The problem was he exposed too much of the implementation into the language itself, destroying its ability to be a simple reference implementation that others could re-implement.

It still blows my mind that the big "we're breaking backwards compatibility Python 3000" release didn't do anything to lay the groundwork for this, or any of Python's other structural problems.

List comprehensions? Really? I remember when they were pretty and I was learning them alongside other languages with higher order functions and Python's approach seemed to be the ugliest of its cohort. They were neither as logical as simple Lispy "take a function as a parameter" things like Ruby, nor were they the kind of clean and legible stuff we expect from Python.

The fact that they didn't solve Venv when they did the breaking change in Python 3 is absolutely bonkers.

It was the first language that actually felt ready-to-use, available for free-as-in-speech. Batteries included, robust online development community, sensible featureset, main libs that were designed bottom-up instead of top-down. I remember learning Java 1.2 or 1.4 after learning Python and it felt like a huge regression. Swing was a joke compared to TkInter (which was weak compared to proper GUI editors like VB but at least made nice scalable native-feeling GUIs and had a sensible API) and the standard collections were miserable without generics.

But Python peaked like 20 years ago. The later features were too ugly, and it was too slow to fill the obvious gaps in the language.

Honestly it took me so long to pick up containerisation because of how it's marketed. "Orchestrate a zillion fake computers, ultralight VMs, livestock not pets" big whoop.

"It's an idempotent language for OS level dependencies so you can be sure exactly what is running on your server"

Gimme gimme gimme!

I mean if they're getting sued for failing to block proxy/vpn services they're being told to be opinionated and they can't be a neutral service. "You asked us to be opinionated about traffic, so we're doing that. Do you want us to go back to being neutral?"

The web ruined everything. Using a document platform for GUIs meant that every widget was reinvented over and over again until all conventional semantics were lost.

Debian always seems to be the grown-ups. I'm a Linux novice so I couldn't get Nvidia drivers working on it but that's the only reason it's not running on my desktops.

Thank you, Wiz Khalifa.

This is why I always think emperor git wears no clothes. Hiding these kind of intermediate junk commits from history should not require rewriting and breaking the distributed history you all share. imho the correct solution would be a tag-like layer for annotating existing commits with metadata (additional signatures, hide-flags, retroactive comments, etc) or just a full 2nd dag, but whatever: git sucks at annotating history and annotating history is a core workflow in git.

Even within animal testing, the cost and convenience of animal testing could vary tremendously. Working in animal testing intrinsically means running a death-camp for mice. The mice aren't are barely even raw materials, they're basically stationery, more treated more like a mobile pH test-strip then a living creature.

There are ways that animal testing could be made far more humane (like birth control to prevent the kind of overbreeding that demands mass culling), but those, themselves, would be costly.

And in order to test cures, you must first inflict the animals with the disease. How many do you need? Are you sure? Because waiting to produce more later would also create costs. Cheaper just to breed a huge batch now and then cull the surplus.

... so how many extra do you want?