Unpopular opinion Show more
Installing an application from your distro is like buying a product from a local mom & pop's store.
Installing an application with pip, npm, docker, appimage, etc. is like buying a product from a huge global corpo.
Using a web application is like renting a product from a huge global corpo.
I should use the browser less.
Btw. do you want to try to figure out why webapps are so popular and what we can do to fix this?
`apt install gajim` is also free, and also lets you upload pix...
IMO, there are two important aspects here, that influence each other:
- ease of installation
- branding instead of blending in the system
I'll try to elaborate on them, but my knowledge/suspicions are not systematized yet.
1. For some reason, there's a trend for each app to have its own branding and consistent UX across platforms/OSes, instead of each version being consistent with the platform/OS it works on.
2. This is strongly correlated with the trend of each app using its own proprietary protocol, instead of having common, standardized application-layer protocols with multiple implementations.
3. 1 and 2 would be impossible without being able to easily make and distribute cross-platform apps.
fuck I lost my train of thought
Ok, so 1 and 2 require that it's easy:
3.A for a developer to make cross-platform app
3.B that there's a way to easily install an app on the target platforms
3.C that it's easy for the developer to start distributing the app in that way
Generally getting people to use something requires that it's easy to install (3.B). Because people are lazy^W^W value their time.
Distro packages are easy to install, but hard for 3rd parties to get their app into.
Webapps are the easiest to install.
Webapps are the easiest to install, and the quickest to start distributing. You don't need anyone's approval.
So, we could - in theory - eliminate those one-size-fits-all apps by:
eliminating 3.C - making it so that it's hard for developers to make their apps available for easy installation,
or by eliminating 3.A - making it hard to develop cross-platform apps.
We can't eliminate 3.B because it will also hurt our clients for standard protocols.
Another thing related to branding is communication about the protocol/app between newbies.
If the protocol, the network, and the client have the same name, it's easy. "Hey, are you on Telegram?" "No, how do I?" "Just search >>telegram<< and install the first search result".
OTOH, with XMPP^W Jabber (for the sake of easy pronunciation), the person will need to find a Jabber client for their platform. There will hopefully be more than one. They'll have to decide which to use.
And then they'll need to remember the association between their clients' name, and the name of the protocol.
And all that assumes they care enough to make a decision and not quit the first moment they see multiple options.
We are a cute and loving international community Ｏ(≧▽≦)Ｏ !