• GnuLinuxDude@lemmy.ml
    link
    fedilink
    arrow-up
    25
    ·
    11 hours ago

    Vibe bros LOVE their useless animations and effects. There is this one website I found for doing Regexes called openregex or something. And just having that page open with nothing else going on slams your GPU. It looks ugly as sin, too. And if you go to wayback machine and see when that page first was created it actually looked relatively normal and fine.

    • Zarobi@aussie.zone
      link
      fedilink
      English
      arrow-up
      11
      ·
      9 hours ago

      When I was leaving a previous job, I watched my replacement put in a bloated as fuck .svg file embedded directly into the HTML… within that, was multiple base64 encoded uncompressed .png images. All to do a spinny animation you can whip up in 1 second with CSS transform transition. When I said that, they were confused because they didn’t even know what CSS is, they just use tailwind. Apparently writing your own CSS is firmly old school nowadays.

      There is zero cares about performance anymore, nobody gives a fuck. Phones are powerful, internet is fast. Yeah sure let’s dump in this 80mb bloated nesting doll abomination above the fold directly in the HTML so it’s never cached and downloaded every time and bloat the images by 33% because base64 does that. When I raised my concerns I was dismissed because it looked good. That attitude was part of the reason I was leaving. Most websites are awful div soup nowadays with 10 frameworks up their asses. The first thing I do when I help people with their code is delete 60% of it.

      Sorry, I still am upset by the direction the web dev industry was going.

      • Sonotsugipaa@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        9
        ·
        8 hours ago

        The salt on the wound is when people say “unused RAM is wasted RAM”, which is true, but often used incorrectly:

        “”“unused”“” memory is used by filesystem caches, and when an application allocates and writes 10x the memory it needs to, the OS cannot use it for caches anymore - thus wasting it.

        • GnuLinuxDude@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          5 hours ago

          100% this.

          If every software maker generalized the principle of unused ram is wasted ram, I would be allowed to keep only one program open on my computer. Because each application must consume all of it for… I don’t know. Showing me a webview of a text box that has a glowing ring for no reason or something stupid like that.

          This isn’t even getting into how cache locality in memory is a performance consideration, or how every software maker is EXTERNALIZING their costs onto users, making us buy more capable hardware to keep up with their software.

          All so I can do the same shit I did 10 years ago: send messages, view pictures and videos.

    • mystic-macaroni@lemmy.ml
      link
      fedilink
      arrow-up
      8
      ·
      10 hours ago

      Isn’t the whole point of regex to toil for 3 hours to write something very specific you will only ever use once?

      • Zarobi@aussie.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        9 hours ago

        Isn’t the whole point of regex to toil for 3 hours to write something very specific you will only ever use once?

        /((?!([es]))y)(?:.*?)((?!(s))e)(?:.*?)(s)/
        
        Tap for spoiler

        It’s a Regex that checks if the letters for the word “yes” exists within a text in order. I call it the yesnometer

          • Zarobi@aussie.zone
            link
            fedilink
            English
            arrow-up
            3
            ·
            8 hours ago

            Nothing is wrong with that, but it will give you different output. I tend to like using capture groups just out of habit, it makes it more flexible and useful in future. Most of my co-workers hated Regex so I tried to make it easy for them.

            I also wanted the letters to be as close together as possible. In this example it doesn’t matter, but in other texts it might. Yours will find the first y, then the furthest possible e, then the furthest possible s. So you might get output where there’s a y on line 1 and the e s at the very end of the text. Nothing wrong with that, it’s just not what I was envisioning.

            Also it’s funnier in this context to have a complicated regex.