![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
This is a pretty interesting counter example: https://www.eteknix.com/running-yuzu-on-switch-gives-you-better-performance-than-native-gaming/
But, as others have said, exceptions confirm the rule.
This is a pretty interesting counter example: https://www.eteknix.com/running-yuzu-on-switch-gives-you-better-performance-than-native-gaming/
But, as others have said, exceptions confirm the rule.
This isn’t a desktop app, but the editor seems quite solid: GrapesJS
Thanks, that was an interesting read! I always felt IPFS wasn’t ready yet, but the value it tries to provide of being a file system, I’ve found no real alternative to. Very good to read that iroh is willing to look beyond the IPFS spec to provide its values with better performance. I hope it works out.
Ever heard of IPFS? I really hope that will take off some time.
I’d say a battery is at least something that should be “chargeable”, either one time or rechargeable. I dont think you can use solar cells to store energy back into the sun.
Not saying that my definition does work for the dirt fuel cell, talked about in the article, though.
Maybe Firefox, Thunderbird or Steam are running in XWayland and that causes different behaviour between them. Just guessing.
Explained by someone that doesn’t know the technical side super well.
1: It’s a new protocol for displaying. The main difference from X11, as I understand it, is a simplification of the stack. Eliminating the need for a display server, or merging the display server and compositor.
2: Some things impossible (or difficult) with X11 are much better supported in Wayland. Their not necessarily available, as the Wayland protocol is quite generic and needs additional protocols for further negotiation. Examples are fractional scaling & multiple displays with differing refresh rates.
Security is also improved. X11 did not make some security considerations (as it is quite old, maybe justifiably so). In X11 it’s possible for any application to “look” at the entire display. In Wayland they receive a specific section that they can draw into and use. (This has the side-effect of complicating stuff like redshifting the screen at night, but in my experience that has fully caught up).
3: If you’re interested, are in desktop application development (but I have no experience in that regard) or have a specific need for Wayland.
4: I think X won’t die for a long long time if “ever”. I’m not super familiar with desktop app development, but I don’t think it requires more work to keep supporting X.
On the other hand, most of the complaints about Wayland I’ve heard were ultimately about support. At some point, when you’re a normal user, the distro maintainer should be able to decide to move to Wayland without you noticing, apart from the blurriness being gone with fractional scaling.
Seems like they at least could’ve made the page have a no-cache header so you don’t have to wipe the cache & history by hand.
Here’s why
Human rights
Alternatively: Hauk
(No idea how they compare)
It’s been a while since I’ve watched it myself, but remember them going into the ownership structure.
https://www.youtube.com/watch?v=hNZy603as5w
There’s basically no way for them to not make it a subscription model.