ragall

A mistake that both Dan and the forum users made, was to discuss averages instead of reliability for certain platforms and/or engine types. Most manufacturers have models with wildly different reliability.

He only gave himself 30 minutes to write the post and publish it.

That's trivially false. There's a large difference between products designed primarily to have a low learning curve, and products designed to maximize the efficiency of users that have been trained in its use.

> If I understand that correctly, it means your app always creates traces

Yes, because otherwise what you propose requires modifying the binary in-place and that's too big of a security hole for lots of (production) environments. Some variants of that could work with an out-of-process method like Dtrace or eBPF, but that means mutating the kernel, even more of a no-no.

EU tires focus on low rolling resistance and low breaking distance (due to environmental and safety regulations), NA tires focus on durability (became people drive a lot more) and suitability for a wide range of temperatures (became of the climate).

Precisely because NA drivers drive a lot more, NA compounds are more focused on durability rather than increasing car mileage. EU drivers are alright with less durable compounds because rubber gets cooked after a few years and would have to be replaced anyway.

Tire manufacturers tend to have different compounds for Europe (focused on lower rolling resistance) and North America (focused on traction and a wider range of working temperatures). I'd guess that California will now simply get the EU variants instead of the NA variants.

Indeed, I put a full set of CrossClimate2 on my German car and the two back tires were completely toast within 24 months and ~15k Km (on Canada). After that I decided to start using proper summer and winter tires.

You're wrong on every count: given the small context window of LLMs, the need for interfaces and scehmas is even greater.

Common law is insane, this is just the last example.

> Even the original ones are actually made in China

Wrong.

Consider that it used to be said that nowadays there is not much class difference in consumption between low, middle, and upper clases in the US, in that the same items are practically available to all. Well, that won't be true shortly, and when only a minority will be able to afford "real" items, made exclusively and entirely by humans, I doubt that democracy will be able to survive, because contempt and animosity between the two groups will inevitably ensue, and democracy can't survive that.

I studied mathematics, and can attest that the attitude of the professor mentioned in the article is very representative of an older generation of mathematicians. Maybe the younger ones are different.

Some mathematicians certainly did, but there's a very large undercurrent in CS, as well as Mathematics more in general, of utter disinterest for applications as well as the idea that the more general a solution, the more "worthy" it is. That was really obvious from the words of the professor cited in the article.

> Saying it's overrated is like saying calculus is overrated because most people don't need to use it every day.

You should stop thinking by analogy.

The article was showing the difference between mathematicians and engineers. For the mathematicians that created Computation Science, the only interesting solutions are complete solutions to general questions, whereas for engineers it's perfectly acceptable to eliminate some corner cases, thereby solving a reduced and simplified version of the general problem.

The infra expansion of the hyperscalers is predicated on, and financially justified by, the presumed future growth of OpenAI and Anthropic, and their projected revenue. If the latter is not going to happen, I expect OpenAI and Anthropic to go bankrupt, which will trigger a restructuring of the hyperscalers, which should flood the market with either training HW or training capacity at very low cost, and it's not necessarily the hyperscalers that will benefit the most: I believe some of the GPU clouds are using HW leased or bought form NVidia, and running inside second-tier datacenters, not the hyperscalers.

It's not ingrained in the Wst Coast people, but very much in the Midwest and a bit lesser on the East Coast. Basically proportional to the Nordic heritage of those regions.

Jantelagen is also deeply ingrained in American culture due to the large amount of cultural influence from German, Dutch and Scandinavian immigrants.

This is the Nordic self-effacement which is so ingrained in American culture due to the high number of German and Scandinavian immigrants of the past. Let's just say that not everyone thinks highly of it.

Self-managed open models hosted on GPU clouds.

This isn't a conspiracy, which requires coordination between the co-conspirators: it's just old-fashioned common interest in propping up a bubble.

Juho, you have a well known blog and enough people would read it, so please go ahead and write a rebuttal.

Here's from a VC: https://x.com/bryce/status/2080766415716692385

"Have lost count of the number of CEOs I’ve talked to this week that are planning to be moved off OAI and Anthropic entirely by years end."

On the contrary, he's more obviously right every day passing.

I'd be happy enough if Nvidia decided to launch an update to the now dated (2019) Shield streaming box, which is still the best on the market as to codec support and image quality.

> General lang benefits from everyone understanding it and all the standard debug/test methods applying, which I'd much rather have than easier static analysis of the dynamic part.

Perhaps. I consider that a very narrow view that's detrimental on the long term.

> But they must've had a reason to try it.

They were obsessed with using a general-purpose language, and Python was the thing they knew.

> SREs weren't just arguing about which is better, they were asserting X is deprecated in favor of Y.

This is a kind of dishonesty I saw a lot at Google.

> TF has seemingly stuck outside. I'm still not a fan of that being a DSL, but at least it's one tons of people use and now Claude can easily handle.

Unfortunately Terraform still has significant flaws that prevent it from being used in a reliable fashion.

At the low end, where the vast majority of people are, even in the US, an extra $120 will double the price.

See my reply here: https://news.ycombinator.com/item?id=49216714. The hatred of BCL was due to people not understanding the benefits of a restricted language with carefully chosen semantics, and stubbornly insisting in "a real programming language".

> But it's almost a general-purpose language, so why not just use one?

The usefulness of not being a general-purpose language it that it makes static analysis very good; that's what made the BCL-based tooling so useful: being able to easily diff two versions of the same module (a tool called UBdiff), compute the transitive closure of a module's dependencies, trace the execution of BCL code and correlate it with the AST, to point out where an error comes from.

All these features were either unavailable or took years to develop for Piccolo, because Piccolo was based on Python.

> I'm still not seeing why a DSL was necessary or helpful.

BCL has distinct evaluation rules and a notation that encodes many patterns that SREs used for defining services, and that made BCL code much more compact and easy to ready than all the alternatives.

BCL was designed to be unidirectional: a module was evaluated locally, and the result sent to the Borgmaster. Compare that to Terraform, whose execution model consists of an execution tree where some nodes come from RPCs, meaning that it's not generally possible to statically analyse a TF module, because some errors can come from from feeding RPC results into new RPCs, and execution often fails after tens of minutes. All very janky.

Indeed, those doing frontend work would not interact with Borg or the SRE tools directly, but they would use Blaze, Critique and all the development toolchain, which is still much above anything available on the open market.