Conversation
Jarkko Sakkinen
jarkko
Edited 10 months ago
In my work (or more like home office) desktop I started to use #sway (#i3 #wayland replica). Works for that really well, would not put it to my casual/studio desktop tho (which is mac mini anyway). i.e. you can use it make your console like you had your power plant or something :-) my friend tuomo.wrote the original #ion3 window manager, which influenced this and few others back in the day.
more direct ion3 derivative also continues to live on as https://notionwm.net/ and i've heard that there is also wayland replica of this.
more direct ion3 derivative also continues to live on as https://notionwm.net/ and i've heard that there is also wayland replica of this.
3
0
5
this is more like workflow optimization than being geeky :-) pretty much same tools every single day and probably many years to come and dedicated computer for work.... also it is nice that if you ramp up a new system i can also deploy my desktop configuration along with other dotfiles fast.
1
0
0
I like to have also one Mac at home. It is pretty good for comparative testing e.g. with syscalls and also compiling ARM kernels (and testing them without having to use SBC's). To add, I don't want to focus on configuration when I make music and Linux is anyway my construction site. Nobody wants to spend 247 at work I guess :-)
I even had one Windows machine at some point but it required more maintaining than my other machines, NAS, network router etc. added together so I gave up on that... And Windows has also worst audio stack of the industry: the native one is pure garbage so there is proprietary ASIO stack that everyone uses from Steinberg, which results a trainwreck system overally.
Why people say that Linux audio sucks had nothing to do with kernel, it was just that low-latency audio was not well supported up until the uncrowned genius of multimedia Wim Taymans fixed the issue with Pipewire. Today in kernel/middleware level has hands down the best audio stack that there exists. I mean even in macOS you have to install 3rd party proprietary product called Loopback to be able to route audio like you can do with Pipewire.
I even had one Windows machine at some point but it required more maintaining than my other machines, NAS, network router etc. added together so I gave up on that... And Windows has also worst audio stack of the industry: the native one is pure garbage so there is proprietary ASIO stack that everyone uses from Steinberg, which results a trainwreck system overally.
Why people say that Linux audio sucks had nothing to do with kernel, it was just that low-latency audio was not well supported up until the uncrowned genius of multimedia Wim Taymans fixed the issue with Pipewire. Today in kernel/middleware level has hands down the best audio stack that there exists. I mean even in macOS you have to install 3rd party proprietary product called Loopback to be able to route audio like you can do with Pipewire.
0
0
1
