fxdave

Hopefully, but it's easier to tell each company what they should do instead of giving them rules that they try to workaround. There are many examples.

From the list, openscad requires the least tutorial. Solvespace is really easy also, but you need to watch some exciting modelling videos before you get the idea around it. Blender is hard.

OpenScad also gives you a different modelling experience that lets you write reusable models, e.g. if you are a carpenter, 90% of your modelling is sizing and positioning fiberboards to shape a box. You can "automate" such tasks, easily. I wrote a script for myself that does that, and I'm now super fast at modelling furnitures. After some modelling you will be also capable of making such lib. (As a developer, I might be biased)

If you are interested in this library: https://github.com/fxdave/woodworkers-lib

Try solvespace or openscad or blender depending on your use-case.

afaik, fedora is the testing distro for RHEL. I also felt this way, when a new gnome version released much earlier than for Arch and it had an obvious bug that could be catched with little testing.

And many issues I found in Fedora's bug tracker was auto closed by the new release. Which is quite frequent. Reviewing the bugs is not that frequent.

That's also why I always use dev containers

You may see shorts in lemmy in the near future because of that.

Slack calls disabled for firefox users, but if you change the user agent to chrome it works...

well, yes, but for e.g. I wrote a software piece that happened to be only a hotkey daemon. And I could write it with X. Now, hotkey daemons are no longer a separate thing unless the compositor exposes a grab API. Which never going to be in Wayland protocol, because they consider this client server architecture a problem.

There's hope. Thanks for letting me know.

Now instead of having Wayland covering everything, applications try to cover every desktops. In the good old times, it worked everywhere.

Why does flameshot need to handle different wayland desktops separately? Because simply the protocol doesn't do it's job. It doesn't cover everything. It's indeed not ready.

I think it kills the community. Making a Wayland window manager is so much harder to do than an X one. This monolithic solution solves the problems of Gnome, and KDE developers but less people want to be involved in windowing systems. I'm just being sad for X11, because, although it had nonsense features, it made linux desktop applications compatible with every desktop and we had huge variety of wms, compositors, desktop environments. Personally I'm still on X because of bspwm, but eventually there will be wayland-only features which will slowly kill X.

there are products that I would buy if I would know they exist but I don't because they don't have enough money to do advertisment. It's inherently an unfair competition. The only ads that I would like to see is a tematical search for all of the buyable products and services.