No offence

  • lowleveldata@programming.dev
    link
    fedilink
    arrow-up
    32
    arrow-down
    3
    ·
    1 year ago

    ah yes programming languages are jokes themselves, and not the programmers using the wrong tools for the wrong job

    • Kryomaani@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      11
      ·
      1 year ago

      While true, there are some languages that are the wrong tool for every job. JS is one of them. I’ve dreamt of a future where web frontends switched to something sane but instead we got stuff like typescript which is like trying to erect steel beams in quicksand. For web frontends I can understand that historical reasons have lead to this but whoever came up with node thinking JS would be a great backend language has a lot of explaining to do.

      • lorgo_numputz@beehaw.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        I’ve commented to my cow-orkers that “Typescript is the bag they put over Javascript’s face so you don’t have to look at it anymore.”

      • ParsnipWitch@feddit.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I am also interested if anyone can tell me the exact time in our history when JavaScript turned from “Don’t you ever use that anywhere on your websites!” into “It’s basically every website”.

        • abraxas@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          It was when better sandboxing came out and the only valid complaints about javascript became invalid.

          I was there. It was a good time.

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

      Come on, Javascript is pretty nasty. Trying to read that shit always gives me brain tumors. Why do they need to wrap every fucking thing in a function inside a function inside a function that is passed as a parameter to a function inside another function?

      Like, bro, you know people are meant to understand what you just wrote?

      It just gives too much freedom and people forget they need to write code that is easy to read for people who aren’t totally familiar with the code base.

      They even bring that shit into typescript. Like they are already using a language that is meant to fix that shit and they are like, nope, let me create 5 nested functions just because.

      • NotSteve_@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        Can you give an example of the multi nested functions? I was a TS dev for a while and don’t remember anything like that. Unless you mean the promise callback functions. Those were a mess but luckily we’ve mostly moved away from those

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

          People creating functions as objects inside of other functions. A few days ago saw a person create a function with two object functions inside, then passed one of the functions as an argument to the other function. Then returned the second function.

          It’s hard to find such a mess in other languages. Yeha, functions as objects are cool. Closures are also cool… But why abuse that shit?

          • NotSteve_@lemmy.ca
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Ahh I remember that sort of JS programming from way back. Do people still do that?? You can just create a class now

  • quadrotiles@reddthat.com
    link
    fedilink
    arrow-up
    19
    arrow-down
    3
    ·
    1 year ago

    Ok, admittedly I was using typescript but honestly, I really enjoyed using JavaScript. I kinda feel like people who shit on it have never used it much, or aren’t very experienced, or it just wasn’t to their taste and they’re jumping on the hate train that the others like to conduct.

    (I also understand this is a joke dw)

    • gamer@lemm.ee
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      1 year ago

      I kinda feel like people who shit on it have never used it much, or aren’t very experienced

      How much experience do you have? (and don’t even think about lying; this is the internet)

      • quadrotiles@reddthat.com
        link
        fedilink
        arrow-up
        15
        ·
        1 year ago

        Definitely 2023 years worth of experience. I taught Jesus himself JS. Which, fun fact, doesn’t stand for JavaScript, but stands for JesusScript. I would never lie on the internet.

        (4ish years lmao)

        • gamer@lemm.ee
          link
          fedilink
          arrow-up
          2
          arrow-down
          3
          ·
          1 year ago

          4 years isn’t enough to hate javascript. Either those 4 years are entirely in JS, in which case it’s all you know and thus you lack perspective. OR, you spent e.g. 2 years with a different language and only 2 in JS, in which case you don’t have enough experience with JS to have an informed opinion.

          Don’t worry though, we all started our JS hating journey like that. Give it a few more years and I promise you’ll be able to hate javascript like the masters.

          • quadrotiles@reddthat.com
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I never said I had a total of 4 years experience, only that I had 4 years of JS experience.

            But yes, I will work on honing my hatred. I hope to one day gain a seat at the JSith council and achieve the rank of master.

          • maltroth@lemmy.ca
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            10ish years here, I don’t hate js. The more modern tools, frameworks and typescript makes it awesome to use for frontend stuff.

    • Primal@beehaw.org
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      My feelings toward JavaScript depend on the context in which I’m using it. I really like JavaScript in a React app or Next.js, but I don’t care for it in Views and Razor page in .NET web applications, though it’s getting better.

    • Redrum714@lemm.ee
      link
      fedilink
      arrow-up
      5
      arrow-down
      5
      ·
      1 year ago

      Glad C++ will be the one step on it cause it deserves it. I’d take PHP over that shit any day

      • vrighter@discuss.tchncs.de
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        it is a horribly slow, ugly language, with the most braindead scoping rules (apart from js, of course). The only fast parts of it are libraries written in other languages, because python itself is not up to the task for anything more than glueing code from other, better languages together.

        • nothacking@discuss.tchncs.de
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Honestly JS seams saner then python, it’s wierd but rather sane. The only really bad parts of JS are the type coercing == and =! operators which are very broken

          For example “” == 0 and 0 == “0” are both true, but “0” == “” is false.

          • vrighter@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            this is an unpopular opinion of mine, but I think lua is, in turn, a saner version of js. Apart from the 1-based indexing (which really isn’t that big a deal imo). But I really love the stackful coroutines.

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

              I haven’t worked with any 1-based indexing languages, but I can’t really see how it could be problematic. The only advantage I see about 0-based indexing is the simplicity in how the memory address is calculated. Just arr + index × sizeof(member) which I think even has its own MOV instruction on x86. But besides that I can’t see any more advantages. With 1-based indexing I see the advantage of the number of elements also being the index of the last element of the array, avoiding off-by-one errors when writing. Though, again, I’ve never used a 1-based indexing language.