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

help-circle





  • I’m familiar with them.

    These are projects sitting years, maybe even a decade, away from maturity. IF web standards and capabilities don’t change at all over the next 5-10 years.

    Hopefully that puts this into perspective. These are really cool projects, but without a massive influx of engineering effort and organization, they will likely be perpetually, hopelessly, behind the standard rate of change required of browsers. Nevermind meeting the current standards of performance, security, observability, ecosystem, user and developer experience.

    It’s always good to check in on these projects yearly, see how it’s going, see if they are accelerating or slowing down. Eventually one of them will take off, and potentially leech resources from other similar projects.


    Though, the nature of FOSS is that 1000 people will work on 200 different projects all trying to do the same thing, instead of combining and organizing efforts to go after the same unified goal.

    This isn’t really a statement of fault but rather a statement of reality. Without dedicated full-time organization, this is usually how scattered resources solve problems. Which is a core problem here in that dedicated organization to rapidly grow the engineering effort for a particular project usually requires funding and full-time employees. To both market it to engineers as an interesting project, mature documentation and DevX, mature the onboarding experience for devs, and to handle the organizational aspects of distributing said work.


  • A company founded and funded on the concept of activity tracking? Private?

    Also, when they first started they seemed to have an unlimited advertising budget, which is why they blew up. Where did that money come from, and what was the promise to those investors on how Brave will bring back revenue to them?












  • Definitely not tube archivist…

    Development is semi-frozen. The developer is also more hostile and they need to be even to contributions from others.

    And it does not store your files in a way that is self-contained. And there is no option to control the naming or organization of the files it stores.

    Your file system should be navigatable and understandable without having to run software and pull information from a database in order to interpret it. Tube Archivist is far FAR from ideal media archival software IMHO.

    It misses the mark in so many ways it drives me insane.



  • Protocols are much more difficult to create and implement.

    The barrier for technical ability and maturity is much higher. Which is why you don’t see them as often, and when you do see them they tend to suck, have massive gaps, or some other significant failing that prevents them from really scaling out.

    Building reliable and robust protocols with a hobby project is a nearly impossible task, it takes a lot of effort and a lot of minds over a long period of time to settle on the specifications. And just as long to actually implement it.

    Usually this requires some sort of funding and dedicated resources from the get-go. Which many of these projects lack.