• 0 Posts
  • 23 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle


  • Clean git histories are fun for the people who care, but they are also mostly useless.

    I’ve been around a lot of arguments about the commit standards in teams and it’s always boiled down to the “I don’t care, but I don’t want to spend time doing anything special” people vs the “do the things the way I like because I can think of three reasons it’s technically superior but not practically useful to do so” people.

    Bikeshedding at its finest






  • I’ve been around open source for 20+ years and can tell you right now that it don’t work that way. An issue tracker and a wiki is not a community.

    Most older open source communities were built on irl connections and irc, with some mailing lists thrown in. Hell, we even funded conferences just around the software, not to sell a product but just because it’s good for everyone to be talking to each other.

    The issue tracker tracks the status of things, the wiki is generally user focused. It’s not where development happens or thinks get built.







  • They take advantage of viewer federation a lot, webrtc is used, so all the simulated browsers are sending the video to each other rather than hitting their server. So their setup is really just a part of the p2p swarm, like a single client in a bitorrent network. Doesn’t use anything fancy above that.

    Honestly, it’s only a setup that’s gonna get far if you serve very few videos, and the P2P client rate is high. Their “real world” assumption of 50% of all clients being p2p enabled is way too high, and they couldn’t limit p2p bandwidth so all the clients were sending data to each other at lan speeds.

    It’s interesting, but it needs to actually leave the simulation and enter real world load to know how things shake out.