awesome-wayland VS semver

Yup. Here is an example list of things you can swap around. https://github.com/natpen/awesome-wayland

You didn't say whether your current config is based on X or Wayland therefore two links with Wayland applications. Are we Wsyland yet and awesome wayland

plenty others of all sorts.

> auto keyboard/mouse scripting with xdotool

There's a few tools for this: https://github.com/natpen/awesome-wayland#tools

> not have unnecessary mouse/keyboard to monitor delay

There's none that I can notice. Mice cursor are rendered with hardware support

Here's one of many forks of an awesome-wayland repository that lists what's going on: https://github.com/natpen/awesome-wayland

customization isn't killed, it just takes time to adapt to a new protocol. check out all the stuff you can do with wayland

More specifically, see: awesome-wayland and arewewaylandyet. Sway-addons also has interesting stuff in it, like wl-clipboard which is mostly compatible with Klipper.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: