this post was submitted on 03 May 2024
995 points (97.0% liked)

linuxmemes

21198 readers
939 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 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, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Sanctus@lemmy.world 7 points 6 months ago (1 children)

    If they're that dumb leave the extensions on and let their eyes glaze over it like they would anyway. Hiding the extensions doesn't seem beneficial in any way.

    [–] RidcullyTheBrown@lemmy.world 7 points 6 months ago

    if you designed the system so that the extension is part of the functionality, then you have to hide it away so that your users don’t accidentally delete or modify the extension thus rendering their files useless (within said system)

    it’s a fundamental shell design flaw: one should never allow users to modify data critical to functionality. And it’s not something that can be changed because almost all applications depend on this