I don’t follow this stuff at all, so I have no idea what the advantages are of Wayland that I’d actually see and benefit from in my daily use. That being said, I saw everyone saying it’s better, so I tried switching to it. After rebooting, my PC just showed a black screen. I needed to use a TTY to revert back to xorg. So no, as of right now I’m not using Wayland.
I just checked the macOS / FreeBSD man page for ‘stat’, and noticed the syntax differs from the version in GNU coreutils (which is what’s used in Linux). That’s probably the only thing that would need to be changed to make the script work on those other systems. It’s on line 526.
Fair enough. But macOS has more users than Linux, and is partly based on FreeBSD. The shell and the userland tools are from FreeBSD. I prefer Linux of course and haven’t used a Mac in years, but I still think it’s nice making scripts compatible with all *nix systems.
For sure. If you get something for free then it is what it is. Some of my scripts probably won’t work outside of Linux but I still make an effort to not use external commands if there’s no need to. I try to use the internal features of Bash as much as possible, mostly cause it’s just faster that way. A consequence of that is that the scripts are at least more likely to work on other systems (that have Bash).
Backend code, basically what is ran on the server and manages user requests, database interactions, etc… Frontend is the user end, so managing input, displaying information from server requests, etc. and is in the form of an app or website page.
As a network guy…open up your favorite web-managed application and open the developer console. Inspect the transactions you see and compare it to the applications REST API reference, and you’ll likely find a lot of commonality (and maybe some undocumented endpoints!).
Backend made the API and everything that is performed by it. Front end is doing the GUI based off the response and promoting for input.
Thank you! I’m happy if more people besides just myself have use for it. It’s a niche some people might not be aware of. Especially for younger people who aren’t familiar with the CD format, and how music is stored in those games. It might help people get more direct access to the OST of their favorite retro games. Instead of having to search around the web for high quality audio, they can just extract it themselves.
I ask because that repo says “The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” and yet it exists only to abuse other people’s creative rights.
Another thing to think about is that CD is a dying format, and the way those old CD-based games are going to be preserved long-term is in the form of disc images stored on HDDs.
I’m sure the artists behind the music for the 20+ year old games this could be used for are really feeling the pain of their creative rights being abused from people trying to still enjoy their art after all this time, you wet blanket.
I am not sure this script will help. But I actually have a lot of cue/bin files from back when I ripped my cd collection. If I remember correctly, I played them through mediamonkey (ape files) or foobar. Windows user then… Most CD’s are either lost or in the back of the attic somewhere. I consider the files dead, but havent deleted them yet. I use plex which can’t play cue/bin files. This script might make my old cd collection come alive again…
If they are CUE/BIN files the script will be able to handle them all without a problem. My advice is to use the ‘-flac’ argument when running the script, so you get lossless copies. But you should double-check the resulting CUE sheet, after processing each album. See if any of the pregaps are longer than a few seconds, cause in rare cases there’s hidden bonus tracks in the pregaps. If that’s the case, you can extract the pregaps separately with the ‘-pregaps’ argument. Good luck!
Wake me up when there’s a working, native non-wsl waypipe client with sound for windows and android, that can hand off applications seamlessly to other hosts. (Think two computers, two monitors that feel like one).
Also working screensaver and monitor power options
My first experience in wayland, us discovering I couldn’t control monitor sleep/standby function. I found how to reinstall X and managed to escape it since.
That sounds like problem with specific software configuration, like missing packages in some distro or something being badly built. There’s nothing about Wayland that would prevent it from working.
Wayland is not a standalone server like Xorg and it doesn’t have standard utilities to control stuff like DPMS. That functionality goes to compositors that are effectively individual Wayland server implementations. Compositors can provide utilities to control display, and they usually do. For example, on KDE Wayland you can call kscreen-doctor --dpms off, wlroots compositors (Sway, Wayfire, Hyprland,…) have inter-compatible tools, like swaymsg output DP-1 dpms off. If that’s what you meant anyway.
There really should be a front end script that has uniform command line parameters, finds what your compositor is, translate the command line arguments and send them.
I dont know what that means. Normally the monitor turns off when the PC stops sending a signal. In KDE i can easily configure when to dim, turn off, lock etc. the screen.
I was the one that came default with ubuntu 22.10 But as I have stated in my initial post, the feature had been restored by reinstalling Xwindow Also, I feel that the commands equivalent to
<span style="color:#323232;">xset dpms force off
</span><span style="color:#323232;">xset dpms force standby
</span><span style="color:#323232;">xset dpms force suspend
</span>
Should be the same regardless which wayland variant you are using.
They dont need to, a Desktop could just use another compositor and the rest of the stuff but they often dont. wlroots is a project doing some general work, but most of the others dont.
lemmy.ml
Top