43
What's the point of lightweight code with modern computers? (liam-on-linux.dreamwidth.org)
submitted 11 months ago by to c/programming@programming.dev
28 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 11 months ago (1 child)

I think it really depends on what your code is doing. I do agree that less isn't always faster or as they mentioned in the post, safer. Taking a raw input is fast, but not very safe for a variety of reasons. I personally make "simple to understand" as the highest priority for my code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 11 months ago

    On a slightly different example, the suckless project has a huge emphasizes on lightweight code, which they call "suckless". I don't think in this case faster is the goal, but having less code and be simple as possible (not even configuration files allowed, you just recompile program) and almost no documentation in the code either. But the idea is the same, of having "lightweight" code.

  • permalink
  • fedilink
  • source
  • parent