Turskarama

Yes but all of those things are independent of the size of the country, which is the point.

Do you imagine an infrastructure project in ANY country is managed like a project in a small company?

- The United States is 85 times larger than Switzerland. The entire country of Switzerland is the size of a small US state. Covering the US with broadband is much harder than Switzerland.

I see this argument come up a lot with regards to all kinds of infrastructure, and the thing is it simply _isn't true_.

What matters is population density, GDP per capita, geography, and will. A countries size doesn't matter since twice the area will, all things being equal, also give you twice the workforce to make it happen. In fact the only change a larger area typically makes is better ability to make use of economies of scale, which makes things _easier_.

The only correlation between larger countries and trouble with infrastructure is that a large country is more likely to have large areas with nearly nobody in them, but these areas also typically account for a vanishingly small percentage of the population so they don't really count when people are talking about bad infrastructure.

The difference is that the US companies are using it as a means to an end, they need to make just enough profit that the investors don't all get cold feet before they get to AGI. The Chinese companies on the other hand are trying to be profitable immediately, which means that they're going slower to save development costs.

Just because the users were already sick when they started using ChatGPT doesn't mean that ChatGPT isn't exacerbating the issue. Sickness isn't a boolean condition. A big problem with LLMs in general when it comes to people like this is that they are too sycophantic, they don't push back when you start acting strange and they're too gentle about trying to validate you.

In my experience AI can write _something_ from scratch, but often edge cases won't be handled until I go through and read the results or test it. Usually when I'm writing by hand I will naturally find the majority of edge cases as I go. By the time I've read through the results and fixed said edge cases, I usually would have been faster just doing it myself.

Agile cannot go over budget or scope because those are failures of planning. Agile is the methodology that was developed specifically to counteract those problems with planning. Projects that use Agile can go over budget and scope but they never do that because they are using Agile, rather they use Agile because they might do that.

Which is fine, the average bike thief is not going to expect to need them.

Yes, there's a reason it was abandoned as a KPI almost as soon as it was introduced. Just because AI is writing the code instead now doesn't magically make it a good metric.

You should have kept reading.

  For performance-sensitive scenarios where case types include value types, libraries can also implement the non-boxing access pattern by adding a HasValue property and TryGetValue methods. This lets the compiler implement pattern matching without boxing.

If Windows update does something weird what do you do?

In many ways the quality of care in the US is far better than what folks get elsewhere, which in part is probably why there isn’t a total patient rebellion

How sure of this are we really? Other countries mostly have problems with emergency departments being full, but that's less because those emergency departments are worse and more because in the US people aren't going, they just stay home and hope they don't die.

Actually you're right, I was going by the source code which was in the link of the comment you replied to, but I missed that that was specifically for divExact and not just primitive division.

More specifically, Zig will return an error type from the division and if this isn't handled THEN it will panic, kind of like an exception except it can be handled with proper pattern matching.

Have you ever had a concept you wanted to express, known that there was a word for it, but struggled to remember what the word was? For human thought and speech to work that way it must be fundamentally different to what an LLM does. The concept, the "thought", is separated from the word.

I have seen people say something along these lines what feels like every month for the past year.

The point is that it's a litmus test for how well the models do with niche knowledge _in general_. The point isn't really to know how well the model works for that specific niche. Ideally of course you would use a few of them and aggregate the results.

I think ideally you need to practice both slow AND fast. You need to practice slow so you can notice and work on small details that can be skipped over with speed, and you need to practice fast because some things are legitimately different at speed and you won't learn how to deal with them only going slow.

The problem with publicly disclosing these is that if lots of people adopt them they will become targeted to be in the model and will no longer be a good benchmark.

The problem with integrating a chat bot is that what you are effectively doing is the same thing as adding a single bookmark, except now it's taking up extra space. There IS no advantage here, it's unnecessary bloat.

The computer chips used for AI generate significantly more heat than the chips on the JWST. The JWST in total weighs 6.5 tons and uses a mere 2kw of power, which is the same as 3 H100 GPUs under load, each of which will weight what, 1kg?

So in terms of power density you're looking at about 3 orders of magnitude difference. Heating and cooling is going to be a significant part of the total weight.

They didn't actually fix this until a couple of months after they publicly revealed that this was the reason the game was so big and a lot of people pointed out how dumb it is. I saw quite a few comments saying that people put it on their storage HDD specifically because it was too big to fit on their SSD. Ironic. They could have got their own data quite a bit earlier during development, not nearly two years after release!

It actually is somewhat a limit of the technology. LLMs can't go back and modify their own output, later tokens are always dependent on earlier tokens and they can't do anything out of order. "Thinking" helps somewhat by allowing some iteration before they give the user actual output, but that requires them to write it the long way and THEN refactor it without being asked, which is both very expensive and something they have to recognize the user wants.

There is one absolutely massive one, and that's that for the first time the problem is truly global. Other famines have been caused either by war or local droughts, both of which affect only a population in a limited area and crucially, can be somewhat mitigated by importing food from elsewhere. You can't import food if there are global food shortages.

It's the same issue, if you have a higher voltage then you can get more power without increasing current.

For example in Australia a standard house circuit is 10 Amps, but because it's at 240V we can get 2400 Watts (realistically more like 2300) out of a _standard_ wall outlet that is in every room of your house.

Everything? No. But routine stuff will NEVER be denied. If your doctor thinks you need a scan, you're getting the scan. I have quite literally NEVER heard of someone in my country (Australia) going bankrupt from medical bills. It can happen but the rate is so low it's not something anyone ever worries about happening to them.

Let me blow your mind for a second: this problem is not insurmountable in language design, C is not a perfect language, and nulls are bad design.

The best of both worlds would surely be for the LLM to write what you've asked, but also write comments about other things it could have done so you can consider those extra bits when you check the output.

"Functions should always be short" is also one of those guidelines that people treat like a hard rule. There are occasions when a 100 line function is easier to read than 5 20 line functions, or god forbid 20 5 line functions.

Stop being overly dogmatic, it ALSO leads to worse code.

Literally at the top of the docs it says it's in Beta. I don't think you have to think too hard to figure out that seamless integration is the goal but they aren't there yet.