• Tenkard@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago
    1. You can call it “Java” to enrage other programmers
    2. You can compare numbers against strings without wasting time converting them
      • nxdefiant@startrek.website
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        5 months ago

        JavaScript: :wide eyed and smiling: Sure why not! You’re the boss!

        Python: Sighing and downing half a bottle of Advil: Sure. Why not, you’re the boss.

      • luciferofastora@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        But what if I don’t want strict comparison? What if my frontend contains a text field for a numeric input and I wanna manually check against each possible valid input value if (input_val == 1) {...} else if (input_val == 2) {...} else if... without having to convert it first or check that it’s actually a number or fix my frontend?

        (I’m sure there are valid use cases for non-strict comparison, I just can’t think of one right now)

        • PrettyFlyForAFatGuy@feddit.uk
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          5 months ago

          why wouldn’t you just convert inline? (Number(input_val) === 2)

          Converting would mean you could use a switch statement with your example rather than an if else ladder

          switch(Number(input_val)) {
            case 1:
              doTheFirstThing();
            break;
            case 2:
              doTheSecondThing();
            break;
            case 3:
              doTheThirdThing();
            break;
          }
          
          • luciferofastora@lemmy.zip
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            5 months ago

            If you’re looking for good code, you missed the point of my comment 😄

            If I was looking for an enumeration of valid inputs, I’d make it a selection box rather than a text field that’s supposed to contain a number and give the selections reasonable names. If I want an integral quantity, I’d use a number input field.

            If I have no control over the frontend, that means I’m writing a backend in JS for a bullshit frontend, and no amount of good coding practice is going to salvage this mess.

            I’m also blessedly far away from WebDev now. I work in Data Analytics and if I ever have to do any of this for a living, something has gone very wrong.

            Converting texts into numbers or dates still haunts me though - fuck text inputs for numbers and dates.

    • ByteJunk@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      I spent way too long today figuring out why my app was doing something that it’s NOT supposed to do on weekends.

      I read Luxon’s docs (pretty cool lib tbh) again and again, and tried everything I could think of to get isWeekend to return a sane result.

      Turns out I was pulling a somewhat older version of Luxon, where isWeekend didn’t exist. In any sane language, I expect I’d get a huge warning about a property that doesn’t exist, but alas…

      Typescript helps me keep my sanity, but juuuuust barely.

      • mynameisigglepiggle@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        5 months ago

        If isWeekend doesn’t exist, then the weekend doesn’t exist, so it’s naturally false.

        That’s why JavaScript gets pushed so hard - it’s part of the capitalist agenda to keep us working 7 days a week

          • shastaxc@lemm.ee
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            5 months ago

            Falsy* because it was undefined

            However, their IDE should have highlighted it as an unknown property. Guess this guy is coding in notepad or vi.

            • humbletightband@lemmy.dbzer0.com
              link
              fedilink
              arrow-up
              0
              ·
              5 months ago

              Yep, thanks for correcting me. In fact, if they write something like

              if (day.isWeekend) {...}
              

              The block will never be executed with the old version of library

              • shastaxc@lemm.ee
                link
                fedilink
                arrow-up
                0
                ·
                5 months ago

                Yeah that’s exactly what I think happened to him. He needs a better IDE and/or needs to stop copy/pasting code from stackoverflow or documentation that doesn’t match his library version.

                • ByteJunk@lemmy.world
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  5 months ago

                  My dude, you need to understand that all that anger and resentment, it is not you. It’s the years of JavaScript poisoning your mind.

                  In any case, that goes to my point. I would have to be saved by my IDE, when any sane language will blow up in your face as soon as you try to run it.

    • Drusenija@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      What’s even wilder is if you look at the code of that package, all it does is include the is-odd package and then return !is-odd. And the is-odd package isn’t much better, it does some basic checks on the input and then returns n % 2 === 1.

      • NotAViciousCyborg@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        I thought I was missing something. JS is one of my main languages and I always just write the is-odd function myself since it’s like 10 characters. It boggles the mind that is-even has 176k weekly downloads

        • gaael@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          Also there are 40-something packages depending on it, so I guess it gets pulled automatically when they are used.

        • Aqarius@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          If youre lazy/busy enough, doing basic checks on the input is enough boilerplate to package out.

        • kevincox@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          To be fair having a name can make things easier to read. I get that i % 2 == 0 is a common pattern and most programmers will quickly recognize what is happening. But isEven(i) is just that much easier to grok and leaves that brainpower to work on something else.

          But I would never import a package for it. I would just create a local helper for something this trivial.

          • NotAViciousCyborg@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            Exactly what I would do if I had to reuse it, especially now since I know that adding a package would actually add 2. It all just seems so…inefficient

            • kevincox@lemmy.ml
              link
              fedilink
              arrow-up
              0
              ·
              5 months ago

              Even if the code isn’t reused adding names to sub-expressions can be very valuable. Often times I introduce new functions or variables even if they are only used once so that I can give them a descriptive name which helps the reader more quickly understand what is happening.

              • NotAViciousCyborg@lemmy.world
                link
                fedilink
                arrow-up
                0
                ·
                5 months ago

                Yeah, I do that with pretty much every separate operation in c# since our solutions are pretty big. Most of my JS scripts are just done in ServiceNow which are separated and named appropriately.

    • kamen@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      This must be a “hold my beer” kind of joke and someone wanting to see how far they can take it.

  • udon@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago
    1. it’s easy to make fun of
    2. it makes every other programming language look better in comparison
  • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    The part that always gets me is when people choose Js for the backend. Like I get that it’s the default thing that works on the frontend, so there’s some rationale why you might not want to transpile to it from another language. On the backend though, there are so many far better option, why would you willingly go with Js, especially given that you’re now forced to do all your IO async.

    • 31337@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      Server side rendering looks like it could be useful. I imagine SSR could be used for graceful degradation, so what would normally be a single page application could work without Javascript. Though, I’ve never tried SSR, and nobody seems to care about graceful degradation anymore.

      • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        Most pages tend be just documents and fairly simple forms. Making SPAs and then having to worry about SSR is just making a Rube Goldberg machine in most cases. I think something like HTMX is a much better approach in most cases. You keep all your business logic server side, send regular HTML to the client, and you just have a little bit of Js on the frontend that knows how to patch in chunks of HTML in the DOM as needed. Unless you have a highly interactive frontend, this is a much better approach than making a frontend with something like React and adding all the complexity that goes with it.

    • jubilationtcornpone@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      I moved from primarily ASP.Net Core backends, which is a hell of a great backend framework btw, to NestJS. Not my choice. I do what the people who sign my paychecks ask for.

      I cannot begin to fathom why anyone would willingly choose JavaScript for backend. TypeScript helps a lot but there are still so many drawbacks and poor design decisions that make the developer experience incredibly frustrating. Features that are standard in ASP.Net Core, Django, or other common backend frameworks just don’t exist.

      Also, don’t get me started on GraphQL. Sure, it has performance advantages for websites of a certain size and scale. But 99% of the websites out there don’t have the challenges that Facebook has. The added complexity and development cost over REST is just not worth it.

      • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        Yeah, gql in particular is a problem looking for a solution in most cases. It makes sense for facebook because they have people building frontend apps for their marketplace, and those apps need all kinds of weird combinations of data. However, this isn’t the situation for most apps where you have a fairly well defined set of calls you’re doing.

      • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        No I meant having to do async as opposed to having threads like you would in Java for example. In vast majority of cases a thread pool will work just fine, and it makes your code far simpler. Typically, Java web servers will have a single thread that receives the request and then dispatches it to the pool of workers. The JVM is then responsible for doing the scheduling between the threads and ensuring each one gets to do work. You can do async too, but I’ve found threads scale to huge loads in practice.

      • KillingTimeItself@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        bash would be a scripting language, though to be fair, i also consider bash to be pseudo code as well.

        If JS is a scripting language, than any other language is a scripting language. And technically, every language can be used to script, so therefore, is a scripting language. i’m referring to the aspect of a scripting language being generally constricted.

        • meteokr@community.adiquaints.moe
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          Pseudo code is literally fake code. Scripting is an actual type of code. Scripted languages while not strictly defined, usually refers to languages you don’t compile before running them. Bash is considered a scripting language because you don’t ship a binary compiled executable, but rather ship a file that is human readable and converted into machine code when it is run. Scripting languages are compared to compiled languages, like C or Rust. Where the file you run is already compiled, and executed directly.

          What do you mean by this?

          i’m referring to the aspect of a scripting language being generally constricted.

          Any Turing complete system, or this case language, can do anything any other one can, depending on the level of suffering you are willing to endure to make it happen. Anything JS can do, Rust can do. Anything Rust can do, Bash can do. The differences between languages is the assumptions they make, and performance characteristics as a result of those assumptions. Functionality is not practically different from one another, though some absolutely make it easier for humans to do.

          • KillingTimeItself@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 months ago

            Pseudo code is literally fake code.

            hence why i specified why i consider it to be as such. I just think pseudo code shouldn’t exist. Plain and simple. Bash scripting is close to a language in the same way that pseudo code is also technically code.

            What do you mean by this?

            i just mean the simple fact that you could technically probably run bash on windows, but really wouldn’t want to. I don’t consider bash to be a programming language, though it is technically a scripting language, because it’s primary existence is in the shell environment of a system. I.E. constricted, but that’s just my view of it.

            • meteokr@community.adiquaints.moe
              link
              fedilink
              arrow-up
              0
              ·
              5 months ago

              Bash being on the same level as actually fake code is a pretty hot take to me. What are your opinions on Python, or Ruby, or any other interpreted language? You could very well use them as your login shell, just like Bash if you wanted. In your eyes, if Bash *isn’t * a programming language at all, how do you describe a programming language? Languages that express code are just the same as languages that write stories, and whether you do it in German or Vietnamese makes no difference on what story you can write.

              When you describe a language as constricted what do you mean? Bash can do anything Python or Rust can do, each of them is just specialized to being better at specific aspects for human convenience in writing code. There is no inherit limitation on what can be done by the language you use to express it.

      • palordrolap@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        Depends on how you define “scripting language”.

        Older techs remember when it was only browser-based and they thought of, and perhaps still think of, “scripting languages” as something that would run from some command-line or another. Starting a GUI browser to run a mere script was a ridiculous concept. (There was also that JavaScript had no filesystem access. At least initially. And then it became a gaping security hole, but I digress.)

        Today, there exist command-line accessible versions of JavaScript but even there (I figure) most people wince and choose anything else instead. Maybe even Perl.

        But another definition of “scripting language” is “(any) interpreted programming language” and where it runs is unimportant.

        From that perspective, sure, JavaScript qualifies. And so does QBASIC.

        • shastaxc@lemm.ee
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          A script is just a file that can execute a series of commands without the need to compile

          • Centaur@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            5 months ago

            They compile in some point of time because CPU don’t know shit about Javascript. But that is for some other discussion.

            Edit: typo

    • inetknght@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      It’s also not a scripting language.

      It definitely is a scripting language.

      hello-world.js:

      #!/usr/bin/env node
      
      console.log("Hello world");
      

      Your favorite command line tool:

      chmod +x ./hello-world.js
      ./hello-world.js
      

      You just need to install npm, eg via apt-get install npm.

  • vocornflakes@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago
    1. Ubiquitous; insane amount of libraries and probably some of the best documentation of any language
    2. JS lambda function syntax is nice
  • SGG@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago
    1. It runs in browsers
    2. If you hate your co-workers, then they will also feel your pain.