• 0 Posts
  • 260 Comments
Joined 2 years ago
cake
Cake day: March 28th, 2024

help-circle










  • Because it adds something that is not essential, so it is not “simple”. If package A depends on package B with an incompatible license then it needs to provide a means to specify alternate packages. Arch follows upstream with best effort possible, so changing dependency could be seen as breaking that. However, pacman already supports choosing alternate packages during installation so technically they could add it, but how many percentage of users are needing that convenience? Not to mention the arch team will need to maintain said list of alternatives for every dependencies. If you want, you can add it yourself via pacman hook to prevent you from accidentally installing non free software, or write a wrapper for pacman, or use other distro like Parabola.






  • Because for big SaaS (international) companies, managing your own infrastructure can be hard or borderline impossible. Each country has regulation regarding data centers, each must have disaster recovery and scheduled backup, each must have redundancy to the max, and many other things to consider when hosting on your own infrastructure. Meanwhile you can use that money to pay developers instead of paying someone to wrestle with server stuff.




  • My point is, clear up your mistakes in communication. It doesn’t help anyone to spread misinformation. I hate MS as the linux guy next door, but making false accusations, intentionally or not, will make people stay away from you. Because as I stated, I immediately understand the context just from you sending ToS of a plugin owned by MS. But your accusation is different entirely than your intention.


  • I never have a problem with your follow up, even if you still did not specify your intention explicitly. At least the ToS is for a plugin that is owned by MS so it provides a clue to what you’re referring to. I have a problem with your original statement.

    … A lot of the functionality is in the marketplace but non Microsoft products aren’t legally allowed to use it and you’re not allowed to distribute builds of the plugins.

    To put differently:

    A lot of the functionality is in the marketplace. Non MS products aren’t legally allowed to use it (1). You’re not allowed to distribute builds of the plugin(s) (2).

    See the problem? That statement with the follow up is accusing MS restricting your right to use MS marketplace from non MS product as a problem (1), and THEN accusing that you cannot distribute the build of the plugins from said marketplace (2) which is only true for MS owned plugins.