Full On-chain NFT Maker VS Commit Together by Github

• Decentralization
  Full On-chain NFT Maker ensures that all data related to NFTs is stored on the blockchain, enhancing security and immutability.
• Permanence
  Since NFTs and their metadata are stored entirely on-chain, they are not subject to loss or manipulation, ensuring content is permanently available.
• Automation
  Smart contracts manage the creation and execution of NFTs, reducing the need for intermediaries and streamlining processes.
• Transparency
  The complete on-chain storage allows for full transparency and easy verification of NFT ownership and authenticity.
• Interoperability
  On-chain NFTs have the potential to be easily integrated with other blockchain-based applications and platforms.

Possible disadvantages

• Cost
  Storing large amounts of data on-chain can be expensive due to the costs associated with blockchain transactions and storage.
• Scalability
  On-chain storage can face scalability issues as the blockchain grows, potentially impacting performance and speed.
• Complexity
  Developing fully on-chain solutions requires a high level of expertise in blockchain technology and smart contract development.
• Data Limitations
  Blockchains have limitations on data size and types that can be stored, which can constrain the complexity of NFTs.
• Market Adoption
  While on-chain solutions provide significant benefits, the market is still adjusting, and broad adoption may take time.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

Tracking Full On-chain NFT Maker since Feb 2022.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago