just trying lemmy

  • 2 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 3rd, 2023

help-circle

  • Google loves open source likely for another reason than you do.

    Google loves open source when they can capitalize on it.

    That is, when a big community works on code that Google can use for free to build their monopolistic infrastructure. They love a global community which works for them for free. They might even foster this community as far as it serves their purpose or for image reasons.

    However, if they’d truly love open-source, they could open the source code to their core services. But they’d never ever do that. For this reason they also ban the AGPL license internally (https://opensource.google/documentation/reference/using/agpl-policy). The AGPL license would force Google to open their code which relies on AGPL licensed projects. Google hates that.

    Google does clearly not stand for the ethical values people usually have in mind when talking about open source. For example when something is competing with them, they’ll hate it. Like ad-blockers or browsers which don’t block ad-blockers like Google chrome does. The core business of Google is about surveillance and advertising. To maximize the profitability of this, then need to violate freedoms of their users (like the freedom to use their service while blocking ads). This is in direct conflict with the ethical values often implied by free and open-source software.

    So if somebody tells you “Google loves open-source and contributes a lot”, think about what it really means.


  • gitlab.com is a for profit service/company. They have an open-source community edition of Gitlab which you can run on your own server. Codeberg is a non-profit association running the open-source software “forgejo” for you. At Codeberg you can become a member and then you can vote for important decisions and make proposals. People also care about ethics there. Nobody cares about profit. Codeberg runs on donations from members. I think some people feel more respected at Codeberg because the governing body of Codeberg is a subset of its users. If Gitlab cares about you, then probably because a bad user experience would be bad for business.












  • This sounds really bad and I’m afraid it’s even worse than it sounds. For example, end of 2022 Italy introduced a law which bans certain types of harmless assemblies (rave parties) of more than 50 people (participants can be put to jail for up to 6 years). This is paving the road for cutting possibilities of people to protest against their government. (Imagine, there is a a protest and somebody plays music. The government will see a rave party.) Yet the Italian government seems to have no problem with 3000 neofascists visiting the hometown of Mussolini. And now this.




  • Spontaneous idea of how to use copyright law for keeping Meta out of the Fediverse (more for fun):

    Introduction: Parts of the Fediverse, including Mastodon, are software licensed under the APGL license. This license is a great choice because it forces the ones running the software to grant users access to the source code. GPL for example would allow to run proprietary services based on GPL code. The AGPL does not. Companies like Meta and Google will likely not use AGPL code because it might force them to also publish their proprietary systems behind the scenes. However, this does not help much for keeping the Fediverse save. They simply implement their own software which will not be open source.

    Therefore we may need another approach. Defederating is the simplest and in my opinion currently the best. It’s easy and keeps people in control.

    However, there could be some ‘automatic’ approach using copyright law. It’s a hack which allows to use existing law to regulate the way instances can federate.:

    • instances would Federate only if the other side can provide a certain piece of information called X
    • X is protected by copyright law, therefore by default, instances are not allowed to provide X
    • However, X is released under a license which for permits to copy and distribute X under certain conditions
    • The conditions allow to tune who can legally federate
    • Conditions could be
      • The server software must be AGPL licensed
      • The instance must not be owned by a company with a certain amount of annual revenue

    Open question is, who owns the copyright of X?



  • IDEs can automate build/test flows. But you can also automate them with scripts. This has the significant benefit that you can check this scripts into your version-control system (git) and publish them together with the code. Then your collaborators can use the exact same scripts. With IDEs that’s really not working well because it would force others to use the same IDE as you. Possibly the IDE configuration is not even version-control friendly.


  • You may actually miss out when using an IDE. Driving without training wheels is more fun :)

    I’ve used IDEs (Netbeans, Intellij) in the beginning but then started migrating away. They where just too heavy for me. Also, often IDEs do lots of stuff in the background such that you easily don’t understand fully what is going on. Now I settled using the ‘helix’ text editor. It provides some IDE-like features like integration with language-servers, syntax highlighting, code completion, file navigation, code navigation, symbol search. But there are no dozens of buttons for triggering compilation etc. You do all this on a separate terminal.

    Quite handy for such setups are tiling window-managers like i3. They allow you to easily fit the editor and terminals on the screen. This way you also don’t need the build-in terminal of an IDE.