![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/5170ed37-415d-42be-a3e7-3edd79eda681.png)
Though, not the same thing. I really like the Dutch implementation for their old maps: https://topotijdreis.nl
Though, not the same thing. I really like the Dutch implementation for their old maps: https://topotijdreis.nl
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.
My neighbour is. I hear the boot sound about once a week. No idea what he’s using it for, but I hope it’s not connected to his network.
Been running Wayland for 5 years on my development laptop (sway, Intel GPU, blacklisted the nvidia gpu). At the start I’ve had a couple of issues, nothing too bad. Haven’t had any issues for over 2 years. Switched to Linux on my gaming PC about a year ago, KDE plasma on Wayland but do most of my gaming from a steam gamescope session. Very happy overall with Wayland, glad it exists. Sharp text on a fractionally scaled display for reading code was just too compelling at the time and it only improved.
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.
Lemmy
First! And I actually did quite poor…
I thought this was a pretty good in-depth explanation of the infinite case and the finite case: https://www.youtube.com/watch?v=zTsRGQj6VT4
Maybe Firefox, Thunderbird or Steam are running in XWayland and that causes different behaviour between them. Just guessing.
You might share a split brain with me. I had this exact thought, but decided to leave it out of my comment.
Can recommend the video from cgpgrey on it to anyone: https://www.youtube.com/watch?v=wfYbgdo8e-8
I wonder if internally the emoji’s are added through a different mechanism that doesn’t pick up the original request. E.g. another LLM thread that has the instruction “Is this apologetic? If it is, answer with exactly one emoji.” After this emoji has been forcefully added, the LLM thread that got the original request is trying to reason why the emoji would be there, resulting in more apologies and trolling behaviour.
Can’t really blame him for not knowing an alternative without providing an alternative.
Just thinking. Maybe there’s a non linear relation between the uptake and the amount of alcohol. As for other products, they usually have a nutritional information table per 100g that you can thus read as percentages.
I think the argument is pretty solid as an alternative to writing PKGBUILDs yourself. Sure it doesn’t hold up for people unfamiliar, but Arch is build on the idea of getting yourself familiar with it.
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.
As an alternative approach you can look into ansible. As opposed to making a system backup you can define your system configuration as code that you can redeploy with it.
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.