jakobnissen

Denmark is not a good model to understand what China can do, because we are a small country who can import a big share of our electricity from abroad when it’s not windy, and export excess capacity when it is. It will be much more challenging for China to achieve what we have done.

Put more directly, our numbers look good because Norwegian hydro and Swedish nuclear saves our bacon when our windmills don’t work; China does not have that luxury.

This is completely infeasible. A C compiler makes so many assumptions that UB does not occur that every program, even well functioning ones, would emit walls of warnings. Also, these warnings can't be silenced. Consider the integer division case: Should the warning be emitted every time division by zero is encountered at runtime? In that case, C would be much, much slower. Or should the compiler emit the warning whenever it can't prove at compile time that the divisor is not zero? In that case, you would get tonnes of situations where you can't fix the issue because you can't prove to the compiler it's not zero. Division by zero is a easy case. It gets much harder to emit warnings for aliasing assumptions, for example.

So not much progress since 3.14 - but still progress! Personally, I think it's nice when my code automatically gets faster thanks to someone else's work, and I don't understand all the negative sentiment in this thread. Yes, of course Python is still a slow language. You hopefully knew that when you picked Python for your project.

I don’t think that’s right. The US government cares a lot about what the public thinks about them. They propagandize actively on social media, the president puts his personal name onceverything, they are extremely persistent in their messaging to loyal reporters and so on.

I think they have discovered that what the public thinks simply no longer tracks what they actually do: "I could stand in the middle of Fifth Avenue and shoot somebody, and I wouldn't lose any voters“

No I don’t know how he gets that info. Most contributions to the language these days are AI assisted, but that’s a completely different matter. IMO if you can afford AI assistance, it would be irresponsible to not use it, given how good AIs are st bug finding and code review

You can not be serious in suggesting these aren’t straight up Python correctness bugs. Exactly the same kind that Yuri brought up as damning evidence of Julia unseriousness, but for Python with easily 25x the user base.

Completely true, but Mojo approaches the problem from a different angle. Where Julia aims to blend fast and slow code seamlessly, Mojo's solution is to have a set of opt-in semantics that ensure fast code.

No, this is not splitting hairs. This is the author using the straight up wrong terminology. Regex can’t match HTML, and aren’t NP-complete. The fact that the author believes that “regex obviously means PCRE” is objectively wrong and misleading in the sense that all the things his article are about would have another conclusion if he actually talked about Regex.

It’s like if there was a library called QuickSort which also included a SAT solver and I then wrote an article about how you can solve SAT-equivalent problems with quicksort (“in the programmer sense, which obviously means a SAT solver”)

This article misleads you by conflating regular expressions with specific implementations like PCRE, which also does non-regex string matches. Annoyingly, the article does a good job of explaining what a regex is and what the limitations of regex are relative to PCRE, so the author should understand that what they are talking about when they talk about NP-complete string matching is not regex, but PCRE-specific features.

The distinction matters because regex absolutely can't match HTML, and because regex, unlike PCRE expressions, have guaranteed O(1) space and O(n) time complexity when matching a string of length n. When you use PCRE features for string matching, that may degrade to exponential time which makes it useless. For example, you can do denial of service PCRE attacks, but not denial of service regex attacks (unless you can query with some megabyte-large regex).

Yes but the question is why Ruff has not released v1 yet. They’re clearly used in production and the entire purpose of v0.x is to signal a project is early in development and is expected to have coarse edges.

But being non-inclusive by speaking to a particular cultural reference frame is not the same as being racist.

But that’s exactly what the inflation measures of the BLS is - someone doing the math on what all these things cost.

Why is the government measured inflation not the same as real inflation?

Their outages are probably not due to their code though. It’s probably their infrastructure that can’t keep up. So seeing failures of infrastructure doesn’t really tell you anything about how good or bad Anthropic makes use of their models.

This sounds horrifying. It’s one of those stories that makes me think in just how many ways our bodies or minds can break or malfunction in terrifying ways. Any one of us could, right now, carry a lethal tumor that hasn’t been discovered.

Best of luck to you, and get well. I’m glad it didn’t get even worse before it was treated.