I don't know, man. For the past year I've been having the "pleasure" of using Windows again for the first time in 16 years. My coworkers recommended I try the WSL since in their eyes I'm a "Linux guy". Well, the WSL crashed an hour into using it (forcing me to reboot Windows because nothing else helped) and then a couple more times that very same day. On a fresh Windows installation.
I ended up installing VMWare and using a full Linux VM. Yes, VMWare. That's how desperate I was.
Pretty cool being racist. I noticed people from varying ethnic backgrounds seemed to land in particular divisions (maybe schools in those countries focused on these cores), but I wouldn't ascribe nationality to anything as broadly as you did.
i think the main problem was that people didn't believe that pip was broken, or didn't think there was any value in a 100% correct package manager over a 97% correct package manager (e.g. misread "worse is better")
I had the problem basically understood in 2018 and I am still pissed that everybody wanted to keep taking their chances with pip just like they like to gamble with agent coders today.
Now that people know a decent package manager is possible in Python I think there is going to be no problem getting people to maintain one.
Idk how anyone could sustain the impression that pip was not broken unless they had basically never used anything else (including Linux package managers) long enough to have even a basic understanding of it.
And that's a big part of what's so frustrating about Python generally: it seems to be a language used by lots of people who've never used anything else and have an attitude like "why would I ever try anything else"?
Python has a culture where nominal values of user-friendliness, pragmatism, and simplicity often turn into plain old philistinism.
I had a breakthrough moment when someone at a workplace (software dev) said something about a thing that wasn't working on their device. Their language made it clear to me that they didn't know how to troubleshoot to figure out how to fix it. But they could write software that ran on millions of devices. Ok, that made me take a step back.
In the early 2000s I was in a rough patch in my career and wound up working at a small town web design shop that had done a lot of really amazing work, like a line of business system for car dealers, an e-commerce site for vineyards, a custom CRM for an academic department, etc. Nobody there knew about version control (not so weird in 2005) or how to write joins in SQL.
that makes zero sense to me. developing something like ruff from scratch takes a lot of things happening - someone having the idea, the time to develop it from scratch in their free time, or the money to do it as a job, and perhaps the need to find collaborators if it's too large a project for one person. but now ruff is there, there's no need to build it from scratch. if I wanted to build a python linter or formatter I would simply fork ruff and build on top of it. as others have said in this subthread, that's the whole point of open source!
> the time to develop it [not] from scratch in their free time, or the money...
How do you think the magic of open source resolves this issue? Think about this for it to make some sense
> I would simply fork
The only simple part here is pressing the "fork" button, which only gives you exactly the same code that already exists, without user awareness or distribution
you're moving the goalposts now. I never said it would be easy to get used awareness or adoption, just that it would be a lot easier to write a new linter by forking and continuing ruff development than it would doing so from scratch.
as to how the magic of open source resolves the time and money issue, it literally gives you the building blocks you need to not have to invent everything from scratch. how is that not significant?
> just that it would be a lot easier to write a new linter by forking
And I never said about the relative ease, you've moved the goalpost there yourself. $1m required to maintain is much less than $10m required to create, yet when you don't have $1m it doesn't matter - you'll still fail, and reasons are the same as the reasons you couldn't build the original.
Blocks lying around does not a building make, so you haven't addressed that magic either.
it does not take $1M to maintain a linter, these tools can and have been built and maintained by people in their spare time. astral built a better one, for which I am genuinely grateful to them, but it's not like they invented linting or that the open source community was just waiting around for some business to supply their tooling. indeed developer tools are notoriously hard to make money off simply because so many good ones have been developed as either solo or community open source projects, largely by people in their free time.
Cannot we at one point consider the tool to be "done"? I mean, what is there to constantly change and improve? Genuinely curious. It sounds like a tool that can be finished. Can it not be?
A famous case of this is https://en.wikipedia.org/wiki/Killing_of_Philando_Castile where the man identitified he had a concealed carry, the cop told him not reach for it, he started to say he wasn't, he was getting his license the officer asked for, with the officer cutting him off repeatedly and the officer shot him because he 'feared for his life'.
All they have to prove is that they fear for their life. It does not have to make sense, does not have to be 'justified', etc.
"All they have to prove is that they fear for their life. It does not have to make sense, does not have to be 'justified', etc."
That's not really true. The standard is a reasonable fear for your life. That's reasonable standard is evaluated in court by how a reasonable person would have reacted. Yes, they do give some deference to the individual who was actually there (police or civilian). The real problems happen because the DA and the courts tend to have bias when it comes to subjecting members of the system to the same process that others face.
Police officers in court cases don't have to meet that standard until it established that they do not have qualified immunity. In vastly more than 9 out of 10 cases, they do, and thus that standard is completely irrelevant.
To some degree this is how they’re trained, and imo the people doing the training also need some form of repercussions - if you haven’t before, check out some information on the courses that are (were?) taught to precincts across the country: Killology. Yes, that’s the literal name.
A black friend of mine did exactly this, asked for a permission to get a pen from his pocket. The cop laughed “sure” and the moment he put his hand inside his pocket they jumped him and arrested him.
> The panel held that at the time of the incident, there was no clearly established law holding that officers violate the Fourth or Fourteenth Amendment when they steal property seized pursuant to a warrant. For that reason, the City Officers were entitled to qualified immunity.
And handed down in only one circuit, so the other 80% of cops in the country can say "well, in my circuit there was no established case law that said stealing the property was a constitutional violation."
That's not exactly consistent with the given scenario. Use of force issues tend to have much better case law at both the federal and state levels than property related issues.
> Corbitt v. Vickers, 929 F.3d 1304 (11th Cir. 2019): Qualified immunity granted for officer who, hunting
a fugitive, ended up at the wrong house and forced six children, including two children under the age of
three, to lie on the ground at gunpoint. The officer tried to shoot the family dog, but missed and shot a
10-year-old child that was lying face down, 18 inches away from the officer. The court held that there
was no prior case where an officer accidentally shot a child laying on the ground while the officer was
aiming at a dog.
> Young v. Borders, 850 F.3d 1274 (11th Cir. 2017): Qualified immunity granted to officers who, without
a warrant, started banging on an innocent man’s door without announcing themselves in the middle of
the night. When the man opened the door holding his lawfully-owned handgun, officers opened fire,
killing. One dissenting judge wrote that if these actions are permitted, “then the Second and Fourth
Amendments are having a very bad day in this circuit.”
> Estate of Smart v. City of Wichita, 951 F.3d 1161 (10th Cir. 2020): Qualified immunity granted for
officer who heard gunshots and fired into a crowd of hundreds of people in downtown Wichita, shooting
bystanders and killing an unarmed man who was trying to flee the area. The court held that the shooting
was unconstitutional but there was no clearly established law that police officers could not “open fire on
a fleeing person they (perhaps unreasonably) believed was armed in what they believed to be an active
shooter situation.”
(And a bunch of others.)
And a matching case has to be very specific:
> Baxter v. Bracey, 751 F. App’x 869 (6th Cir. 2018): Qualified immunity granted for officers who sent a
police dog to attack a man who had already surrendered and was sitting on the ground with his hands in
the air. The court held that a prior case holding it unconstitutional to send a police dog after a person
who surrendered by laying on the ground was not sufficiently similar to this case, involving a person
who surrendered by sitting on the ground with his hands up.
The prior opinion in this case, found at Jessop v. City of Fresno , 918 F.3d 1031 (9th Cir. 2019), is hereby withdrawn. A superseding opinion will be filed concurrently with this order. Plaintiffs-Appellants’ petition for rehearing en banc remains pending.
I picked the second one to start. So I don't think that's a great source.
What was the outcome of the lawsuits against the agencies? You don't have to win a suit against an individual. Most of the big payouts have to come from the cities.
I would probably say that both the city and the cop should, independently, be liable. Given the position of authority the city provides, it is ultimately responsible to hire and properly train people who will use that authority well, while the individual is also responsible for their own actions.
If the cop is following procedure, the city and others who set the procedure should be liable. If the cop is breaking procedure, then they should be liable. If there is no clear procedure, then they should both be liable.
Sadly, yes. They're also the populace that voted for that leadership. There are many leaders of major cities that continually push policies that are highly probably to result in legal action due to their conflict with existing law and case law. I don't like it, but its true.
Some more recommendations. Keep your registration and insurance in an easily reachable place like in the passenger side visor/mirror. Keep your hands on the top of the steering wheel where the officer can see them at all times. Keep your car clean.
The goals are to make the officer comfortable and minimize the time.
I had Claude Code create an architecture overview that includes descriptions of each component of an app with all the functions, how they worked, and where to find them within the codebase. I hoped it would reduce token burn, but in testing it didn't seem to have a meaningful effect. However, I noticed that having it and explicitly telling Claude to refer to it reduced code drift and improved consistency across runs.
I've installed this and I'm gonna take it for a spin and see if I can perceive any measurable improvements. Cool project.
It's almost as though the well-known and proven method of building more housing works!
Similarly, the tested and proven solution to homelessness is providing housing up front. Don't have any requirements (employment, sobriety, etc) blocking housing. Those things are easier to achieve with a roof over your head.
I am a musician and electronic music is my primary jam. I once bought way too many plugins on Black Friday because there were so many incredible deals. The next day, I opened my preferred DAW and I was just overwhelmed with options. It caused my creativity to short-circuit. I didn't make music again for months because of the sheer sense of drowning in new tools.
Of course, every time I've ever added just one tool I've been fine. I explore it and learn it and figure out the limitations and how to make it do what I want (or decide I don't like it).
The brain is funny. It's not always possible to rationally explain our motivations and blockers in a way that feels satisfying. I'm a big believer that words help us understand feelings / reality. Not being able to articulate the things that are blocking us satisfactorily makes it harder, or possibly impossible, to work through them or try to tackle them or work around them.
And then there are the times when we can perfectly explain our feelings in a way that accurately represents the inner turmoil but it's just a crappy new reality. I think that's a lot of what people are feeling wrt coding agents.
reply