this post was submitted on 13 Nov 2023

1268 points (97.7% liked)

Mildly Infuriating

35557 readers

1981 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.

Rules:

1. Be Respectful

Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...

2. No Illegal Content

Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...

3. No Spam

Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...

4. No Porn/Explicit

Content

-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...

5. No Enciting Harassment,

Brigading, Doxxing or Witch Hunts

-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...

6. NSFW should be behind NSFW tags.

-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

7. Content should match the theme of this community.

-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...

8. Reposting of Reddit content is permitted, try to credit the OC.

-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense

Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago

MODERATORS

[email protected]

1268

I just want to set a timer for MY FOOD WINDOWS WHY? (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

318 comments fedilink hide all child comments

why?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 20 points 1 year ago (1 children)

Plus Linux could update it in the background while the app is running. There's no reason windows can't do these things, and yet, it can't.

[–] [email protected] 22 points 1 year ago* (last edited 1 year ago) (2 children)

It can't, really. What Linux will do (and Windows won't) is delete old files and replace them with new ones while they are still in use. But this has two problems.

It can lead to stability issues. See e.g. Firefox, which refuses to open new tabs and can't shut down cleanly if you update using the package manager while the browser is running. If you replace a binary executable in use and it later tries to load a shared library dynamically, it will get an unexpected version of that shared library which can potentially lead to memory corruption. Similar problem if the program tries fork+exec itself to create more instances (like Firefox and Chrome do).
It won't actually update the running process in memory, so even if you install security fixes your system will still be vulnerable. To be safe after e.g. fixes to libc you really need to reboot your system, but most distributions hide this fact from the user.

Windows could certainly opt for a similar solution as Linux. They just chose a stricter and more reliable model for file locking, for good or bad. For what it's worth I personally prefer the Linux model, but that's because I know to reboot my system after updating it. I don't trust my dad to take that social responsibility so he needs to be forced.

[–] [email protected] 12 points 1 year ago (2 children)

Outside of the kennel a reboot is not necessary you just restart the app/service it’s really not rocket science.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Updating a shared library requires an understanding of which services (and interactive programs) use that shared library. There's a lot of room for mistakes. So while restarting specific services can be worth it for a high-availability server, for a desktop PC I find it easier and less error-prone to just restart the machine. If you are really keen to avoid going into POST you can use kexec.

[–] [email protected] 0 points 1 year ago (1 children)

You're wrong about everything

[–] [email protected] 3 points 1 year ago (1 children)

But... But... He explained in a very organized manner, so it must be true, right?

[–] [email protected] 2 points 1 year ago (1 children)

I am rubber, you are glue

[–] [email protected] 2 points 1 year ago

So you're a condom?