• shyguyblue@lemmy.world
    link
    fedilink
    arrow-up
    26
    ·
    13 days ago

    I always hated Dreamweaver, so no big loss.

    Fireworks, on the other hand, had the best compression engine in the game, even Photoshop dulled the colors on every “compress for web” job i threw at it.

    I started as a flash developer, don’t miss it since jQuery and the Green Sock Animation Platform does everything flash could do, but better.

    • kellyaster@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      13 days ago

      Dreamweaver, gaaaah. Hey, at least it was better than Frontpage, which took a much faster nosedive into enshittification after Microsoft bought it and ruined the absolute shit out of it. Slightly better. Like, it had its own shitty inline styling that would get tangled up in itself and you’d have to clean it up manually, but at least it wasn’t Microsoft styling.

      Yeah, Fireworks compression was great! There was a period of time where I only used it to export jpeg, Photoshop’s did suck in comparison.

      • shyguyblue@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        12 days ago

        Ugh, you just unlocked a core memory: Every element is assigned a class, but they are unique to the element, thus defeating the whole damn point of the class functionality?!

        • kellyaster@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          12 days ago

          Oh jeez, it’s coming back to me now. Yikes, what a terrible use of classnames. I’m sure they thought they had a good reason for it, but to me it’s kind of a failure of a feature implementation if most of your userbase ends up not just ignoring it but outright deleting it because it’s useless to them and just creates clutter.

          Dreamweaver did have one saving grace. It had this code editor cleanup mode that removed empty and redundant tags, and at one point they added a neat option to remove Word document tags! From what I remember, it was pretty accurate and helped clean up a lot of shit. Unfortunately, it was unable to clean up code that it created itself.

          • shyguyblue@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            12 days ago

            Ahhh! I had a client a hundred years ago that did a “save as webpage” from a Word doc and wanted me to clean it up… I’m like, “it’ll be easier to throw it out and start over”, so that’s what i did. Then i charged her for the time it would have taken, had i bothered to try and clean up the code. She was happy to pay it!?

            • kellyaster@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              12 days ago

              Argh! Yeah, sometimes it’s better to start over than try to fix it. All those weirdass classes and bizarrely nested divs, screw that hahah

    • ByteOnBikes@slrpnk.net
      link
      fedilink
      arrow-up
      1
      ·
      12 days ago

      Funny story: around the mid-2000s, my boss at the time moved me off of web development because his teenage son was really good at Dreamweaver. I was in my 20s, losing my “Webmaster” job to a young whipper snapper.

      It was my first wakeup call that young people can always replace you.

      Btw - Not shitting on the kid either. He was pretty smart and honestly, I was a really crappy web developer in that era.