• nonearther@lemmy.ml
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 year ago

    IMO, deno’s approach was bad as it was reinventing the wheel, so one had to relearn. And then they brought package.json which they said they wouldn’t. This again got people to unlearn and relearn things.

    Bun, on the other hand, acts like what Typescript is to Javascript. It’s just feels like superset of Node, instead of completely different tool.

    I expect Bun will get more success than Deno.

    • snowe@programming.dev
      link
      fedilink
      arrow-up
      4
      arrow-down
      4
      ·
      1 year ago

      Makes sense. Deno was created by the same person that created node. They’re both going to be terrible, especially when they ignore everything ever discovered in software engineering about writing good code, good frameworks, good languages, etc.

          • sip@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            sorry, brainfart. I read “bun is created as the same who created node” 🤦🏻‍♂️

            • snowe@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              gotcha. I don’t think bun is created by the same person that created node. deno is, and has just as bad a design as node as a result. it honestly baffling that people trust someone to write a language who failed so badly to write a language that they set back the entire world for decades to come.

              • sip@programming.dev
                link
                fedilink
                arrow-up
                2
                ·
                1 year ago

                idk I think people can learn from their mistakes and evolve. especially if they accept collaboration and RFCs.

                I haven’t worked much with deno, so I can’t tell. But I earn my living with Node and it’s ok. I dislike js way more than node itself.

                I guess all the hate is around module resolution and package management.

              • sip@programming.dev
                link
                fedilink
                arrow-up
                2
                ·
                1 year ago

                idk I think people can learn from their mistakes and evolve. especially if they accept collaboration and RFCs.

                I haven’t worked much with deno, so I can’t tell. But I earn my living with Node and it’s ok. I still hate js more than node itself.