It is not accurate to claim that frameworks automatically make programmers bad. In fact, frameworks are powerful tools that can accelerate development, promote best practices, and facilitate code maintenance. However, it can be argued that overly relying on frameworks without understanding the underlying principles of programming may have some negative effects. Here are some reasons why this might happen:

    • Carighan Maconar@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      10 months ago

      Because that’s the alternative, anyways. People love to pretend that’s not going to happen, but of course we all do that. Nothing as cool as building your own little meat framework.

      Of course, by the time you leave, it’s an undocumented nightmare that has 15+ calls for every single functionality, is so abstracted it’d make my Math professor blush and has more security holes (that no one even has a reporting mechanism for) than all the frameworks you could end up using together.

      (Still love writing my own stuff! 😅)

      • sheogorath@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        10 months ago

        I use it as a learning tool. When I was making my own framework it forced me to learn all the intricacies of the thing I was making the framework off. TBH it never saw any use in a project but the process of making it is a huge learning experience for me.

    • insomniac_lemon@kbin.social
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      10 months ago

      As someone who wanted to use an engine, I tinkered with a framework for a bit and immediately found myself in the beginnings of creating a framework for said framework.

      And they almost got away with this obvious scam, but unluckily for them I didn’t want to do stuff like that. They might’ve pulled it off if the particular thing I wanted was more straightforward.