- cross-posted to:
- phoronix@lemmy.world
- cross-posted to:
- phoronix@lemmy.world
You must log in or register to comment.
So… there will be Alphas 5 and 6. And we got Alpha 4 a week late, compared to the old release schedule of the last Thursday of every month. And a lot of the things that were meant for Alphas 3 and 4 were pushed back. I hope that System76 doesn’t encounter more features that push things back further (the way VRR seems to have done), for their own sake. That way, they can keep up a lot of hype around the Betas and the release of Epoch 1.
And we got Alpha 4 a week late, compared to the old release schedule of the last Thursday of every month
i bet most likely due to the US holiday. 28/11 and 29/11 were the Thanksgiving and Black Friday holiday in US
Ngl this Desktop might make me use Popos and even outside Popos it looks nice,Idk about X Fallback. support (Since i play Beamng Which does not run on Nvidia Wayland And i cannot figure out a way to fix it),And i wanna see peoples opinion on it or if people will care anymore.
Variable refresh rate (VRR) allows your display to match the framerate of an image source, such as a game — and doing so prevents screen tearing. Support for VRR has been added to the cosmic-comp compositor and Displays Settings. You can set VRR to be either always on or automatic, which will enable VRR for fullscreen content.
memory leak fixes,
But muh Rust??
Rust doesn’t prevent memory leaks. You can do that in every language
Thought the whole point was that it forced you to handle memory properly and automatically released things when they go out of scope
What kind of situation can cause a memory leak in rust
You can have a memory leak when items are still in scope in some loop or when you have a reference count cycle. The latter happens with the Rc/Arc types in rust.
An example for the former can be a web server that keeps track of every request it’s ever received in memory. You will eventually run out of memory. But you did not violate any memory rules (dangling pointer, etc.). Memory leaks can be caused by design issues.
That doesn’t fit the definition of memory leak in my mind, had thought a memory leak was specifically when the program completely loses track of memory
That’s one kind, and Rust’s “ownership” concept does mean there’s built-in compile time checks to prevent dangling pointers or unreachable memory. But there’s also just never de-allocating stuff you allocated even though it’s still reachable. Like you could just make a loop that allocates memory and never stops and that’s a memory leak, or more generally a “resource leak”, if you prefer.
Rust is really good at keeping you from having a reference to something that you think is valid but it turns out it got mutated way down in some class hierarchy and now it’s dead, so you have a null pointer or you double free, or whatever. But it can’t stop the case where your code is technically valid but the resource leak is caused by bad “logic” in your design, if that makes sense.
