• bob_lemon@feddit.de
      link
      fedilink
      arrow-up
      13
      ·
      10 months ago

      The more you learn about JavaScript, the less you understand how the modern web actually functions.

  • vexikron@lemmy.zip
    link
    fedilink
    arrow-up
    2
    arrow-down
    16
    ·
    10 months ago

    Ah yes, javascript, the database language.

    Jesus fucking christ I am so glad I don’t work in the corporate tech sector anymore.

      • vexikron@lemmy.zip
        link
        fedilink
        arrow-up
        1
        arrow-down
        14
        ·
        edit-2
        10 months ago

        If you need to be able to do unions and you are doing it in javascript, you are being absurdly inefficient compared to setting up a postgres db, but i wont be able to convince you of this because of basically nonsense brainwashing from your corporate conditioning.

        EDIT: Note to self, do not use lemmy while hangry.

        Yep Im wayyyy off base here.

        • Kogasa@programming.dev
          link
          fedilink
          arrow-up
          9
          ·
          10 months ago

          Why would you need to set up a postgres db…? Unions are a fundamental set theoretic operation that are applicable to all set-like collections. You may as well say “an in memory hash map / list is absurdly inefficient compared to a relational db.” Is it efficient, to you, to spin up a postgres instance to hold a dozen key value pairs?

        • median_user@lemmy.one
          link
          fedilink
          arrow-up
          5
          ·
          10 months ago

          Sets are super useful for all sorts of stuff where you want the datatype to guarantee there is only one instance of a value in the collection. UI components where you are incrementally adding things to a selection is a great example.

          It’s a completely standard feature in many stdlibs and has nothing to with turning JS into a database.