510
The #1 Programmer Excuse for Legitimately Slacking Off (2026 Edition) (lemmy.world)
submitted 9 months ago by to c/programmer_humor@programming.dev
40 comments fedilink hide all child comments
 

And for anyone interested in a template:

you are viewing a single comment's thread
view the rest of the comments
[–] 91 points 9 months ago (21 children)

What we need is some sort of distributed version control system.

I’m not quite sure how it will work yet, but it would have the entire codebase and its history mirrored onto every developer's computer. Instead of requiring a central repository, developers could share their changes directly with each other.

  • permalink
  • fedilink
  • source
  • hideshow 21 child comments
    •
  • [–] 29 points 9 months ago (5 children)

    but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 9 months ago

    For issues tracking there's the venerable git-bug, although development has sadly slowed way down in the last years.

    And I am always jealous of the way fossil repositories just have a complete front-end and wiki baked in, would love something like that for git.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 28 points 9 months ago (4 children)

    Maybe something on the blockchain??

    JK JK don't burn me on the public place!!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 15 points 9 months ago (3 children)

    git itself is really not far from a blockhain. Blockchain is fine, it only has a bad rep because of ponzi schemes that use it to create crypto, but the technology and trustless consensus mechanisms are interesting.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 9 months ago (2 children)

    I think blockchain also has a bad rep because every chance is mirrored to every copy of the blockchain? Thus wasting a lot of power and bandwidth for most use cases. Unlike git, where you only push what you want, and everyone only pulls what they want.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 9 months ago (1 child)

    The waste of power is often associated to the proof of work consensus, but that's not a requirement of blockchain. There are other ways to create consensus.

    The bandwidth requirements really depend on what's being stored, but it's usually very manageable for a server. And clients not running validation don't need to store or transfer that much data.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 12 points 9 months ago (3 children)

    Is this sarcasm about git/svn or are you serious?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 25 points 9 months ago* (2 children)

    It was mostly a joke/irony.

    Git is already a “distributed version control system” that does exactly what I’ve described. On the other hand, relying on centralized systems such as GitHub means that the “distributed” nature of it doesn’t make it any more resilient to failure.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 9 months ago

    We need better distributed connectivity. It wouldn’t be that hard to build a project management system (issues, etc) on top of Git, but DVCS only gets you so far without a way to connect directly to the other contributors.

  • permalink
  • fedilink
  • source
  • parent