You don’t get to choose, that is the illusion of choice that everyone (or rather most) believes. The stealing is indirect, and it has many forms like: - tax structure: investment income get taxed less than payroll etc etc - tax avoidance: offshore, trusts, using companies to write off the tax plus the benefit provided by the government on these write offs. Using assets to loan more with speculation, worse, the buy borrow die model where they borrow against the asset and the heirs inherit the gains never taxed, among many ways and loopholes. - asset inflation: low interest rates increase the stock and property, good for who owns it, while the poor get to pay higher rent, the cantillon effect - the housing and zoning topic, and how it’s one of the pillar of such indirect money stealing, a topic that needs a book to describe but the solution is simple, depreciating housing as assets. - monopolies and few (or one) companies controlling the price, or hold down the wages, to keep poor people poorer and shifting the money more to who controls the scheme - poor people end up usually paying even more with overdraft fees or higher interests, punishing the poor even further, and these interests goes to lenders and shareholders. - that leads the wealthy to be able to lobby to shape the interests and taxes to their liking, the subsidies etc. when a crisis or hard time happens, all tax payers get to pay and shoulder that but in times of booms the profit stay and remain private. And many more cases or situations, hell, not just monetary stuff, even remote work was attacked because it shifts a slight of power dynamics to employees rather than the employers.
"It's not so different from a lot of other businesses. " It's quite different and that's the point. The issues beyond 'apparent value creation are': 1) asymmetries in power between different actors that induces some to make ill advised actions - passing off hidden costs and especially risks 2) externalisations - aka damaging the environment, labour regs (which exist due to 1) 3) misrepresntations in value to end customer - dark patterns, hidden fees, risks not apparent in the transaction. Entire industries would not work if we had to properly account for a lot of things. "I know I'm getting ripped off by doordash, but I'm hungry and I'm busy and the harm of getting ri" <- it's not just the 'price' that is high and you're 'willing to pay' - that's fine. That's definitely not 'rip off' because you're not coerced in any way for that - that's just 'high prices. The $10 bottle of water at an event <- that is a 'rip off'. It's all the other things in the system that make it problematic. Last mile delivery by poor people almost should not exist as a business because it depends on externalizing too many things. If they provided healthcare, vacation, job security, didn't force people to run around, all that stuff that removes the 'power and information asymmetry' - and then - it still works as a business, fine but it generally wont. Some businesses are structurally unsound, and people invest in them to take advantage of broken systems (social, regulatory) at the margins. Gambling, day trading. A lot of zero-sum stuff. Now 'Robot Delivery' - that's an entirely different prospect. That's an attempt at real value creation. If we got our act together, everything could be delivered by little robots - today - already in 2026. It would reuire a lot of coordination.
He mixed some units there, mostly by translating Chinese costs into OECD/USA costs. China does indeed take 5 years to build a reactor. That's what happens when you build a couple a year for decades. After 20 years, that might be true in the OECD/USA too, but for now you are looking at over 10 years, $10B/GW, and over 8% interest. None of that is the real issue though. The real issue is for at least 8 hours a day, but probably more like 16 hours a day, renewables can generate power at well under 1/2 the price of what he calculated. So they won't sell the 9 units of power he forecast - it will be at best 4.5 units, and the nuclear plant even at his optimistic assumptions never makes money. If you look at South Australia [0] - they are at 80% renewables now. At 80%, the average wholesale is cheaper than what nuclear can supply. The percentage will go higher, probably to around 90%..95%. They are and will achieve that with very limited (ie, cheap) storage. But obviously that isn't 100% - so it becomes a question of what can fill the gap of 60 days or so a year the cheapest. Nuclear has no hope. Generating and storing ammonia using excess renewables and burning it when needed is one of the most expensive forms of energy available - but if you only need to do it for 60 days a year, it is still far cheaper than nuclear, because nuclear's primary cost is it's interest bill, not fuel. The good professor paints gas fuel cost as a disadvantage. But when you are only burning it 60 days a year, then compared to paying nuclear's interest bill 365 days a year it's cheap. [0] https://www.energymining.sa.gov.au/consumers/energy-grid-and-supply/our-electricity-supply-and-market
I think the core problem isn't that the Noise "API" is confusing, it's that Noise is a framework for building reasonably-secure protocols. If you don't know how to build or evaluate cryptosystems, you shouldn't assume that just dropping in a library will somehow make your novel network protocol secure. "Don't roll your own crypto" gets a lot of lip service (and a fair number of eye rolls) but it's really, truly something worth considering because it isn't just the algorithms or libraries you choose: it's about the whole package, including things like wire serialization, internal handshakes/security, etc. Just grabbing a Noise tutorial and building your own implementation is a Bad. Idea. And this is only getting worse now that people can prompt their way through building a "secure" system only to realize they really didn't understand what that means. No amount of Markdown saying, "don't introduce a cryptographic vulnerability in this code" is going to save you if you don't know what to do in the first place. But also: the vulnerability was literally visible using basic Wireshark/pcap traffic sniffing. I'm sorry, but if you don't even bother (or know how) to do that kind of basic security analysis you should stop and look for someone who does to check your system in the real world before you tell people to depend on it for serious work. (That being said, if someone had just typed 'find me a vulnerability in this protocol' in a code agent backed by Fable or Astra with any kind of access to network traffic dumps it probably would have taken about 15 minutes to discover this issue. Might even be significant part of how the above author found it, given the other LLM-ish fingerprints in the writeup.)
 Top