Did you just strawman a fact with an anecdote and then completely get your second statement backwards?
Nuclear plants have to scale down their water output for ecological regulation reasons. Which means they have to restrict their inflow, which means they have to restrict their output capacity.
Oil industry wants you to think that nuclear there doesn't work, not that it does. Oil and coal have been working against nuclear for an entire generation or more.
The nuclear capacity losses are because of environmental regulations, not because of inherent issues with nuclear.
Regulations restrict discharge of cooled water above 30°C into waterways, and they are responsible for the riverway temperature downstream of them. Since the waterways are warmer during a heat wave and the nuclear plant is responsible for the temperature of that waterway, they cannot discharge as much warm water into that waterway.
Solar doesn't work at night, and sufficiently scalable energy storage technology doesn't yet exist.
Solar loses considerable capacity as ambient temperature increases. At 40°C ambient, you're talking about a 15% or higher reduction in efficiency. Which would be HIGHER than the ~12% reduction in nuclear capacity Europe hmis seeing
They are buying up capacity from manufacturers who are stopping production of DRAM and pivot to HBM which is more profitable. Abandoning DRAM which affects a lot more than just "consumer grade RAM"
You're most definitely wrong here because the first step is to announce something like this because a project like this requires gathering a significant number of contributors.
They're trying to hard fork Firefox, which means they are trying to take on the engineering efforts of hundreds of full time engineers who are browser development experts. To keep up with bugs, web standards, security patches, and performance. Nevermind new feature development.
How are they going to maintain the hard fork when something like 95+% of all engineering efforts that support LibreWolf and similar come from the Firefox engineering team?
Mostly mundane stuff like security patches, performance fixes, and web standards features and updates make up the bulk of the engineering efforts.
Literally all knowledge and understanding requires memorization of some sort and the understanding of reality and prior information.
It is difficult to fathom the level of wrong in this comment.
Here's the thing people who lack knowledge, critical thinking and understanding about the how the world works. Still form opinions and makes decisions as if they did have that knowledge and understanding. Which negatively affects everyone else.
It's only bike shedding if the people arguing over it don't know enough about the topic to actually make cohesive arguments.
Things like how we name things and the grammar we use are quite important in cognitive psychology. And we can take advantage of research into cognitive psychology to better improve how we write software.
No, they're throwing the book at him to make a statement.
Their argument, which is stated in the article, is that since he was not in the US (you are not considered in the U.S. until you go through border protection, even if physically here), US rights and protections don't apply.
Similarly, this isn't destruction of evidence they are charged for. It is destruction of property to prevent seizure. Which is a bit awkward because that's a law in the US, but he isn't in the US yet....?
Of course, it's all bullshit. We all know this, but this is going to set a very dangerous precedent if it sticks.
I mean, screw performance. You can get away with a lot of shitty performance and still have a completely functional application. However, the kind of slop that happens around module boundaries that turns your codebase into a giant pile of workarounds and hacks really sucks.
And AI is particularly bad at this, as AI almost always prefers to work around a problem or do everything it can to meet the plan the user approved, even if that plan meets reality, it has problems. Which tends to lead to cascading misalignment with intentions and cascading infrastructure and architectural technical debt.
All of which culminate in less stable software, lower likelihood of long-term support of that software, and worse performance.
FR. If a relationship gets to this point it's for a reason.
If the partner is prioritizing games over their relationship or responsibilities, and is making the other feel like they have to compete for attention and time with their partners habits or addiction. They have every right to desire to leave that relationship because their needs are not being met.
It's not a reasonable response at all. It's unhealthy AF.
If the partner is prioritizing games over their relationship or responsibilities, and is making the other feel like they have to compete for attention and time with their partners habits or addiction. The affected partner hss every right to desire to leave that relationship because their needs are not being met in that relationship.
This is what the ultimatum is targeting. His response being intentionally obtuse and flipping it back around to the partner whose needs are likely not being met in their relationship being the problem is extremely toxic and manipulative.
Anyone can tell anyone anything, it doesn't make it true or validated.