HN Simulatornew | past | comments | lists | submit | martinald's commentslogin

But they don't have a monopoly. Their marketshare is sinking, down to perhaps 45% of estimated TSMC CoWoS supply next year (down from close to 70% last year).

75% gross margin. For a market this big. This not healthy free-market competition working as expected.

Chip company profitability is notoriously fleeting and cyclical.

I wonder if the large margin is due to off book sales.

Nobody made AMD Radeon shit the bed, see: geohot’s experience with getting model training and inference working on AMD

Nvidia is right to cash in on the benefits of its long term strategy, including making CUDA available on grad students’ lowly gaming GPUs.

US capital markets are the envy of the world because winners get to take all (from the world, not just the US), instead of getting smited into oblivion for being head and shoulders better than the competition


UK doesn't have the same tariffs the EU applies though...

Depends what market you are in. In the UK I would estimate M365 usage is ~100% of local/national govt.

And in terms of classic 'corporate' sectors like law, finance, etc, it also close to 100%.

Whereas in "tech" it is far more likely to be Gmail.

I _still_ get people who are non technical that work in 'corporate' sectors that can't join a Google Meet because they think it is Teams. They literally haven't ever used a Google meeting before.


Absolutely bizarre wording of these updates. Strangest corporate speak with urgency turned up to the max.

copilot, make this doom and gloom situation sound better. assume you're using the voice of a friendly but intensely focused sysadmin. use only neutral language.

Nearly all EVs now do "battery preconditioning" when on the way to a charger. They would be pretty unusable without, I know one person had a model that didn't have it (this was a few years back) and he could barely pull more than 10kW in winter from public chargers, vs 100kW+ in summer at the exact same chargers.

But just because there isn't a working PoC on GitHub doesn't mean there isn't one and things aren't been actively exploited.

If you are a bad actor you probably don't share your PoC around as it means less boxes to hit.


You can never rule out the possibility that someone interested in attacking you has a non-public exploit, but it's dramatically less likely if there aren't already working exploits circulating all over the internet.


It was true before great LLMs era


I don't think that's very true. Certainly, modern LLMs make it much easier to discover a vulnerability given only limited clues—but if it's easy to find that way, then probably someone will do that and post it for clout. So if no one has, then it probably isn't.


I have a bad gut feeling that every day is going to look a bit like today with endless urgent patches and breaches.

Fwiw it sounds similar to the hack over the weekend that opencode suffered.


The security team at my company is working with a frontier lab to scan all our code/systems. They are in a borderline panic to close every possible issue, even innocuous ones that are buried under defense in depth. Whatever they are seeing from our partner has them spooked -- as in "acceptable risk" is no longer a thing anymore.


What company do you work for?


The internet is over. We are going back to static htmls for public pages, and Point to Point VPN bases connections for B2B service provision.

B2C? too risky to publish services online haha.


>We are going back to static htmls for public pages...

God yes, please. I backpack and mountaineer in the PNW and have been trying to research trip ideas up in British Columbia, and as a result I discovered https://bivouac.com.

Here's a website that's still frequently used by a large number of people as a valuable resource, is regularly updated and maintained, and yet looks like it's straight out of 1995.

Every pages loads instantaneously, everything is simple yet packed with detail, and it's such a basic, straightforward, delightfully pleasant experience to just browse through the site. I was so thrilled after just 5 minutes on the site that I threw them $25 for a year's full access.

Sorry for the tangent, but oh man, it's such a refreshingly stark contrast to the rest of the bullshit that fills the web these days.


Simple and fast also works better when you're sneaking some internet from your hike to recon your next chunk of trail, good on them!


Still some industries where you cable colocated servers in a shared DC together where neither server has internet access.



I think you missed why they’d be doing it in the first place.


No, but being able to directly cable two servers in a COLO rack isn't always possible.


Static HTML, yeah.

Not sure about VPN. Seems likely to provide a false sense of security.


I think they mean VPN as in WireGuard where each customer would have a separate private network to the service provider. This way the service wouldn't be exposed to the public Internet.


MTLS would do the job, but you still just need one compromised customer.


I fully believe the only sustainable future is that hot patching will need to itself become fully automated. Hot patch now with a minimal allowed amount of line changes to head off the AIs, review it in office hours for auditing and the team is actually awake.

My second belief is that environment variables as a development concept will need to be retired. If it's something that causes a security breach if it by its mere existence on a public git repo, it is information that by design cannot ever pass to a filesystem out of a chain of trust, not by mere development conventions people choose to adhere to.


> hot patching will need to itself become fully automated.

Great, even less control over the things we use and more power ceded to corporations.


Due to the small nature of hot patching (eg. bump this dependency, rotate these keys, turn off that config, follow the runbook) it will unlikely need to be a frontier model and is likely able to be done LocalLLM/Jev style decision making rather than having to hand all the keys to frontier model operators.


One more step to just turning it all over to Skynet. It's hilarious how prophetic that movie was.


Do you want your shit hacked? Better patch.


And where does that leave the tenet of auditing patches?


Do you want to get hacked or audit the patch?

The barbarians are at the gates and they're interested in laundering your compute and network for other attacks, scams, and things like transferring CSAM.

How much time do you need to audit? You might have an hour - for now.


Hot patching is itself a liability


Not reacting is a liability. Blue-Green deployment is a liability. Code is itself a liability. Choosing this career at all is a liability.


For the record, there was a bunch of non-functional vibe coded fixes flying around during this PHP bug. If you were just running the first thing AI made because you were worried about "not reacting," you would likely end up running a crap script.

AI is quite good at finding vulnerabilities, but it's been rough for patching them. The old adage "defenders have to be right every time, attackers only have to be right once" applies to AI security patches.


Great, but the fact remains that easy hot patching which skips normal review is going to open you up to many of the same liabilities you're trying to minimize by introducing it. The target just shifts, and people will attack that infrastructure.

The actual solution largely involves the same technologies but in reverse: leveraging AI for live security monitoring, better correctness validation and security testing before code goes live, etc. And of course more pressure to use battle-tested widely-adopted libraries and systems, even though of course that comes with its own tradeoffs.

Importantly, as an engineer, when someone tells you something has liabilities or tradeoffs, the response is not "Everything is a liability, existing is a liability"; that is unprofessional. The appropriate response is to engage with them on these tradeoffs and working through the best ones, because that's your job. Otherwise defer to security engineers who are ready to back up their arguments. It could be as simple as following up with, "But do you think those liabilities outweigh the benefits of hot patching without proper review? What are some of the main liabilities you see, and what methods/technologies do you think properly address them?"


With AI, in the long term open source code might actually become more secure than obfuscated closed source, since it's had so many more (AI) eyes looking at it.


It's only just starting. It'll get worse before it gets better.


I think the only way out is to go back to on-prem for everything, like in the 00s.

LAN cables will go up in price soon.


I think we'll see a reduction in complexity and an increase in transparency, rather than just on-prem.

One medium-sized server can now easily serve the entire banking system of a large country. So you don't need clusters of servers with careful tradeoffs between consistency and availability because of the CAP theorem.

Just get a big honking host, slap Postres on it, and run your application server in a VM on the same host. For backup, export the WAL logs from Postgres onto your favorite off-site blob storage. UI for it? There's Pigsty.

It still makes sense to host this in a cloud provider, just because you probably don't want to deal with actual hardware. And maybe get a second standby server for redundancy.

That's it.

You'll need a bunch of external dependencies for email, 2FA, observability, LLMs, and so on. But they should all be outgoing dependencies that should not allow access back into your system.


Real loads are too spiky for that.


A PostgreSQL server on an NVMe can handle several _million_ simple requests per second. This is bonkers.

Do you think you can hit these load levels? For compute, a 64-core CPU can saturate a 10G network with simple template rendering. If the code is written in something reasonably fast (Go, Rust, Java).

Of course, if you're on a scale of Amazon or Stripe, you'll need more than that.


This is how we spot someone that has never done transaction processing in a consumer facing business. You are focused on completely the wrong dimensions.

Postgres fanboys are insufferable.


You sound insufferable. Educate us, wise guy.


Ha, Cyberpunk 2077 is becoming reality. We're proposing the Blackwall.


That was always going to happen. The future of the internet is AIs scamming you and your grandmother, ransomwaring you, draining your back accounts, etc. There will be no reason or rhyme, it's simply a function of available compute and ease of automation, both of which have reached a critical threshold.



"So you want to build your own data center?"

https://blog.railway.com/p/data-center-build-part-one


They then say they are colocating. Something everyone and his dog did as a hobby 25 years ago.


How does on-prem help if your product is a SaaS.


You open a SaaS shop where people come to use it


Instead of being a SaaS it will need to just become a S


You put the SaaS into a Box your customers can install into their datacenter!


What a brave new concept!

Sometimes I do miss owning the hardware to run a thing.

What I don't miss was having all of those appliances run a different base distro of Linux, each with varying levels of update support, while the security team keeps reading security scans to me.


Like back when you could rent a Google appliance.


surely once there's been enough patches the code will be perfect though?


Interestingly, in the UK you can get 31 JA solar bifacial panels for ~£2k+VAT including shipping (https://www.solartradesales.co.uk/ja-solar-455w-n-type-bifac...), so around $2.6k.


Renewables require gas in the UK. There is no realistic route to 100% renewable grid without gas currently. I did some modelling of this and you'd require something on the order of 4000GWh of battery storage. We currently have 40GWh.

Gas is far, far cheaper than building ~£1T worth of battery storage. Even if prices dropped, you are still looking at multi-hundred billions, and you still need the renewable capacity on top of that.

Arguably if we had spent the £100bns (in subsidy and transmission upgrade and curtailment costs) we've already spent on renewables on nuclear instead we would have a very clean grid, even at crazy UK nuclear build prices, and stable electricity prices.


Last time I did the maths based on data from gridwatch the storage capacity required dropped dramatically if you over built the on the production side.

But ok, 30 million homes, 100kWh storage each, that's 3000 GWh

A 100kWh battery is about £25k, less than 1/10th the cost of the house, and less than the average new car

That doesn't seem unrealistic.


The issue is you need to design for 1-2 weeks of little to no wind and very little solar in winter, when demand is it its greatest. This is what is so tricky, unlike more southern climates where you have pretty reliable solar year round (even if its reduced, its not close to 0 which is the case in the UK). Instead of storing a day or so, you need to store weeks of energy.

Also you're forgetting residential electricity is maybe 1/3rd of total demand.


You said your modelling needed "something on the order of 4000GWh of battery storage"

That's not outlandish given the cost of distributed batteries.

Are you upping that model?

(If you build more generation -- for example have renewable peak generation of 80GW rather than 40GW, that reduces storage requirements drastically, as on a dull quiet winter week where you're only getting 10%, you'd be generating 8GWh in a given period of time, instead of 4GWh)


Where do you get "close to 0"? From what I read the output is still 15-30% of the summer peaks, which is very different from "close to 0".


On average. That doesn't mean there aren't sunny weeks where you get a lot more, and dark weeks where you get less. For instance if you get snow, output is pretty much 0 unless you clean them.

I believe there were 7-10 days in January 2025 where both solar and wind were in the single % digit for instance.


Of those 7-10 days, how many were consecutive? A couple days of single-digit efficiency each winter would be trivial to manage with batteries. I'm sure we can figure out a solution for the snow issue, especially since panels are usually angled.

Don't get me wrong, I get where you're coming from! But especially in the last 2-3 years, it seems like people always evaluate solar under the worst 0.01% chance scenario, which other power sources never have to survive. For example, not even half the days in January 2025 had single-digit outputs, yet they're still called "close to 0".

What I'd love to know is e.g.: in 99% of years, what's the worst Dunkelflaute we can expect? How much battery storage/solar overbuilding would we need to cover that, how much would it cost, and how much will it cost in a few years (based on current development rates)? I'd argue it'd be okay to reduce power-hungry industry for at worst few days, in case a once-in-a-century year happens.


The issue is though that you are saying 0.01% chance scenario, but gas/nuclear doesn't all go down at once at the same time every year. It's a somewhat fair counter that you might have serious gas disruptions, but LNG does massively diversify potential supply (and in the UKs case we have and will have a fair amount of domestic production for the next while).

Also keep in mind the overbuilding a massive problem anyway _outside_ of those 1-2 weeks worst case scenarios. We already have highly negative prices occurring more and more, and IMO this is the definition of policy failure, because the negative prices only arise because subsidies _encourage_ plants to keep producing even though the value is quite literally negative of the output.

Finally I don't think it's once in a century, probably most years have a significant Dunkelflaute event. And not all industry can be shut down like that (eg aluminium production) without causing catastrophic damage, and even if they can it makes them an unreliable supplier.


> The issue is though that you are saying 0.01% chance scenario, but gas/nuclear doesn't all go down at once at the same time every year.

Over this summer, a huge number of nuclear plants in Europe went down all at the same time, because they either would have killed the nearby river ecosystem by overheating it, or because they didn't have enough water to operate safely. This issue is only going to get worse as climate change progresses, and unlike most Dunkelflauten, the heat & drought really affect most of the continent at once.

> Also keep in mind the overbuilding a massive problem anyway _outside_ of those 1-2 weeks worst case scenarios.

It's only a problem because power generation tech like nuclear is so expensive, and it would become even more expensive if they couldn't run as much as possible. If we had a fully renewable+battery-driven grid, the issue would disappear.

> Finally I don't think it's once in a century, probably most years have a significant Dunkelflaute event.

I think you might unknowingly be ideologically motivated, because I specified that we should build enough to cover every Dunkelflaute in 99% of years. The amount of battery storage in this scenario by definition suffices for 99% of years, which makes the point about unreliability moot.


[dead]

Yes, I have no doubt we can hit even a 90-95% renewable grid. It's the last 5% that is impossible to do without gas.

The cost of those last few percent is absolutely eye watering. The current plan to get it to 100% net zero is by having gas for the final 5% then using carbon capture and storage to offset the emissions.


you don't even need to use carbon capture and storage if you use green gas instead of fossil gas.


It is not even the final 5%, it is the final 1-2%, because you need a multi-week dunkelflaute across Europe for the gas turbines to be needed in the future. A lot will also just be curtailing. For instance EV charging might be restricted in the future in such a winter black out scenario.


> For instance EV charging might be restricted in the future in such a winter black out scenario.

Or indeed when petrol runs out as happens occasionally (in 2022 most recently). Of course there's also the problem of gas supplies stopping


You are making the mistake of thinking that if the grid could provide 100% renewable energy on a windy day at noon in summer, it could also provide 100% renewable energy at night in winter with no wind. Obviously that’s not accurate. Renewables provide energy in a highly volatile sine wave. It’s the bottom of the sine wave which determines the capacity required for base load and dispatchable generation, not the top of the wave.

[Gas is about 11-13x cheaper than renewables with externalities like grid restructure and volatility imputed.](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4028640) That’s not to say renewables don’t have their place in modern grids. In fact an optimal allocation is around 80% renewable in the UK. However, until battery storage becomes about 95% cheaper, it would be ASTRONOMICALLY expensive to make the grid 100% renewable. Trillions of pounds in the UK. An order of magnitude more expensive than just paying higher gas prices.

People often make the mistake of thinking that because wind and sun is free, the cost of energy generation is basically free. Those people don’t understand how many fixed and marginal costs there are. If you’re interested, the paper above provides good insights into those costs.


Do we know if claude -p is now drawing from this API usage?


Not yet, as of version 2.1.293. But I suspect this is coming next.


How credits work with `claude -p` is a common question we're seeing. we're updating the faq now to make sure it's more clear. Will share updated docs soon

Update: We just updated the docs to clarify how API credits can be used w/ claude -p: https://support.claude.com/en/articles/15036540-use-the-clau...


That's what the Agent SDK is, according to this help page:

https://code.claude.com/docs/en/headless

So, as written, yes.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: