Blender was crossplatform way before any major corporations took interest in it.
3 weeks ago
Anonymous
obviously, doesn't matter there weren't paid devs working on it full-time
3 weeks ago
Anonymous
my point being if a bunch of hobbyists can do crossplatform development fine in their spare time. so could a mid sized company like Affinity.
maybe "it doesn't make financial sense" but they really don't have anything to lose.
3 weeks ago
Anonymous
I mean im sure there is like an autistic developer or two in their company that would be more than happy to spend their time writing a Linux backend. and they only have to do it once.
3 weeks ago
Anonymous
i think you're underestimating the incompetence of an average programmer
also there's a stigma with linux so nobody wants to touch it but it shouldn't be problematic at all if done right
3 weeks ago
Anonymous
>there's a stigma with linux
ehh... normal people don't ever know what linux is, the stigma is probably from Wangblows users that used linux once like a decade ago and hated it.
I really doubt if they mentioned that they have a Linux version on their website that 99% of their users would even care. it might piss off a geeky wintoddler or two.
they're both good enough. >If they can't get that to work, they're idiots and their app isn't worth your time.
honestly whats their excuse? just target X11 and package your own glibc and pack it. I swear a 12 year old that just wrote their first hello world program could do it.
AppImage is okay, but when it doesn't work you're fucked, and it happens on occasion.
I dunno how you can fuck up Flatpak though, even some commercial products like Bitwig are available through it.
>If they can't get that to work
They can, but would be a waste of money, resources, etc, because there's no profit.
They're just being 'polite' about it.
because the devs are retarded. just statically link glibc and all your needed deps. >doesn't work on my distro
then stop using it. any distro that doesn't support AppImage/Flatpak out of the box isn't worth using.
It is literally just a few clicks. Bug whoever made your file manager to make it executable by default I don't know. They probably won't for multiple reasons but you can try. it's not the fault of appimage.
A few clicks that add up over time. the less clicks the better.
3 weeks ago
Anonymous
i don't think you can save as executable from browser but i might be wrong
it'd make sense for appimage launcher to be preinstalled and automatically pick up appimage type files
That's not enough, full integration is needed otherwise you wont be able to open files with some programs and you wont see them in app launcher, among other things.
app image doesnt ship all the required libraries, then I need to manually get the libraries compile and pray it was the only one required but not shipped on the app image, but most of the time is just dependency hell
>just statically link glibc and all your needed deps
kek nodev detected.
If you'd worked on any real world linux codebases you would realise how monumental of a task that actually is due to freetard obsession with shared libraries.
how hard can it be? does glibc refuse to compile if you try to statically link it? you could dynamically link it and just keep it in the same directory of your program Windows style.
Static linking glibc is not supported and I think you can't even do it nowadays. Static linking musl on the other hand, now that's the sane choice, and easy to do if you use something like nix.
glibc literally broke compatibility not too long ago
https://www.gamingonlinux.com/2022/08/valve-dev-understandably-not-happy-about-glibc-breaking-easy-anti-cheat-on-linux/
3 weeks ago
Anonymous
Don't use unsupported hacks in your code. This is a basic rule on every platform, Windows, macOS, Linux, etc, it will even get you rejected from app stores.
3 weeks ago
Anonymous
this shouldn't be the concern of the developer thats relying on core system libraries.
core libraries should ideally never break compatibility.
if a feature is a "hack" that needs to be fixed NOBODY cares just keep it. the importance of my binaries working outweight the "need' to fix this "bug". it's a nonissue.
3 weeks ago
Anonymous
>core libraries should ideally never break compatibility
It happens all the time, especially if you're anticheat software digging through internal data structures instead of going through the supported API. I still remember how broken VAC was when Windows 10 released, SteamService.exe would literally take down your machine after a few minutes. >if a feature is a "hack" that needs to be fixed NOBODY cares just keep it
You don't get it, there was no "feature", Epic was digging through data they weren't supposed to dig through. Nothing you need to worry about unless you're developing malware.
3 weeks ago
Anonymous
>It happens all the time
no it happens like once every 2 decades on Windows at most, but it breaks every couple of months or years at most on Linux. >Epic was digging through data they weren't supposed to dig through
mind to elaborate?
3 weeks ago
Anonymous
>no it happens like once every 2 decades on Windows at most, but it breaks every couple of months or years at most on Linux.
You made up these numbers in your head. >mind to elaborate?
They were looking for exported symbols by scanning memory manually instead of using a supported API (like dlsym). Makes sense for anticheat software but don't be surprised when it breaks.
https://maskray.me/blog/2022-08-21-glibc-and-dt-gnu-hash
3 weeks ago
Anonymous
>You made up these numbers in your head.
software from the early 2000s and even sometimes way before still works on windows10/11
try something like Fraps ancient crap that still runs. no way something like that would last this long in binary form on Linux.
3 weeks ago
Anonymous
3 weeks ago
Anonymous
I can run old programs in WINE that no longer work in win10
3 weeks ago
Anonymous
maybe they should fire that homosexual for pretending to be a linux dev.
Linux has a very stable API. You choose libc to be the intermediary layer between Linux and your program.
libc does changes according to the standard. This comes with changes that take 10+ years to be enforced, i.e. the functions to be totally removed from the library.
You can either pick a different library that takes care of those abstractions, i.e. apr library, or you can pick a library like musl and compile against it statically. musl comes also with a cuck license.
Do you know what these fags want?
minimum effort, maximum profit.
>error while loading shared libraries: libreallyold.so.0: cannot open shared object file: No such file or directory
You'll run into problems like that, but yeah glibc is an excellent example of *backwards* compatibility, so
>glibc has maintained ABI compatibility since the FIRST version released for Linux in 1999.
what a load of bullshit. Lintroons are compulsive liars.
>compile a simple tool in ubuntu 22.04 >give to client >client uses 20.04 >fatal error: glibc version too old pls update && upgrade >client uses arch >fatal error: libnagger-4.2.0 not found
>compile the same tool in windows 10 >give to client >client runs tool in windows 11 >client runs tool in windows 7 >client runs tool in windows xp >client runs tool in ubuntu >client runs tool in arch
it's fucking retarded how I get way more reliability running windows software in Wine than I get when running native Linux binaries
Flatpak, retard. You aren't supposed to use distro libraries unless absolutely necessary.
Also, I can guarantee you that if your app isn't a game or made less than a decade ago, running it in Wine will have all sorts of subtle bugs. Don't bother "supporting" it that way.
>don't use the libraries in your OS!
this is unbelievably fucked, this is beyond microsoft levels of fucked, stop coping
3 weeks ago
Anonymous
You are aware that Flatpak is similar to how software is distributed for other OSes, right? Have you ever actually developed anything in your life?
>you need to use flatpak for a 2K LoC command-line utility
And then linuxtards make fun of Electron homosexuals
>command-line utility >being at all useful in Wine
LARP post.
3 weeks ago
Anonymous
yeah, i can compile my EXE for windows and microsoft don't change anything for bullshit reasons no one cares about, so i can count on it working for the next 15 years unless i did something unusual
3 weeks ago
Anonymous
>so i can count on it working for the next 15 years
...until you can't, in which case you are fucked, which happens at least 1/4 of the time because Windows' compat mode is a joke.
Source: have actually had to work with ancient Windows programs.
nagger you don't understand, flatpaks are not intuitive in that way, if you can't do it in a GUI it might as well not exist.
can you locate the flatpak, drag and drop it on a USB stick and give to someone else without touching the CLI? no? then its trash.
Filtered.
3 weeks ago
Anonymous
>Filt..ACK!!
I can do it with the CLI dickhead. but if normies can't do it then it's shit.
3 weeks ago
Anonymous
If you need it to be usable by idiots, why do you even care whether it runs on Linux?
3 weeks ago
Anonymous
both are fucked, but its a hell of a lot easier dealing with 12 year old windows programs than 4 year old linux shit
3 weeks ago
Anonymous
>...until you can't, in which case you are fucked
Then run ancient windows in a VM or use dos box.
Windows is not only the hands down champion for backwards compatibility in desktop apps, it's the only desktop OS that actually makes a genuine effort to preserve backwards compatibility with older software.
Even ancient windows exe tend to work fine unless they are doing something quite unusual.
3 weeks ago
Anonymous
>Then run ancient windows in a VM or use dos box.
lmao >Even ancient windows exe tend to work fine unless they are doing something quite unusual.
They usually ARE doing something unusual. This is not the exception, it's the norm, and maintaining perfect bug-for-bug compatibility is insanely hard, even for a large company.
3 weeks ago
Anonymous
>maintaining perfect bug-for-bug compatibility is insanely hard
at least they try, you seem like one of those devs that forced me to upgrade from 4 GB of ram
3 weeks ago
Anonymous
Flatpak doesn't increase memory usage of applications. It only increases disk usage, and almost everyone has tons of disk space to spare.
3 weeks ago
Anonymous
buying new SSD's isn't free you know, your just making a crappier product thats costing me money, dont you have a little pride in your work?
3 weeks ago
Anonymous
also im stuck in bumfuck nowhere and im tired of these download times increasing because of people who don't consider efficiency
3 weeks ago
Anonymous
Electricity isn't free either, yet you can read this. Go be poor somewhere else.
3 weeks ago
Anonymous
>why are you poor
not valid excuse for shitty lazy programming, go suck dick somewhere else fag
3 weeks ago
Anonymous
also, you are full of shit. If every program has its own snowflake library and i have multiple programs open, thats multiple duplicates of the same library loaded, when using the OS library would have just had 1 loaded
3 weeks ago
Anonymous
How is this any different from distros providing multiple versions of certain libraries?
>why are you poor
not valid excuse for shitty lazy programming, go suck dick somewhere else fag
You suggest running entire VMs for compatibility and call others lazy. Incredible.
3 weeks ago
Anonymous
1: i wasnt the VM guy
2: I can just have 1 version of the old library, i dont need to redownload it with every program
3 weeks ago
Anonymous
*1 copy, not version
3 weeks ago
Anonymous
>distributed for other OSes
not anon. Android APKs are unironically better than flatshits. you could download an APK directly from a website, you can't do the same for a flatshit.
either way they're both trash.
3 weeks ago
Anonymous
>you can't do the same for a flatshit.
Yes, you can. I literally did just that earlier today to try out Bitwig.
Why do people just blatantly lie about things that take FIVE SECONDS to debunk? Are you an actual invalid? Am I committing a hate crime by insulting you?
3 weeks ago
Anonymous
nagger you don't understand, flatpaks are not intuitive in that way, if you can't do it in a GUI it might as well not exist.
can you locate the flatpak, drag and drop it on a USB stick and give to someone else without touching the CLI? no? then its trash.
3 weeks ago
Anonymous
you do know command line utilities can be used for more things than tinkering with the OS, right
Most Windows software only supports Windows 10 and up these days because they all use Electron or CEF, which only supports Windows 10 and up. You could compile your software against the glibc in xenial and get the same level of support. >fatal error: libnagger-4.2.0 not found
You were supposed to bundle libraries with LD_LIBRARY_PATH or static linking.
It won't be no matter how much linux improves or even gets better than windows because normalfags are stupid sheep that will always use whatever is put in front of them like windows or chrome.
Tech dorks think anyone that isn't a tech dork like them must be "stupid sheep". Get a grip. You are the bottom rung of technical fields. There are people orders of magnitude smarter than you that have never touched a command line in their life.
>You are the bottom rung of technical fields.
In my case yes I'm not even in the technical field. Even I know they're stupid sheep. I used to be a stupid sheep myself about this. >There are people orders of magnitude smarter than you that have never touched a command line in their life.
Them existing doesn't erase the countless people who use windows just because they can't imagine using anything else to use the internet.
>Them existing doesn't erase the countless people who use windows just because they can't imagine using anything else to use the internet.
Okay, why should they have to?
3 weeks ago
Anonymous
I didn't say have to. But these are the people who will never even look into any other option and probably don't even know there are other options. Remember, all I said was linux will never be the desktop of choice because of them. That's just a fact.
3 weeks ago
Anonymous
humans are stupid shits anyways. who cares what the majority of people think or use? of the smart minority uses windows or mac in their day to day lives to fuck over the normies then all the power to them.
For one thing you don't "own" your software just because it's executable. But you probably meant you want your software to be easily accessible and offline which there are multiple ways to do this even for most software online literally just look it up and use a software manager and something like mint and you'll probably never see the command line.
3 weeks ago
Anonymous
>you don't "own"
it doesn't matter what corpos or governments have to say. it's not like an army of lawyers will bust into my house for using their software however I like. they only care about the big fish, other corpos that use their software while violating the terms.
On the other hand, the devs have said they have no problem with any efforts to get Affinity Suite running in Wine and there are multiple threads on the official forums right now where people are coordinating that effort.
is it stable? I wanted to give this a go with wine but I don't want to waste money in case it doesn't work. more than happy to pay for working software on Linux.
Unfortunately, appimage cannot confirm 100% dependency shipping and often times it breaks on updates and different distros. Most notable, it broke on all ubuntu and ubuntu based distros when the distros upgraded to libfuse 3.
I have shpped a number of GUI applications and never had good experience with Appimages. Ended up completely axing the appimage builds.
Flatpaks are ok but the issue is that they lack portability between regular end users.
its doable but its cumbersome.
with AppImages you just drag and drop the program and give it to someone else.
also developers might not want to rely on a centralized repo aka "App store" and just want to ship the program directly to their customers.
users don't want to add a repo. they either want to automagically find it in the store or download it directly from the developers website.
if for one reason or another a developer doesn't want to publish on flathub that means that the only viable option is either a custom installation wizard or an AppImage.
based. I make a major desktop app for mac os and windows and will never support linux. Working on a new one now. The linux desktop is a nightmare to develop anything for that you actually want most users to be able to run. Not to mention 0% of your revenue and 98% of your complains will come from linux users.
Yes, bugs in the linux version. Which is where 98% of the bugs will be, which incidentally are also the most time consuming to resolve if that's even possible.
Windows developers are idiots who think they have to recompile their programs for each and every distro, which they conclude is too much work so they refuse to produce a linux build.
You do have to test for at least major distros and WMs. Not to mention wayland and X flavours now. It's retarded. It's only practical to reliably ship applications no more complex than a fart app. Unless your okay with your app randomly being broken in random ways, which linux users are well used to.
All they need is a layer to rest their programs on.
vulkan/opengl for advanced graphics
X11/Wayland as a canvas to draw your GUI on
but they don't even need to do that, they could just target something like SDL2 which covers all your needs.
idk where this "we have to support every variation of linux tho" nonsense comes from.
>Compilation error because it couldn't find the windows/macOS in-built display library on the linux container
>Not designing your software with a proper crossplatform layer.
ngmi
Do you think the code for the bottom layer that interacts with the target OS will just pop out of thin air?
all they need is to target something like SDL2. and draw their GUI on top.
The naggers at Blender did it just fine, and for FREE. they could open a gofundme for a linux port if they're that greedy.
>and for FREE
blender foundation is sipping millions of dollars from nvidia, intel and like 30 other megacorps
Blender was crossplatform way before any major corporations took interest in it.
obviously, doesn't matter there weren't paid devs working on it full-time
my point being if a bunch of hobbyists can do crossplatform development fine in their spare time. so could a mid sized company like Affinity.
maybe "it doesn't make financial sense" but they really don't have anything to lose.
I mean im sure there is like an autistic developer or two in their company that would be more than happy to spend their time writing a Linux backend. and they only have to do it once.
i think you're underestimating the incompetence of an average programmer
also there's a stigma with linux so nobody wants to touch it but it shouldn't be problematic at all if done right
>there's a stigma with linux
ehh... normal people don't ever know what linux is, the stigma is probably from Wangblows users that used linux once like a decade ago and hated it.
I really doubt if they mentioned that they have a Linux version on their website that 99% of their users would even care. it might piss off a geeky wintoddler or two.
Do you think it's really that difficult to write such a layer?
systemd is becoming that
Flatpak is perfectly fine. If they can't get that to work, they're idiots and their app isn't worth your time.
they're both good enough.
>If they can't get that to work, they're idiots and their app isn't worth your time.
honestly whats their excuse? just target X11 and package your own glibc and pack it. I swear a 12 year old that just wrote their first hello world program could do it.
AppImage is okay, but when it doesn't work you're fucked, and it happens on occasion.
I dunno how you can fuck up Flatpak though, even some commercial products like Bitwig are available through it.
bitwig flatpak is horrible for yabridge vst compatibility unfortunately due to how flatpaks work
>If they can't get that to work
They can, but would be a waste of money, resources, etc, because there's no profit.
They're just being 'polite' about it.
>click compile for target: linux x86_64
>package it in AppImage
>Upload to website
pheew! what a waste money and resources!
app images dont work 100% of the time
because the devs are retarded. just statically link glibc and all your needed deps.
>doesn't work on my distro
then stop using it. any distro that doesn't support AppImage/Flatpak out of the box isn't worth using.
The problem here is anon probably not right clicking the appimage and setting it to is executable or whatever their file manager says in permissions.
AppImages should be executable by default
It is literally just a few clicks. Bug whoever made your file manager to make it executable by default I don't know. They probably won't for multiple reasons but you can try. it's not the fault of appimage.
A few clicks that add up over time. the less clicks the better.
i don't think you can save as executable from browser but i might be wrong
it'd make sense for appimage launcher to be preinstalled and automatically pick up appimage type files
That's not enough, full integration is needed otherwise you wont be able to open files with some programs and you wont see them in app launcher, among other things.
we need installation wizards back
either the wizard comes presinstalled or it comes with each AppImage.
something like AppImageLauncher but better.
app image doesnt ship all the required libraries, then I need to manually get the libraries compile and pray it was the only one required but not shipped on the app image, but most of the time is just dependency hell
>just statically link glibc and all your needed deps
kek nodev detected.
If you'd worked on any real world linux codebases you would realise how monumental of a task that actually is due to freetard obsession with shared libraries.
how hard can it be? does glibc refuse to compile if you try to statically link it? you could dynamically link it and just keep it in the same directory of your program Windows style.
Static linking glibc is not supported and I think you can't even do it nowadays. Static linking musl on the other hand, now that's the sane choice, and easy to do if you use something like nix.
just dynamically link it and package it with the rest of your program anyways.
>statically link glibc
Stupid and unnecessary, glibc has maintained ABI compatibility since the FIRST version released for Linux in 1999.
>glibc has maintained ABI compatibility since the FIRST version released for Linux in 1999.
what a load of bullshit. Lintroons are compulsive liars.
You can run "ancient" Linux binaries on modern systems just fine. Stop falling for stupid LULZ memes.
glibc literally broke compatibility not too long ago
https://www.gamingonlinux.com/2022/08/valve-dev-understandably-not-happy-about-glibc-breaking-easy-anti-cheat-on-linux/
Don't use unsupported hacks in your code. This is a basic rule on every platform, Windows, macOS, Linux, etc, it will even get you rejected from app stores.
this shouldn't be the concern of the developer thats relying on core system libraries.
core libraries should ideally never break compatibility.
if a feature is a "hack" that needs to be fixed NOBODY cares just keep it. the importance of my binaries working outweight the "need' to fix this "bug". it's a nonissue.
>core libraries should ideally never break compatibility
It happens all the time, especially if you're anticheat software digging through internal data structures instead of going through the supported API. I still remember how broken VAC was when Windows 10 released, SteamService.exe would literally take down your machine after a few minutes.
>if a feature is a "hack" that needs to be fixed NOBODY cares just keep it
You don't get it, there was no "feature", Epic was digging through data they weren't supposed to dig through. Nothing you need to worry about unless you're developing malware.
>It happens all the time
no it happens like once every 2 decades on Windows at most, but it breaks every couple of months or years at most on Linux.
>Epic was digging through data they weren't supposed to dig through
mind to elaborate?
>no it happens like once every 2 decades on Windows at most, but it breaks every couple of months or years at most on Linux.
You made up these numbers in your head.
>mind to elaborate?
They were looking for exported symbols by scanning memory manually instead of using a supported API (like dlsym). Makes sense for anticheat software but don't be surprised when it breaks.
https://maskray.me/blog/2022-08-21-glibc-and-dt-gnu-hash
>You made up these numbers in your head.
software from the early 2000s and even sometimes way before still works on windows10/11
try something like Fraps ancient crap that still runs. no way something like that would last this long in binary form on Linux.
I can run old programs in WINE that no longer work in win10
maybe they should fire that homosexual for pretending to be a linux dev.
Linux has a very stable API. You choose libc to be the intermediary layer between Linux and your program.
libc does changes according to the standard. This comes with changes that take 10+ years to be enforced, i.e. the functions to be totally removed from the library.
You can either pick a different library that takes care of those abstractions, i.e. apr library, or you can pick a library like musl and compile against it statically. musl comes also with a cuck license.
Do you know what these fags want?
minimum effort, maximum profit.
>error while loading shared libraries: libreallyold.so.0: cannot open shared object file: No such file or directory
You'll run into problems like that, but yeah glibc is an excellent example of *backwards* compatibility, so
has a non argument.
>compile a simple tool in ubuntu 22.04
>give to client
>client uses 20.04
>fatal error: glibc version too old pls update && upgrade
>client uses arch
>fatal error: libnagger-4.2.0 not found
>compile the same tool in windows 10
>give to client
>client runs tool in windows 11
>client runs tool in windows 7
>client runs tool in windows xp
>client runs tool in ubuntu
>client runs tool in arch
it's fucking retarded how I get way more reliability running windows software in Wine than I get when running native Linux binaries
Flatpak, retard. You aren't supposed to use distro libraries unless absolutely necessary.
Also, I can guarantee you that if your app isn't a game or made less than a decade ago, running it in Wine will have all sorts of subtle bugs. Don't bother "supporting" it that way.
>don't use the libraries in your OS!
this is unbelievably fucked, this is beyond microsoft levels of fucked, stop coping
You are aware that Flatpak is similar to how software is distributed for other OSes, right? Have you ever actually developed anything in your life?
>command-line utility
>being at all useful in Wine
LARP post.
yeah, i can compile my EXE for windows and microsoft don't change anything for bullshit reasons no one cares about, so i can count on it working for the next 15 years unless i did something unusual
>so i can count on it working for the next 15 years
...until you can't, in which case you are fucked, which happens at least 1/4 of the time because Windows' compat mode is a joke.
Source: have actually had to work with ancient Windows programs.
Filtered.
>Filt..ACK!!
I can do it with the CLI dickhead. but if normies can't do it then it's shit.
If you need it to be usable by idiots, why do you even care whether it runs on Linux?
both are fucked, but its a hell of a lot easier dealing with 12 year old windows programs than 4 year old linux shit
>...until you can't, in which case you are fucked
Then run ancient windows in a VM or use dos box.
Windows is not only the hands down champion for backwards compatibility in desktop apps, it's the only desktop OS that actually makes a genuine effort to preserve backwards compatibility with older software.
Even ancient windows exe tend to work fine unless they are doing something quite unusual.
>Then run ancient windows in a VM or use dos box.
lmao
>Even ancient windows exe tend to work fine unless they are doing something quite unusual.
They usually ARE doing something unusual. This is not the exception, it's the norm, and maintaining perfect bug-for-bug compatibility is insanely hard, even for a large company.
>maintaining perfect bug-for-bug compatibility is insanely hard
at least they try, you seem like one of those devs that forced me to upgrade from 4 GB of ram
Flatpak doesn't increase memory usage of applications. It only increases disk usage, and almost everyone has tons of disk space to spare.
buying new SSD's isn't free you know, your just making a crappier product thats costing me money, dont you have a little pride in your work?
also im stuck in bumfuck nowhere and im tired of these download times increasing because of people who don't consider efficiency
Electricity isn't free either, yet you can read this. Go be poor somewhere else.
>why are you poor
not valid excuse for shitty lazy programming, go suck dick somewhere else fag
also, you are full of shit. If every program has its own snowflake library and i have multiple programs open, thats multiple duplicates of the same library loaded, when using the OS library would have just had 1 loaded
How is this any different from distros providing multiple versions of certain libraries?
You suggest running entire VMs for compatibility and call others lazy. Incredible.
1: i wasnt the VM guy
2: I can just have 1 version of the old library, i dont need to redownload it with every program
*1 copy, not version
>distributed for other OSes
not anon. Android APKs are unironically better than flatshits. you could download an APK directly from a website, you can't do the same for a flatshit.
either way they're both trash.
>you can't do the same for a flatshit.
Yes, you can. I literally did just that earlier today to try out Bitwig.
Why do people just blatantly lie about things that take FIVE SECONDS to debunk? Are you an actual invalid? Am I committing a hate crime by insulting you?
nagger you don't understand, flatpaks are not intuitive in that way, if you can't do it in a GUI it might as well not exist.
can you locate the flatpak, drag and drop it on a USB stick and give to someone else without touching the CLI? no? then its trash.
you do know command line utilities can be used for more things than tinkering with the OS, right
>you need to use flatpak for a 2K LoC command-line utility
And then linuxtards make fun of Electron homosexuals
Most Windows software only supports Windows 10 and up these days because they all use Electron or CEF, which only supports Windows 10 and up. You could compile your software against the glibc in xenial and get the same level of support.
>fatal error: libnagger-4.2.0 not found
You were supposed to bundle libraries with LD_LIBRARY_PATH or static linking.
>linux users thinking they are entitled to anything
Funny as always.
Someday wintoddlers, someday Linux will be the desktop OS of choice.
>two more decades!!
It won't be no matter how much linux improves or even gets better than windows because normalfags are stupid sheep that will always use whatever is put in front of them like windows or chrome.
Tech dorks think anyone that isn't a tech dork like them must be "stupid sheep". Get a grip. You are the bottom rung of technical fields. There are people orders of magnitude smarter than you that have never touched a command line in their life.
>You are the bottom rung of technical fields.
In my case yes I'm not even in the technical field. Even I know they're stupid sheep. I used to be a stupid sheep myself about this.
>There are people orders of magnitude smarter than you that have never touched a command line in their life.
Them existing doesn't erase the countless people who use windows just because they can't imagine using anything else to use the internet.
>Them existing doesn't erase the countless people who use windows just because they can't imagine using anything else to use the internet.
Okay, why should they have to?
I didn't say have to. But these are the people who will never even look into any other option and probably don't even know there are other options. Remember, all I said was linux will never be the desktop of choice because of them. That's just a fact.
humans are stupid shits anyways. who cares what the majority of people think or use? of the smart minority uses windows or mac in their day to day lives to fuck over the normies then all the power to them.
not anon. bro i just want to own my software I don't want to use a command line either I just want the source code and im willing to pay for it.
For one thing you don't "own" your software just because it's executable. But you probably meant you want your software to be easily accessible and offline which there are multiple ways to do this even for most software online literally just look it up and use a software manager and something like mint and you'll probably never see the command line.
>you don't "own"
it doesn't matter what corpos or governments have to say. it's not like an army of lawyers will bust into my house for using their software however I like. they only care about the big fish, other corpos that use their software while violating the terms.
On the other hand, the devs have said they have no problem with any efforts to get Affinity Suite running in Wine and there are multiple threads on the official forums right now where people are coordinating that effort.
is it stable? I wanted to give this a go with wine but I don't want to waste money in case it doesn't work. more than happy to pay for working software on Linux.
I never had a single AppImage fail on me. Definitely something I cannot say about Flatpaks, or god forbid, Snaps.
Appimage is not a reliable deployment platform, but flatpak is.
both are. installation wizards and portable exes were always reliable on Windows. having a store (flatpak) is also nice but not necessary.
Unfortunately, appimage cannot confirm 100% dependency shipping and often times it breaks on updates and different distros. Most notable, it broke on all ubuntu and ubuntu based distros when the distros upgraded to libfuse 3.
I have shpped a number of GUI applications and never had good experience with Appimages. Ended up completely axing the appimage builds.
>2019
who is this, what is the context, and why the fuck should i care about a pre-covid forum post?
>Affinity
literally what?
>what is good software?
Don't they know Flatpaks exist? not need to worry if your distro includes the right libc library for appimages to run, it just works!
Flatpaks are ok but the issue is that they lack portability between regular end users.
its doable but its cumbersome.
with AppImages you just drag and drop the program and give it to someone else.
also developers might not want to rely on a centralized repo aka "App store" and just want to ship the program directly to their customers.
They can have their own flatpak repo. Though that means they will force users to open the terminal, as there's no flatpak repo gui for now
users don't want to add a repo. they either want to automagically find it in the store or download it directly from the developers website.
if for one reason or another a developer doesn't want to publish on flathub that means that the only viable option is either a custom installation wizard or an AppImage.
*is a single file that just runs, regardless of the platform*
linux is for servers only. you don't need affinity on servers.
based. I make a major desktop app for mac os and windows and will never support linux. Working on a new one now. The linux desktop is a nightmare to develop anything for that you actually want most users to be able to run. Not to mention 0% of your revenue and 98% of your complains will come from linux users.
linux users are also the first ones to report bugs. they're basically free QA
Yes, bugs in the linux version. Which is where 98% of the bugs will be, which incidentally are also the most time consuming to resolve if that's even possible.
>closed-source not available on linux
good
keep the botnet away from me
Windows developers are idiots who think they have to recompile their programs for each and every distro, which they conclude is too much work so they refuse to produce a linux build.
You do have to test for at least major distros and WMs. Not to mention wayland and X flavours now. It's retarded. It's only practical to reliably ship applications no more complex than a fart app. Unless your okay with your app randomly being broken in random ways, which linux users are well used to.
>>You do have to test for at least major distros and WMs.
They do not.
nagger no you don't have to test for anything.
the only problem is linux not having a stable ABI.
All they need is a layer to rest their programs on.
vulkan/opengl for advanced graphics
X11/Wayland as a canvas to draw your GUI on
but they don't even need to do that, they could just target something like SDL2 which covers all your needs.
idk where this "we have to support every variation of linux tho" nonsense comes from.