That might be true for general consumers, yes. Not so true for software developers though. For developers, the tooling is definitely not a moat, and that means the models are what must differentiate.
Claude code is very polished, but I can get the same jobs done using Cursor CLI or any number of open-source coding harnesses (I like Pi, personally). Most plugins/skills/mcps are portable between harnesses with minimal or no effort.
I use the same skills, rules, and MCPs across claude code, cursor, and pi. My tools/plugins aren't identical between harnesses, but porting them from one to another is just a prompt away.
LLM-driven programming doesn't necessarily imply slop. I know some very good developers that use LLMs carefully. As a research tool, code reviewer, Q&A about a large codebase, error message decoder, bug-hunter, and for first-pass implementations. They're always on the newest models and they care about the craft.
Not everybody is oneshotting with Sonnet medium and pushing unreviewable code.
Another option is that it's affected by the order of consumption.
I know somebody who got really into blood glucose monitoring, and she tells me that the order in which she eats a meal affects how much it spikes her glucose. So if she eats a piece of toast followed by a piece of cheese, it causes her a bigger glucose spike than she'd get if she eats the cheese first and then the toast.
Looking at the two meals in the study: if I sat down to eat the processed one, I'd probably start with the veggie straws. If I saw down to eat the unprocessed one, I'd almost certainly start with the egg or the cheese.
edit: and here are some other options: I notice that the unprocessed one is grain-free, vegetarian and has significantly less sucrose. I don't know if any of that makes it more or less healthy, but they're significant differences nutritionally.
If you look up how to calculate the glycemic index of a meal, the formula treats each meal component's glycemic index as a proportion of the total meal's glycemic index.
But the above example shows that the body doesn't treat food in that manner - the relatively low carb, higher fat cheese didn't smooth out the higher proportion carb count of the toast.
In the paper, the largest carbs for the ultraprocessed meal was instant mashed potatoes, while the non-processed meal had bananas as the largest carb source followed by craisins/cranberries.
The high carb foods in the unprocessed meal are paired with fiber.
The high carb foods in the ultraprocessed meal are NOT paired with fiber.
The fiber slows the rate of carb intake.
Same thing occurs with protein - same amount of ground beef and steak, ground beef meal will result in faster amino acid ingestion than the steak meal. No idea if there are any pros/cons of the faster ground beef ingestion, but there is a difference in how the digestive system processes the two meals.
> I know somebody who got really into blood glucose monitoring, and she tells me that the order in which she eats a meal affects how much it spikes her glucose. So if she eats a piece of toast followed by a piece of cheese, it causes her a bigger glucose spike than she'd get if she eats the cheese first and then the toast.
This is what I read in a book about glucose. So I went ahead and measured. I found it not true, at least in my case. The recommendations of eating salad before your meal do nothing measureable for my glucose spikes.
As currently practiced, yes. Non-dividend non-voting shares might as well be pokemon cards. Their only real value lies in getting somebody else to buy them, and new money has to flow in from the outside. The question isn't "will it collapse?", it's "when?"
The fact that those are so few relative to what dividends would be is a measure of the market's (lack of) health. But it doesn't automatically make the market a Ponzi scheme.
My god, this is the most HN comment of the day. You do know that most normal people buy a house not to resell it at profit, but to have a place to live, right?
It’s almost always both. Basically every single retired person I know in my family or friends of family are relying on their home to be their primary asset/income in retirement. It’s always a much larger chunk of their net worth than any retirement savings, if they even have the latter.
They were commonly called forced savings accounts when I was growing up. The standard advice was to buy a home as an investment vehicle. Every older family member giving me advice would preach about how they don’t make any more land and the price will only go up.
You can - to this day - talk until your are blue in the face to these people that your primary place of living is not an investment, but they will refuse to even entertain the idea even with the stark cold math staring at them in the face.
If these retired folks can’t sell their homes for a huge profit they will be in for some very difficult times a decade or two from now. They are highly motivated to keep the music playing as long as they can vote and show up to local city council meetings.
The US is pretty unique in that mortgages are typically fixed for the length of the loan, which means the monthly outgoing is guaranteed to go down in real terms due to inflation
Renting means that your rent will typically stay the same in real terms, so increase each month, and indeed you might find your landlord decides to sell and suddenly you're homeless.
Most people in the UK, despite lifetime fixed interest mortgages being very rare, buy for stability, and to ensure they don't have to pay rent in later life. They might do an equity release as they are retired to give them more money, but that's certainly not the norm.
Now the buying of additional properties from the mid 90s was very profitable, house prices would increase far more than rental income, and you could leverage that, and some people (spurred by daytime tv shows) decided to buy a house, spend 100k doing it up, and selling for 150k more than they bought it, making a 50k profit. Had they not done it up they'ld likely have made more money, as the profit was caused by increasing house prices.
Certainly in the UK that was still a small part of the market.
The biggest leap was the move from the mid 90s to the mid 00s of house price:wage ratio from about 4-5:1 to around 7-8:1 as mortgage companies would lend more -- typically 4 times two incomes (in the 80s and 90s mortgage companies wouldn't lend that much).
Since then house prices have broadly remained locked to wages at a radio of 7:1. Its dropped to about 6.5 and gone up to about 8 over the last 20 years.
The point is it has value and can be resold later to get your capital back. Housing tends to be a mediocre investment at best but folks do generally expect to be able to get their capital back when selling.
Houses have real value by themselves as you can live in one. But they have been treated like a Ponzi scheme recently which is why we are in such a mess with housing
I think the GKI initiative is great, personally. I've worked with chip companies that are super-resistant to upstreaming their code, and just give me a fork-of-a-fork of the kernel and kind of say "welp, good luck maintaining that unless you pay us".
I don't love how much control Google is exerting over Android, and I don't love having to use their signed kernel. But I do prefer that vs. being stuck on an abandoned vendor kernel. If I have to accept low-quality proprietary kernel code, I'd rather keep it in small module-shaped boxes.
Companies like Qualcomm complain about this, but their historical practices are what drove Google to mandate it in the first place.
How open will the boot stack be for this chip? Qualcomm has historically been pretty bad about this: mandatory closed-source bootloaders, mandatory closed-source hypervisors, mandatory closed-source TEEs, forked UEFI, etc.
An open Linux is hobbled without the rest of the stack.
Non-native speaker here. I hadn't noticed there are two words for what seems like the same thing. Is there a difference between a water boiler and a water cooker?
oh, no that wasn't a correction - it was a pun because "cooked" in American slang means "broken / destroyed / over". In parent's context, "boiling" is correct.
"Boiling" does have a few meanings in English. As a verb, it can either mean "cook in boiling liquid", or it can mean "heat a liquid to its boiling-point". As an adjective, it means "heated to boiling-point". Also "boiling angry" means very, very angry.
Claude code is very polished, but I can get the same jobs done using Cursor CLI or any number of open-source coding harnesses (I like Pi, personally). Most plugins/skills/mcps are portable between harnesses with minimal or no effort.
I use the same skills, rules, and MCPs across claude code, cursor, and pi. My tools/plugins aren't identical between harnesses, but porting them from one to another is just a prompt away.