this post was submitted on 29 Jul 2024
401 points (99.5% liked)

linuxmemes

23285 readers
245 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    401
    Shit, it's how I feel after contributing 1 line of code to fastfetch (sh.itjust.works)
    submitted 7 months ago by [email protected] to c/[email protected]
    27 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 17 points 7 months ago (4 children)

    These days id prefer a developer produce negative lines of code without breaking anything.

    [–] [email protected] 18 points 7 months ago

    As experience tells me, every program contains at least one bug.

    Experience also tells me, that you can remove the buggy line of code and the program will still not work as intended.

    From this follows, that every program can be reduced to a single line of code that doesn't work as intended.

    [–] [email protected] 5 points 7 months ago

    I want to roll back my commits, not make more!

    [–] [email protected] 2 points 7 months ago

    Wasn't there a kernel release a few years back that actually resulted in less code? Or at least at some huge part?

    [–] [email protected] 2 points 7 months ago

    I saw it put really well the other day. Any software has in general a set number of bugs per lines of code. Something like Debian the number of bugs goes down after release as only bugfixes occur, while anything constantly moving like a rolling release, is certain to grow in number of bugs as the less tested newer software (which generally includes more loc) is pushed. There are tradeoffs to both methods, and edge cases of course.