6,977 karma · joined May 16, 2011
https://scifi.stackexchange.com/questions/83720/so-that-eart...
Okay, let's ignore "most of the time" and focus on times when carbon-free power was more expensive. Were these companies actually footing the bill in that case? Because increasing the marginal funding toward clean sources when the grid is dirtiest is the whole point.
That's precisely why a 24/7 goal matters. Energy is already cheap and clean for a large portion of the day, but covering the rest of the day will require significant investment.
Look at those numbers. 100% still is a very ambitious goal. Currently 0 global customers are buying 24/7 carbon free power from the grid, and even getting from 0 to 1 will require a lot of boots on the ground building real infrastructure. Afterwards, getting from 1 to [everyone] is just a matter of scale.
Even the "lazy" strategy of buying up capacity from existing nuclear plants requires outbidding the existing customers (if the law allows it), and only works in regions where nuclear plants actually exist.
If you buy a 1 GWh block of wind/solar energy for a month, you're not doing anything to supply clean energy when it's dark and the wind isn't blowing.
"24/7 carbon free" means increasing the time resolution from 1 month to 1 hour, and funding projects that deliver clean energy when you're actually using it. This includes stuff like batteries, nuclear, and geothermal.
Thanks to AI, it could be: https://g.co/gemini/share/3e1cb15c52aa
It would be challenging for Google to argue that the app should be banned entirely, as it's basically a web browser with extra APIs, like TCP/UDP sockets.
A user would install the runtime, signed by a developer who shared their government ID with Google, and then use the runtime to launch whatever app they want. It's probably infeasible to launch an APK from another APK, so the runtime could be based on WASIX+WebView or something.
We could call it "General Computation". Google could start a cat and mouse game of banning developers who sign the app, but at least this "war on general computation" would be obvious and ironic.
100 kW, in sensible units.
They're not entirely wrong. A/C is often installed without adequate ventilation, and elevated indoor CO₂ levels are not great for your well-being. HRV (heat recovery ventilation) solves the problem, but it's currently a niche technology compared to mini splits.
GitHub has been ignoring customers' desire for IPv6 support for years[0], whereas Microsoft got IPv6 running on Windows NT 4.0 in 1998[1], so there might be a silver lining here.
[0] https://github.com/orgs/community/discussions/10539 [1] https://www.oreilly.com/library/view/ipv6-essentials/0596001...
- Foreground services used to require a persistent notification, now they're not allowed to have a notification unless you prompt the user. So I added a button to beg for POST_NOTIFICATIONS permission, but now permission can be granted after the service starts, so I had to build some magic to make the service refresh its own notification.
- Gesture navigation steals user input when swiping on the left/right edges of the screen, so I had to build some magic to automatically make my UI narrower when gesture navigation is enabled. Drawing apps can't really use setSystemGestureExclusionRects() because it's limited to 200dp.
- By default, apps now render edge-to-edge vertically, behind the semi-transparent status bar and bottom navigation buttons, so I had to build some magic to avoid those areas.
Now that gesture navigation is the default, many developers aren't testing with 3-button navigation, so I've noticed apps where I can't interact with the bottom because it collides with my navigation buttons.
Do you know the shelf life of TRISO fuel? I imagine it doesn't matter because it would be very expensive to build a reactor and not switch it on.