any opinions on the german WW2 engineer laying neutral tracks toward Auschwitz
EDIT: sorry, that was glib. However I want to make the argument that the argument of doing "neutral" physical work is not absolutely morally absolving.
Yes. It's not, and I agree. There's no bright line that says you're morally culpable or you are not morally culpable for what you do. But all of us should think about our roles in that light. If Palantir uses Git, does that mean new Git contributions are part of what is arguably an ethnic cleansing? I wouldn't be able to sleep at night and work on this project. (I do not work at Palantir).
But the point is also that maybe we should take one step back and think about the morality of the people we put in decision making roles. The technology is morally neutral, but the intention is not. And helping to realize that intention is not. And sometimes the things we build can be used in horrible ways unless we also think about safeguarding their use.
This is just the tip of the iceberg. It is my very real fear that a lot of information has been aggregated into Palantir and other applications and is usable with no restraint. And that even if you just run the build system, across hundreds of apps, you might be culpable as well.
Well that's clearly an example of putting the cart before the horse. You should be able to sleep at night so long as you remember that Git isn't what enables Palantir to power an army of federalized brownshirts; it's the people making the tools explicitly for an army of federalized brownshirts with Git that are morally culpable.
Okay, that's where you draw the line. But someone provides power to their data center and their offices. Someone provides hand-held devices. Someone provides network connectivity. Someone has a contract to house and feed these agents. Someone has the logistical and fleet services for their vehicles. Someone is likely the landlord to their buildings. Someone has a contract to clean the buildings. Someone is a deciding to buy a block of Palantir stock versus some other software company. Someone runs the private prison into which people are herded. An attorney has a choice to file a charge or not file a charge. A judge has the choice to bend over backward to give ICE/CBP the benefit of the doubt, or be skeptical.
Baking a roll of bread is not immoral. Baking bread as part of a contract to feed the gestapo, is.
There are people who would not sleep at night knowing that the tool they created was enabling such things. I believe some are looking to make "semi-open" source licenses that add more restrictions.
uv can install a version of python of your choosing in addition to pulling the specific versions of libraries specified in your lockfile. it's extremely dummy-resistant.
Right, but that means the end user has to have (or install) uv, and then you ship them all your code, and then they can use uv to run that. That's a development workflow - and exactly what I meant when I said that uv didn't solve distribution in the way a language like Go or Rust does by producing a single binary.
I'll be honest, after seeing a nightmare situation where a smartring battery inflated and cut off circulation to a finger, I will never ever buy a ring with a battery in it.
I’d be interested to see a battery-less ring that uses the mechanical energy of the press to power a BLE transmitter to trigger voice input on a watch. I feel like it’s much safer, plus it has no fixed lifespan.
It's a single press, which has to power the microphone for several seconds, and wireless connection to communicate with the sync device, even later if it isn't immediately available. In what way would piezo generate that much energy?
I see. However that misses the point of always having the function at hand, 24/7/365. There will be the off time when you remove the watch to charge it for instance, or times when it may be inconvenient to wear a watch.
Your use case would be another product, likely with a different audience.
git bisect gets interesting when API signatures change over a history - when this does happen, I find myself writing version-checking facades to invoke the "same" code in whatever way is legal
Yes. poetry & pyenv was already a big improvement, but now uv wraps everything up, and additionally makes "temporary environments" possible (eg. `uv run --with notebook jupyter-notebook` to run a notebook with my project dependencies)
reply