User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
you see, you should hold both proprietary and free software to the same standards and not just be like "oh this thing crashes a lot, that's fine", or "this is very inconvenient in use but that's fine" when you are using non-proprietary shit "software"
❤1
3
2
5
1

User avatar
Katze von Schrott @schrottkatze@chaos.social
2y
@jeder im sorry but that sounds toxic as hell. proprietary software usually has a lot of money and power behind it, while small foss projects only a few people or even only one person.
1
3
3
0
User avatar
M⑨ddie @mjdxp@labyrinth.zone
2y
@schrottkatze @jeder imo it's often worth dealing with some shortcomings of software developed by a smaller team if it means not getting fucked over by big tech deciding they need to extract more money from their users
0
0
1
0
User avatar
RedPandaLiz ΘΔ @RedCyberPandaz@zoner.work
2y
@jeder yeah we should totally hold software thats made by 2 people in their free time to the same standard as software made by a billion dollar company.
1
0
1
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
0
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
"but you can fix it yourself!!" consider this: you can't, before you'll fix it yourself you'll most likely waste hundreds of hours figuring out other shit software and the architecture of software you want to "fix" that you need in order to actually write a single line of code, not to mention another hundreds of hours of time you'll spend on "learning" how to code, at which point you'll also most likely figure out that you are not even predisposed to write code so you'll just throw all that shit out
0
1
1
0