The AI can also only ever predict that you might die. So how should these predictions be weighed? Say there's a group of five children - the car predicts a 90% chance of death for them, vs. 50% for you if the car avoids them. According to your comments, it seems like you'd want the car to choose to hit the children, right?
What is the lowest likelihood of your own death you'd find acceptable in this situation?
> No. There is NO demand for transit from people living in the city. None. The demand is from _companies_ that force people to work in/near dense city cores.
Am I missing an obvious joke here? Because I've lived in multiple cities with great public transit, and this quote couldn't be further from the truth - the people love their public transit options, and they keep voting to build it out further.
The cost of housing further backs this claim. The market is usually right - and amenities like a tram or great public transit lead to higher prices particularly near the stops or in a certain proximity. With extra travelers you get shops and small business that spring up that corporations like Starbucks can't as readily compete against. That further drives interest and development and you create a positive economic feedback loop.
"Die Regelung habe bereits in den Zeiten des Kalten Krieges gegolten "und hatte keine praktische Relevanz", teilte das Ministerium mit. Sie sei auch nicht sanktioniert. Im Gegensatz zur alten Fassung gilt die Genehmigungspflicht nun auch außerhalb des Spannungs- und Verteidigungsfalls."
The rule existed, but apparently they broadened the scope. In any case, even if the rule is ignored nothing happens - so the question is of course why that rule exists in the first place of course.
When there's a rule with a condition that meant the rule hasn't applied for decades, and then the condition is removed so that the rule always applies, it's no longer the same rule.
Plenty of people in Germany (on all social/political levels) still talk about climate change, and have done so without pause before, during and since Ukraine.
If you think that everything "seems to be fine after all", you're in for a very rude awakening.
Is that your perception, or do you have data to back this up?
For context, here's one source saying public concern for climate change has fallen in Germany from 42% to 34% from 2022 to 2025, in line with other European countries. [0] This was a study done by a German sustainability non-profit.
Here's another source stating that globally, news coverage about climate change has diminished by 38% from 2021 to 2025. [1]
Here's a third source stating that the share of German citizens who claim to be "very concerned" about climate change has dropped from 50% to 33% from 2019 to 2025. [2]
> Even if Trump's approach is worse than Biden's, which I'm not sure of, that still does not mean it is bad for the country.
But the discussion isn't about whether it's bad, but whether it's in the countries best interest. If you switch to a less effective & more damaging policy compared to your predecessor, it's not in the countries best interest, even if it's (supposedly) better than nothing.
One scary thought however is: once automation has progressed this far and there are enough mostly autonomous humanoid and/or military robots, what power does the suddenly jobless general population have against those who own and operate them, which will mostly be rich people - and the government, which is in many places made up of other rich people?
I'm not saying this is a likely scenario. But as far as I can tell, we will objectively be mostly at their mercy. And how merciful have they been over the last few decades?
From a developer perspective you're obviously correct, but from a user perspective it doesn't make sense that the tool discards information, especially when competing tools don't do that.
Of course as a developer that makes it all the more impressive - kudos to the team for making such big progress, I can't wait to play around with all the new improvements!
Cropping IS a destructive operation. If the program isn't throwing information away, then it doesn't actually do cropping, but some different operation instead.
From a user perspective I wouldn't like it, if I were to crop something and the data would be still there afterwards. That would be a data leak waiting to happen.
I genuinely can't empathize with this objection. To me it's basically the same as arguing against Undo/Redo in a text editor because someone could come along and press Undo on my keyboard after I've deleted sensitive data.
What percentage of users sends around raw project files from which they've cropped out sensitive data to users who shouldn't see that data, vs. what percentage of users ever wants to adjust the crop after applying other filters? The latter is basically everyone, the earlier I'm guessing at most 1%?
going by your text editor analogy, we are arguing against implementing undo/redo as a "non-destructive delete", based on adding backspace control characters within the text file. I want infinitw undo/redo, but i also want that when I delete a character it is really gone, not hidden!
Sorry, but I still don't see it - the text editor analogy is stretched far too thin. If I share a project file, I want the other user to see all this stuff. If I don't want them to see all this stuff, I send them an export.
It would be a true shame if every useful feature was left out due to 1% of use cases becoming slightly different.
Which agreement are you referring to? The commonly cited 2% agreement that I'm aware of was for 2025 - which all members reached. When was Europe ever non-compliant?
It's part of the conditions for NATO membership. Oh and to have 4% as a target.
Of course they have renegotiated, and so now the target is 2% by 2027, with all historical arrears forgiven, and several countries have already publicly announced they agreed to it, won't do it (Ireland and Spain I'm aware of, I doubt they're the only ones)
You could also see this as most countries joining, promising to do this starting in 1949. Not even in the first years did most countries do this (except France). So most countries are let's generously say 1% of GDP in arrears, for 75 years now ...
> It's part of the conditions for NATO membership. Oh and to have 4% as a target.
Could you please share where the 2% were defined in the requirements since 1949, and where the 4% are currently defined?
As I already stated, the 2% requirement I'm aware of was negotiated in 2014, to be reached by the end of 2024. If this is indeed where the 2% come from, it's obviously completely ridiculous to act like the member countries didn't meet the requirements - it wasn't a requirement of the treaty they signed!
So yes, you're talking about the target of 2% by 2025. Why are you saying that the countries didn't comply with the target, when they did?
If the US wanted the 2% target to be met before then, you should have negotiated an earlier deadline. Don't agree to one deadline and then cry because an arbitrary earlier one hasn't been met.
I keep trying the "native" solutions every so often, but every time I quickly hit some snag that makes me question why I'm not just using the solution that actually works. As an example, I just generated a new project using create-vite & added two subpath imports:
The second one (#/*) is similar enough to what I usually use (@/*), and it's supported in Node since v25.4.0! Yet when I try to import the file at projectRoot/src/router/index.ts using:
import router from "#/router/index"
VS Code shows an error: "Cannot find module '#/router/index' or its corresponding type declarations."
Now, imports from e.g. "#assets/main.css" work, so I could work around this issue - but this is what I keep experiencing: the native variant usually kinda works except for the most common use case, which is made unnecessarily awkward. For a long time this is what ESM used to feel like, and IMO it still does in places (e.g. directory imports not working is a shame).
What is the lowest likelihood of your own death you'd find acceptable in this situation?
reply