I assume the nuclear reactors are to power the data centers using the new chips. There have been a few mentions on HN about the US being very behind in building enough power plants to run LLM workloads
The frenetic pace of data center construction in the US means that nuclear is not a short-term option. No way are they going to wait a decade or more for generation to come on line. It’s going to be solar, batteries, and gas (turbines, and possibly fuel cells).
That question was asked and answered years ago and the answer is YES (not me personally, but the people in charge)
There are things about China not to be celebrated but one cannot help but admire the way that they invest in their country as a whole. The US is all about "what's in it for me".
Fortunately, we have environmentalists who can protect us from a future of towering nuclear plants and wind turbines with hills covered in solar panels.
Is all that construction really worth it when we could be protecting neighborhoods and historic views?
That's absolutely a fair dig but it's far more complex than that. Our whole manufacturing base being outsourced is on the corporations who chose that "cost-cutting" path.
And it's not an entirely binary choice on protecting neighborhoods and views; for example what's happening in south Memphis with the power plant that's powering the Grok center there is a classic case of environmental racism -- they are cutting costs on pollution regulation because they have a community that they can dump the externalized costs on via their emissions.
Nobody's saying Grok shouldn't have the power, it's just a small detail on how that impact is managed.
That's if the website you're querying is a static html file but the web is much more dynamic and varied. Some of the questions I have: does yesnotice execute js, does it handle an answer appearing on a different page, does it handle ambiguous launch language. In essence: how does it work?
The comments here are pretty surprising. a lot of commenters are very worried about something that seems like a very reasonable change. The license change is to prevent someone like AWS offering managed-liquibase. It might not be technically open source anymore but why does that matter? You can still read/fork/contribute to the source and leverage liquibase internally. The fact that liquibase the company exists and provides this library is great. They shouldn't have to live in fear of their hard work being co-opted into managed liquibase to pass some open source purity test.
For people who don't or can't have Ethernet wiring, I've had great success with Ethernet over coax. My ancient coax wiring gets 800mbps back to my router with a screenbeam MoCA 2.5
MoCA is truly amazing. I'm getting full symmetrical 940 Mbps speeds simultaneously over upload and download using RG59 cable with a pair of ECB6250. It helps that our house is fairly small, as the high frequencies that MoCA uses get attenuated pretty quickly on RG59 cabling, but even still, I'm impressed by the results.
I'm using it for a browser extension, just because I wanted to code more in rust. It's great at what it does and has all the same paradigms from React. The best use case though, would be if all your code is already rust. If you have a complex UI I'd probably use react and typescript.
reply