• jjjalljs@ttrpg.network
    link
    fedilink
    arrow-up
    9
    ·
    1 month ago

    Thus, you have validated my comment you found insulting.

    I don’t think insults are going to benefit anyone.

    But the logic to perform operations on those tables for a transaction and accounting system must still be written. One of the main aspects of blockchains are exactly such an API.

    Transactions are one of the most basic things databases do. Audit trails are also extremely common. Have you done any development that uses a relational database? Nothing you’re describing is difficult or uncommon.

    When you buy an NFT, the actual data for compromising the NFT itself is stored somewhere else. The blockchain just has the token proving ownership.

    I don’t see how this is a plus or unique. A typical row in a standard table would be like pk, item_id, owner_id, etc. Foreign keys are extremely common.

    You are debating so confidently and asserting things so boldly, yet you don’t have the knowledge of the topic that a 2 hour tutorial would give you. That is the real problem

    I mean, maybe, but I’m really not getting the impression from you that you know how existing technology works. I’ve been a software developer for more than a decade so I’ve got that going for me.

    • Vilian@lemmy.ca
      link
      fedilink
      arrow-up
      6
      ·
      1 month ago

      bro, just point at Valve, they did all of that without stupid NFTs almost 20 years ago with CS and TF2, all of that, without blockchain and shit, the algument of NFT being descentralized is okaysh, but claiming that you can’t do that without NFT, or no one ever did is plain wrong

    • pantyhosewimp@lemmynsfw.com
      cake
      link
      fedilink
      arrow-up
      1
      ·
      29 days ago

      So you’re a developer. Beautiful. That makes it easy then.

      Look, you mentioned Postgres. But why use it at all for anything? Because redoing all the features that separate product provides is a giant pain in the ass. Now, what if your needs didn’t quite work with trad-relational DBs? Too much data, reads a million times higher than writes, no need for real-time accuracy. Then you use a specialized db like BigTable.

      There are other services you plug into instead of reinvent. You stand up web servers with special features like redirect rules as configuration. You could write your own web service every time you start a new app, but that’s crazy. The need Apache or whatever is filling is a communications management piece.

      Ok. Now. You are building a service and you need to build a transaction system for trading of digital assets with fiat currency. You could write your own or you could use a specialized service. NFTs on crypto currency are that prebuilt service. I’m switching metaphors now, but it’s just like picking a Docker provider.

      • jjjalljs@ttrpg.network
        link
        fedilink
        arrow-up
        1
        ·
        29 days ago

        Look, you mentioned Postgres. But why use it at all for anything?

        It’s a good tool for the job. It’s well tested, supported, documented, etc

        I really don’t see the value that NFTs and block chain offer for games (or much else). I don’t want to store my game data on some block chain. That’s going to be slow and awkward. A quick Google says etherium can handle like 10 transactions a second. Bitcoin takes like 10 minutes. That’s unacceptably slow.

        So it’s more like switching from postgres to an Excel sheet.