just ask AI how to build a fusion reactor, ez
To add to this, spent fuel is over 90% recyclable. If the US were to instate a comprehensive recycling program like France has done, the spent fuel cache could be reduced to negligible amounts.
If it results in the nuclear plants remaining online and providing energy after the AI bubble pops, that doesn't seem so bad.
Fission is one of the cleanest energy sources we have today.
Which GPU do you have? I'm looking for an upgrade and those framerates make me drool.
I thought they had white coats because they take their methamphetamine production lab very seriously.
So you're saying Rust is the TOOL of programming languages.
Point of clarification: DAC is copper, AOC is fiber.
A lot of 10G equipment will support 5G/2.5G SFPs as well, so it can still be beneficial to go 10G on the core equipment.
There's that awful dad joke that foggy was talking about; Use it as inspiration for your exasperated sigh.
Not for the same cost per gram as good ol' Horse Electrolyte™! Talk to your Ivermectin dealer today!
Signing every message should have zero effect for people who don't use PGP; they'll just have a cryptic block of text at the bottom of the message you sent.
It's overkill to ship your pubkey with every email. Most people just publish to a trusted keyserver and call it a day since pretty much every client worth its salt can look up your pubkey directly.
One way they could increase the housing supply is by severely taxing corporate ownership of single-family homes (and possibly low-occupancy multi-family homes like duplexes).
Give it a grace period, say... 3 months (to cover the cases where a bank forecloses and is sole owner while the house is auctioned), then charge like 95% tax on market value every quarter.
Ted Ts'o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.
I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.
The hardline C devs that don't want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.
The Rust devs that are getting upset because people are "attacking" their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it's a matter of momentum and greybeard stubbornness.
In fairness, "I don't want to maintain bindings for a language I never intend to use" is a perfectly reasonable position.
The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).
omg dude you can't just ask about white collards
alternate joke: I guess you could say it's a white collard crime?