27,471 karma · joined December 24, 2015
Recylable is important because it means we don't have to mine as much.
So nobody's even started on it except Chrome.
I can't comment on the cost of Gas Turbines.
My repos probably don't see as much traffic as SQLAlchemy though.
I don't
> Where I live isn't relevant,
But where you live does matter. Average monthly household energy usage in the EU is 200-400 kWh. In the US it's more like 800-900kWh. So what you consider "normal energy usage" may vary considerably by where you live.
At 200-400kWh total usage, 30kwh starts to look a lot more significant. So you should at least consider the possibility that it's not that energy usage from AI is insignificant, but that your existing energy usage is wasteful.
At the very least they ought to consider doing a macOS-based server chip. Given how many providers are racking Mac Minis these days. It's mostly for CI testing for code deployed to Apple platforms, so it very much supports their business.
Linking is normally slower in debug btw (because of the debug info)
FWIW:
- Binary sizes start around 8mb if you're using GPU rendering (you can go smaller with CPU rendering, but you probably want the GPU). Our full browser app which pulls in things like sqlite, http cache libraries, etc is 20mb. Those usually compress to about half for distribution (.dmg, .appimage, etc).
- Base memory usage is something like 100mb (mostly from the graphics stack). I'm hoping to be able to bring that down a bit, but I think you can't realistically get much lower than 60mb with modern graphics. And to be perfectly honest we currently have an issue for RAM where it will often jump to more like 300-400mb after a little use. And I haven't fully gotten to the bottom of that yet.
So far it's only HTML/CSS (and we have our Rust-based framework to write the apps in). But it has been designed for fast incremental rendering, so it could be extended with JavaScript support quite easily.
And from what I read in the media, a lot of the economic indicators are backing this up: discretionary spending is down, private debt levels are rising, etc. All signs that the slack in the system is disappearing.
That's true. But will anyone have any money to pay for the LLMs? The AI market is currently being heavily subsidised by, ultimately, everyone else. But the economy in general is looking extremely dire at the moment, and that seems unlikely to last.
- It's implemented in a non-backwards-compatible way
- The benefits over the older model are a bit nebulous
- There's a large amount of tooling that needs to catch up, and little sign that there is movement there
> Another thing that can easily improve performance is changing the global allocator, but I've seen teams that measured 10% perf improvements in their own metrics decide against going with anything other than the "default".
Yeah, although I think there's more of a trade-off there. Alternative allocators can add significant amounts of compile time. Whereas, modulo maturity, I think a faster linker is more of a pure win. I would imagine we will make wild the default linker at some point if development continues on the trajectory it seems to be on.
Is that still true with modern linkers like `wild`? Seems like it can link Chromium in 1-2s.
> Another thing is that stable rust doesn't treat macros as idempotent
This seems absolutely insane to me given how pervasive macros are in Rust (I wonder how much of incremental compilation time is just repeated serde derives?). Obviously we can't just blindly treat all macros as idempotent, but an opt-in attribute on a macros that pinky-promises that it is seems like it ought to be pretty easy to implement?
Maybe somebody's looked into it and it doesn't help much? But I've heard (unverified) rumours of the opposite.
I feel like this is likely going to be a non-issue in practice. Because these batteries are rated to last at least 10 years either way. And by that time, the cost of replacement will be dramatically cheaper.
> And having AI code to review is no different than any other code that ever was to review
If your company is sticking to "everything needs (human) review" then you wont run into most of this. This issue is that a lot of companies are using AI as an excuse to remove that review process (either partially or entirely).
You're typically better off looking for some kind quick/fast mode. Or even the "regular" mode.
(YMMV, look things up for your specific model)