BatmanAoD
Right, but their endorsement is still likely to do more harm than good in terms of public perception of the law, I think.
Well, that's fair; first-class support for running an actual Linux kernel, with the containerization support that implies, is one of the reasons I prefer Windows with WSL as a dev environment when using Docker (at least, in companies where the IT team won't just let you run native Linux).
MacOS and docker is asking for trouble.
That's a real problem! MacOS and Docker are extremely common for development, and a scripting language like Python should just work with them, not just at the language level (which is good enough) but in the ecosystem and tooling. The latter is what Astral is trying to improve.
I understand having severe philosophical disagreements with the Rust project, with the majority of Rust users, or with the uutils project specifically. What I don't understand is this part:
If you go to the website of the Rust programming language nowadays, one of the first things you'll notice is that their primary communication platform is Discord. Yes, you read it right - their primary communication platform is Discord, a proprietary spyware program that is owned by a Chinese investment company and has backdoors to various other national intelligence agencies too.
Rust did have an official Discord, years ago, before switching to Zulip (alongside other official communal hubs, most prominently the Discourse forums that the author complains about next). But this was written in March and specifically says "nowadays", and I cannot find any mention of Discord on the Rust website.
If you drive a car, have you read the entire owner's manual for every car you've owned? If you're a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?
At some point you need your tools to be intuitive enough that you don't need to read an entire manual in order to do your work.
Oh, you just mean he believes that's the future, not that he agrees with it or thinks it's a good thing.
Do you mean the "this is where we're headed" comment? That's not agreeing with the direction.
... until you have an off day, or you get bored of coding, run off to join the circus as a professional knife-juggler and your codebase is inherited by someone of more conventional aptitude.
Sometimes you even have to deal with having mere mortals on your team!
For what it's worth, I agree with you about branches, and there are various ongoing discussions about how to make working with branches more convenient. I use an experimental feature called "advance branches" that makes it mostly fit my workflows, and the other benefits of jj are sufficient that I haven't switched back to git.
I create log files of runs, temporary helper scripts, build output, etc. in my working copy all the time.
The solution to this is to just have a more aggressive .gitignore. But also, note that the "working copy commit" isn't generally something you want to push or keep; think of it more like a combination of the git staging index and an automatic stash.
Same
"Heartbreaking: the worst person you know just made a great point"