☆ Yσɠƚԋσʂ ☆

  • 101 Posts
  • 178 Comments
Joined 5 years ago
cake
Cake day: January 18th, 2020

help-circle














  • It’s much better to fund projects using a nonprofit foundation. There are plenty of examples of this. The problem with corporate muscle behind it s that development priorities end up being driven by the corporations doing the funding. In some cases, like the Linux kernel, there can be enough alignment so that it’s not problematic. However, Chrome is an excellent example of how corporate backed open source goes horribly wrong.


  • It’s not just a problem of stuff getting acquired. Companies exist to make money, and they have to chase new customers. No matter how good the software was originally, sooner or later you’re going to stop being the target demographic. This happens all the time, every single proprietary product I’ve used eventually changed in a way I did not want it to change. At that point I either have to adapt or find a new product. On top of that, companies go out of business all the time. At that point you lose support for your product, or if it’s an online service the product itself disappears.

    With open source the situation is much better. As long as there’s a community of users who want it to work a particular way, then it’s always possible to fork it and keep it working the way you want. A perfect example of this was when GNOME started moving in a direction a lot of people didn’t like, and now we have Cinnamon and Mate desktops.






  • I really like the idea of using a relation db to track change history. It removes so much weirdness and quirkiness that git has. You just have regular SQL queries you can use to go through history and ask questions about the state of the repo. I also like that it’s immutable so you don’t have to worry about things like rebasing and other ways you can fuck up history in git. The problems solved by mucking with history largely go away when you can query the db with a rich syntax.