I just turn off trackpads, I'm not interested in that kind of input device, and any space dedicated to one is wasted to me. I use nibs exclusively (which essentially restricts me to Thinkpads).
My arms rest on the body, the last thing I want is for it to be a material that leeches heat out of my body or that is likely to react with my hands' sweat and oils.
There's a lot of editorializing going on. Now that the title has been restored, hopefully things calm down a bit.
Ultimately, Tesla has two problems going on here:
1. Their crash rate is 2x that of Waymo.
2. They redact a lot of key information, which complicates safety assessments of their fleet.
The redactions actually hurt Tesla, because the nature of each road incident really matters: EVERY traffic incident must be reported, regardless of fault (even if it's a speeding car from the other direction that hits another vehicle which then hits the robotaxi - yes, that's actually in one of the Waymo NHTSA incident reports). When Tesla redacts the way they've been doing, it makes it very difficult to do studies like https://www.tandfonline.com/doi/full/10.1080/15389588.2025.2... which show how much safer Waymo vehicles are compared to humans WHEN IT COMES TO ACTUAL DAMAGE DONE.
We can't get that quality of info from Tesla due to their redaction practices. All we can reliably glean is that Tesla vehicles are involved in 2x the incidents per mile compared to Waymo. https://ilovetesla.com/teslas-robotaxi-dilemma-navigating-cr...
The redactions also indicate they are hiding something and deprioritize safety below (whatever they are hiding). That is, it makes Tesla not trustworthy with something that risks life and limb.
If you only count robotaxis and not all Tesla, isn't the crash rate 20X per driven mile? I remember doing the math a few months ago and finding 20, but I might be mistaken.
America is, and always has been, an isolationist nation - behaving like an island nation even though it's not an island (although it might as well be, given it has only two neighbors of little consequence).
It was dragged into the first world war (despite strong public aversion) because J.P. Morgan Jr started lending money to Britain and France to buy American steel, thus setting in motion a cycle of investment and production protection that eventually required boots on the ground.
It was dragged into the second world war by Japan's attack on Pearl Harbor (and Germany's subsequent declaration of war, as it was obligated to do under its treaty with Japan).
It protected Europe and SE Asia in the post-war years in order to contain communism, which it feared more than anything else. Once that threat subsided, there wasn't much reason for it to continue with its overseas footprint other than inertia and protecting important trade routes.
Gulf Wars I was to protect oil prices (and because they already had the equipment for war), and Gulf Wars II was to be seen to be doing something about 9/11.
Now that Trump is in power, America is performing its "great reset" (which was going to come eventually), where it becomes isolationist again, sticking to the Americas (reinvigorating the Monroe Doctrine), and leaving everyone else to their own devices.
For the 80% of use cases, you have homogeneous build commands that are the same across projects (such as a makefile with build, clean, test, etc). This calls the real (complex) build system underneath to actually perform the action. You shouldn't need to type more than 15 keys to make it do common things (and you CERTAINLY shouldn't need to use ANY command line switches).
Then for the other 20% of (complex) use cases, you call the underlying build system directly, and have a document describing how the build system works and how to set up the dev environment (preferably with "make dev-env"). Maybe for self-bootstrapping systems like rust or go this isn't such a big deal, but for C/C++ or Python or node or Java or Mono it quickly becomes too bespoke and fiddly.
Then you include tests for those makefile level commands to make sure they actually work.
There's nothing worse than having to figure out (or remember) the magical incantation necessary to build/run some project among the 500 repos in 15 languages at a company, waiting for the repo owner to get back to you on why "./gradlew compileAndRun" and "/.gradlew buildAndRun" and "./gradlew devbuild" don't work - only to have them say "Oh, you just use ./gradlew -Pjava.version=11 -Dconfig.file=config/dev-use-this-one-instead.conf -Dskipdeploy buildAndDeploy - oh and make sure ImageMagick and Pandoc are installed. They're only used by the reports generator, but buildAndDeploy will error out without them". Wastes a ton of time.
Yes. In the example of gradle I setup all specifics to the well know lifecycle tasks: check, assemble and in some cases publish.
Some projects are more complicated specifically when you can really use the rule of: 1 project one assembly. See android with apk vs bundle.
Here you may need more specific tasks. But I try to bind CI (be it Jenkins or GitHub actions) to only know the basic interface.
But I meant specifically the believe that build systems and tooling around is too complicated and unnecessary.
Ah yes. Unfortunately the complexity is necessary in modern codebases. There are usually ways to simplify, but only to a point - after that all you're doing is smearing the complexity around rather than containing it.
These online storage services like iCloud and Google Drive are, and always have been, a trap.
They feel convenient, but they will keep changing their TOS to disadvantage you further and further as time goes on.
Everything you upload is scanned into their AI to create a profile about you that they can then exploit (once again, to your disadvantage). They do it despite regulations against it (Who's to say what they're complying with, deep in their complex data centers? Who's gonna even check? And how?) This is why online services that take control of your data are such gold mines (subscription fees, analytics, profiling, etc). They get you coming and going.
And of course, the account terminations: The earthquakes and "natural disasters" of the online world that destroy lives with no consequence or care.
When your data is not in your sole possession, you own nothing.
> Assuming both parties can come up with unbiased random numbers
When you're in competition, this cannot be assumed. You'll each bias the numbers you come up with towards your preferred outcome. Even with A + B mod N, you can still bias the results when you know what your opponent is trying for.
A fairer approach would be to make a long series of randomized values. Your opponent secretly chooses a starting offset, and you pick an offset to add.
> Silent failures like these are least likely to be reported to Apple.
They might be, but unfortunately Apple's MetricKit reporting system is extremely primitive when it comes to crashes. It can't even handle C++ exceptions, and important information like thread/queue names, CPU registers, stack area and app state are strangely absent.
The ridiculously bad crash reporting on Apple products is why I wrote KSCrash.
Property is the only way that we can build complex things.
We couldn't have airplanes if property didn't exist. Anyone could just walk away with parts off the airplane if they felt like it. And in fact that's exactly what happens if you leave an airplane unprotected for too long.
Hydroelectric dams would be impossible. You couldn't even have light bulbs or computers because their production methods require so much coordinated effort as well as protection from theft and damage.
Without property, all you'd have are bands of foragers because without the ability to control access, any group efforts could be undone overnight by anyone.
I wasn't talking about about stuff you can walk off with, nor was the article author, nor was Proudhon in 1840. This is about the difference between owning things made my people versus owning people who make things.
Used to be that the people themselves were property, then it was the machines they used, now it's some abstraction related to shares and companies, but it's all the same: what you're doing belongs to me not because I bought it from you but because of something to do with my position in society as it relates to yours.
> Property is the only way that we can build complex things.
This assertion needs to be substantiated, even if it is true. You give an example of how property "allows us to build complex things", but you don't prove that it's impossible for any other system of ownership or of mediating access to resources/"things" to allow that.
> but you don't prove that it's impossible for any other system of ownership or of mediating access to resources/"things" to allow that.
You can’t prove a negative, so the onus is actually on you to show an example of a working alternative that does not rely on property.
And it has been tried in the 20th century. Several times, in fact. Despite all the industrial espionage committed by the Soviet Union (which saved them the resources to do the research themselves) and the slave labor of people who spoke or wrote about the “wrong” ideas (which surplus was given to the rest of the population), ordinary people in the USSR had much worse lives than those in the West.
The Soviet Union won the space race, but I'm not sure if they had property or not. They were a dictatorship, anyway, so we probably don't want to repeat that.
Yes, it did[1]! Because they rather quickly discovered that you can’t build complex things without it. Which brings us back round to the original point!
[1] But… they did make a go of it without property before discovering that it wouldn’t work. It turns out (shockingly!) that indentured serfs (who make the food) like the idea of land reform when it means they own the land. But they don’t like it so much when it means nobody owns the land. And when they are not happy then you have no food. And then those quotes about “x meals until y” start to have some salience. And then you start to think about the most effective way to use the number of bullets you have on hand (which is smaller than the number of mouths you need to feed).
Fine. It's the only way we know of that unlocks the potential of building complex things. If you know of an alternative that is better, please tell us!
Please look up the difference between private property and personal property. When people decry "property is theft", they're not talking about personal property, they're talking about private property.
Also, socialist states with advanced economies built airplanes, hydroelectric dams and all kinds of complex things. This is a joke of an argument. Say what you will about the living conditions, fairness, corruption or other issues with socialist states, but to pretend they "didn't build complex things" is ridiculous when you look up the number of scientific achievements made first by the USSR.
reply