Welp...
-
Welp... in researching & testing my way towards #Linux, one of the first things I've discovered is that "[Thing] is available for Linux" is nonsense.
There's no such thing as "Available for Linux".
There's "Available for some Linux'es & if you're lucky & willing to work hard for it, yours may be one of them".
Not sure I'm complaining, exactly; I understand why this is the case - but it sure as shit doesn't make the decision to actually switch any easier...
-
Welp... in researching & testing my way towards #Linux, one of the first things I've discovered is that "[Thing] is available for Linux" is nonsense.
There's no such thing as "Available for Linux".
There's "Available for some Linux'es & if you're lucky & willing to work hard for it, yours may be one of them".
Not sure I'm complaining, exactly; I understand why this is the case - but it sure as shit doesn't make the decision to actually switch any easier...
@jwcph Sometimes, if the developer is stuck in the past, they will put out packages that are tied to one distribution these are typically .deb or .rpm packages
However, Flatpaks and AppImages will work across all distributions, because they are self-contained and carry all dependencies in one package (sort of like .dmg-files on Mac)
-
Welp... in researching & testing my way towards #Linux, one of the first things I've discovered is that "[Thing] is available for Linux" is nonsense.
There's no such thing as "Available for Linux".
There's "Available for some Linux'es & if you're lucky & willing to work hard for it, yours may be one of them".
Not sure I'm complaining, exactly; I understand why this is the case - but it sure as shit doesn't make the decision to actually switch any easier...
@jwcph indeed, sometimes installing things can be very frustrating trying to get it to work on your system. It does get easier to recognize what type of software will be harder than others to get working. +1 to the flatpak and appimage recommendation. Those generally "just work". If your having struggle with anything in particular, feel free to reach out
-
Welp... in researching & testing my way towards #Linux, one of the first things I've discovered is that "[Thing] is available for Linux" is nonsense.
There's no such thing as "Available for Linux".
There's "Available for some Linux'es & if you're lucky & willing to work hard for it, yours may be one of them".
Not sure I'm complaining, exactly; I understand why this is the case - but it sure as shit doesn't make the decision to actually switch any easier...
@jwcph
It sounds like you are taking the wrong approach.
You should be thinking in terms of function required rather than 'thing'. -
@jwcph
It sounds like you are taking the wrong approach.
You should be thinking in terms of function required rather than 'thing'.@anarchotaoist What do you think "thing" means...?
-
@jwcph indeed, sometimes installing things can be very frustrating trying to get it to work on your system. It does get easier to recognize what type of software will be harder than others to get working. +1 to the flatpak and appimage recommendation. Those generally "just work". If your having struggle with anything in particular, feel free to reach out
@Shirley @simonjust Sure - but what this means in pratical terms is, you go to the homepage of some thing you need & it says "Avaliable for Linux" you may find that it isn't available for *your* Linux - or, as I've already had happen more than once, it's available, but not through the app manager provided with your system for some reason...
(I do have a specific struggle but it's only tangentially related to this; turns out getting Win VSTs into Fedora is particularly problematic
) -
@Shirley @simonjust Sure - but what this means in pratical terms is, you go to the homepage of some thing you need & it says "Avaliable for Linux" you may find that it isn't available for *your* Linux - or, as I've already had happen more than once, it's available, but not through the app manager provided with your system for some reason...
(I do have a specific struggle but it's only tangentially related to this; turns out getting Win VSTs into Fedora is particularly problematic
)@jwcph @simonjust ugh yeah, doing audio production? I gave up on the vst route and tried to find lv2 plugin alternatives to the vsts. So far so good, but I wish I had more drum sampler options.
-
@jwcph @simonjust ugh yeah, doing audio production? I gave up on the vst route and tried to find lv2 plugin alternatives to the vsts. So far so good, but I wish I had more drum sampler options.
@Shirley @simonjust Yeah, going Linux-native plugins only is a dealbreaker for me - there are some key ones I use (and also paid good money for) that I simply don't want to do without, which don't come in Linux versions & almost certainly never will.
-
@Shirley @simonjust Yeah, going Linux-native plugins only is a dealbreaker for me - there are some key ones I use (and also paid good money for) that I simply don't want to do without, which don't come in Linux versions & almost certainly never will.
@Shirley @simonjust - but that's kinda one of those "Not for your Linux" things; everybody says to use Wine & Yabridge & while I'm sure you can probably force/kludge those things onto Fedora (my main candidate for now), they aren't "available" using the normal tools of that system.
- and then comes the problem that if you coax things manually until they work, maintaining them is also now your own, manual job & it's probably going to get increasingly difficult over time...
