Wow, that looks stunning! I am no where near skilled enough to be able to even begin wrapping my head around making a compositor, even with a library - but I do know that like the other commenter mentioned we certainly need more libraries aside from the two that we currently have (but I understand why that’s a very tall order) so major props to you!
Thanks, maybe you could follow the tutorial if you are interested. And I wouldn’t mind answering doubts; that actually would help me improve the docs ;)
You mentioned it being easier then wlroots, but wayfire and phoc reportedly act as high level abstractions on top of wlroots that could be used to make it easier to create window managers (wayfire author explicitly mentioned it), Maybe it will be good to create a comparison with these projects? or even divert your future efforts to one of them?
I’m not sure if I explicitly mentioned that it’s easier than wlroots, but I believe its design can considerably ease the learning curve for newcomers. While I’ve read about those projects, I haven’t had the chance to try them myself. Although I’d be interested in contributing to their development, I don’t intend to abandon Louvre. I find it beneficial that there are different alternatives, as each can bring unique and clever ideas to enhance various aspects, ultimately improving the overall design across the board.
Title bullshit, we have multicore machine for years, I can guarantee you this had about no impact else people running Xeon or Threadripper would have saw it at first try 15 years ago.
This looks like to have an impact on the scheduler but not on how many cores are used.
I agree. Some of the Linux servers I used to run at work in the early 00’s were 12 to 16 core monsters (for the time) and the kernel didn’t even blink.
We used to run firewalls running Fedora at work, works fine. Issue is you’re only getting 6 months of updates, best to look at Rocky Linux for something that doesn’t change much if you do anything beyond a single program.
anedotally: it works fine if it’s from a vendor who provides support for it. eg cumulus switches running fedora 9 but still getting updates from cumulus engineers.
The main differences between distros boil down to:
init system
default configurations and applications
release cycle
package manager
Most end users don’t mess around too much with their init system and software configuration. With the rise of mainstream distros and application developers opting to ship desktop applications as snaps/flatpak/appimages, the last two points have less importance than ever.
IMHO, considering this, most of the discussions surrounding distros is relatively silly. After using Linux for almost 20 years at this point, I think I can safely say I could be productive on most popular distributions, with minor adjustments to my workflow.
For a new user? Just pick one of the main distros, that supports the software you need, and roll with it for a while. It won’t make much of a difference. Distro hopping doesn’t make one learn much outside using a different package manager.
Base os install ad a template in your hypervisor. Ansible playbook with a task to spin up the VM, another task to setup network and required packages. Then other playbooks for the software/services setup.
I sounds like you have to apply new cooling paste. This might be a pain to do on a laptop but certainly worth it. Another distro probably won’t do the trick, whether it’s minimal or not.
Is it still maintained ? I’d probably go with FreeBSD if I’m switching to BSD at all. It has ZFS out of the box and has support for nvidia’s non opensource driver. I have used it as a desktop OS for a good 3 months, it was pretty good (even though I couldn’t game on it)
In what kind of world is a missing feature or a broken feautre due to incomplete migration to a new ecosystem, a reason to boycott that new ecosystem?? Those are simply not valid arguments to me.
They are obviously valid arguments to say, hey, this work is not completed, is not mature enough etc. So, therefore, you stay with previous ecosystem. But to boycott it because of that? That does not make sense to me at all.
Part of the problem extended beyond software. Back when I got into recording, FireWire was necessary for the data bandwidth and it was standard on Macs. I had to install a card to work with my recording interface on Windows.
On a side note, been using Reaper for years and it has been great as a hobbyist option. I understand why any professional would use something like ProTools instead, though.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.