// Only one cleanup task is posted at a time.
if (!HasDirtyJSFinalizationRegistries() || is_finalization_registry_cleanup_task_posted_) {
return;
}
I was frankly impressed by the experience. They had me create a minimal extension illustrating the issue and were very quickly able automate a bisection that found its root, a security fix somewhat bluntly resolved. They've supposedly fixed the issue in an upcoming release I await with bated breath.
- [1] https://issues.chromium.org/issues/405283740
- [2] https://chromewebstore.google.com/detail/tabasco-advanced-ta...
>Avoid where possible
>Correct use of FinalizationRegistry takes careful thought, and it's best avoided if possible. It's also important to avoid relying on any specific behaviors not guaranteed by the specification. When, how, and whether garbage collection occurs is down to the implementation of any given JavaScript engine. Any behavior you observe in one engine may be different in another engine, in another version of the same engine, or even in a slightly different situation with the same version of the same engine. Garbage collection is a hard problem that JavaScript engine implementers are constantly refining and improving their solutions to.
Kinda tricky API
Really looking forward to the "Explicit Resource Management" proposal[0] that sounds like a much better idea really.
[0]: https://github.com/tc39/proposal-explicit-resource-managemen...
I think WASM had historically had some problem with freeing memory, so I'd probably rather rely on some pooling or arena with explicit memory size limit (for the whole allocated wasm memory).
rvz•11mo ago
> At Monumental we’ve building robots to automate construction, starting with masonry.
If you thought running to construction jobs was safe, well thanks to Monumental, it soon won't be.
The end goal is to achieve a 10% increase of global unemployment by the latest 2035 and 40% of employers anticipate reducing their workforce where AI can automate tasks by the 2030 deadline according to the WEF 2025 Future of Jobs report. [0]
Worse if earlier.
[0] https://www.weforum.org/publications/the-future-of-jobs-repo...
TheDong•11mo ago
We've already managed to handle the desire to keep the sham of "jobs are a necessary part of life for everyone who isn't ultra-wealthy" going via Bullshit Jobs, we can keep inventing more Bullshit Jobs.
Heck, we probably both work Bullshit Jobs. Do we really need 20 different companies, all with thousands of employees, optimizing ad-impressions to make teenagers want to drink coke and buy nike shoes?
Do we really need 10 different "uber for pet-sitting your turtle" apps?
Each failed startup was, in reality, a large bag of bullshit jobs that transferred money from the VCs to bullshit-job workers, who's to say those people couldn't be ex construction workers?
Cthulhu_•11mo ago
The demand for housing and thus construction workers isn't going down any time soon; the Netherlands alone needs to build a million homes in the next decade and are running behind on that. Brick walls is just one task of many in a construction project, just like your JIRA or Github ticket is just one task of many in a software project.
bouk•11mo ago
There's a huge shortage of workers, which is why we're working on this.
pjmlp•11mo ago
We are really going into a dystopian world, unless there is some event that disrupts the roadmap to drive everyone into unemployment, besides a few elite folks that get to profit from the robots.
The generations to come will have much more to worry about than climate, also note how all the ongoing wars, geopolitcs change back to cold war days, and AI race has made everyone forget about the planet.
Forcing us to use paper straws and wood cuttlery won't save us.