• vrighter
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    1 year ago

    nope. The bloat is there mainly because it makes the job easier for the devs.

    • ZILtoid1991@kbin.socialOP
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      In the short run, yes. In the long run, this just makes a bunch of coders that are now afraid of type declarations, because they were scared away from it with the “what if you have to choose?” tagline, thus making turning back to the proper way of doing things harder.

      • scubbo@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Can you talk more about this? I’ve never heard that tagline and can’t figure out what it’s supposed to mean.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Just from context, I’m guessing it means that you might type things one way and then need to use them another way later, and dynamically typed languages are sold as not having that problem.

    • CanadaPlus@lemmy.sdf.org
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      I was thinking about this a bit. Does that mean you can develop a piece of software much more cheaply now? I have a fear that companies writing software get a 10% discount from writing bloat, while clients wind up using 10,000% the resources and are just so used to it they don’t complain.