Note that this wouldn't have been useful for Factorio, because Factorio deals with the harder problem of needing deterministic results with varying amount of parallelism, whereas from what I understand Dthread only give the same results if you run the program with the same number of "threads".
During winter, France uses ~50% more electricity per day than during summer.
And during cloudy days in winter, solar produces 10%-15% what it produces during summer.
If you don't have month-long battery storage, in order to be fully solar based France would need to produce 20 times more electricity than needed during summer.
> And during cloudy days in winter, solar produces 10%-15% what it produces during summer.
This doesn't matter. If you look at the monthly stats, solar panels in France produce ~3x more in the summer than the winter at a month by month view. As such, you only need 3x extra overall, and some day to day storage.
Or you use a different technology optimized for long term storage. Batteries are not that technology. Hydrogen (or other e-fuels) or long term thermal storage.
> Or you use a different technology optimized for long term storage. Batteries are not that technology
I've heard this before but can you explain why? A cursory web search tells me batteries hold charge pretty well for 6 months. And the new sodium batteries from CATL are certainly cheap enough.
For long term storage, capex is king, not round trip efficiency. The capex of batteries ($ per kWh of storage) is much too high. There aren't enough charge/discharge cycles to amortize that capex. This is unlike with diurnal storage, where there are many thousands of cycles over which to spread that cost.
To go into more detail: you want to really aggressively minimize capex, even at the expense of round trip efficiency, for long duration (like, seasonal) storage. The interesting example from Standard Thermal is something that could reach a capex of $0.10 per kWh-th of storage capacity (yielding heat at 600 C). This is three orders of magnitude better than batteries. Even tossing in 40% round trip efficiency from converting this back to electricity using steam turbines it would be vastly superior to batteries for seasonal grid storage.
There are varieties of batteries with somewhat lower capex and lower charge/discharge rates. Form Energy's iron batteries are of this kind. They would occupy an intermediate timescale, perhaps ~1 week, which could be good for leveling wind output.
I think that the laws of physics dictate that there is. If your developers are spawning the galaxy, the speed of development is slower with continuous development than with pinning deps.
We don't know the laws of physics though. We just have models which can both fit into human brain to a point that they are surprisingly good for what humans have an opportunity to experiment agaisnt. That is really awesome, but it doesn't mean we know.
As it stands, we already have a high-performance, sandboxed VM that we are maintaining successfully, and our editor environment is decidedly _not_ multilingual for historical reasons/lack of investment. It'd be very, very expensive for us to see any of the advantages of wasm for the platform today, and it wouldn't really do anything about our existing need to support the millions of lines of code written in Luau today.
Also strategically, wasm is a massive project coordinated by a large number of companies, and it doesn't seem especially prudent to bet the success of a single multibillion dollar company and their entire platform on a project that they don't control the destiny of.
Agreed. I think an underappreciated aspect of choosing a script VM in the space Roblox is in (user-generated content where scripts are content) your product is at the mercy of whoever controls your scripting implementation.
The scripting engine is an integral part of your product, and you need to "own" it end-to-end. Any bugs that creep into new versions of your scripting engine, any API breakage or design changes that impact your usecase are things that you are responsible for. Roblox owns the entire toolchain for Luau, and it's relatively small compared to the set of libraries required to compile to and execute WASM in a performant way.
The nuances of your typical JITing WASM runtime or V8 are pretty hard to learn compared to a simpler VM like Luau, it's a big reason why I've used Luau in my own projects.
Which ML-based products?
> It was convenient for Google that OpenAI acted as a first mover
That sounds like something execs would say to fend of critics. "We are #2 in AI, and that's all part of the plan"
reply