I am a front-end developer who is FED up about front-end development. If you write front-end, this isn't about you personally. It's about how your choices make me angry. Also this is about how my choices have made me angry. Also this is mostly just about choices, the technologies are incidental. Note: The views expressedRead More

Too good NOT to share.

My brothers and sisters in Christ I want you to know that I care about your souls enough to share these truths with you:

  • You don’t need JavaScript to make a web page.
  • You don’t need JavaScript to write styles.
  • You don’t need JavaScript to make an animation.
  • You don’t need JavaScript just to show content.
  • lowleveldata@programming.dev
    0·
    5 months ago

    No we don’t need it. But is it better if we use it? Like, you don’t need OOP for implementing literally anything either.

    • magic_lobster_party@kbin.run
      0·
      5 months ago

      When you hold a hammer everything looks like a nail. Just because it’s useful in some cases doesn’t mean it’s always the best solution.

      The article mostly rants about front end devs using unnecessarily complex solutions for simple problems. Like using React for generating static web sites.

      • mamotromico@lemmy.ml
        1·
        5 months ago

        I get what he means and in most points I agree (I’ve worked primarily as a front end dev so far in my career), but as you get more familiar with these frameworks they tend to be so much faster to iterate on compared to a more “cleaner” setup. I’ve seen plenty of situations where using such frameworks were clearly overkill, but were still much faster to setup and were ready to be expanded on if needed in the future. Everything about the package ecosystem on web dev he’s 100% on point though. Things like the left pad situation are insane.