• 0 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle


  • bisby@lemmy.worldtoLemmy Shitpost@lemmy.worldsoda
    link
    fedilink
    arrow-up
    58
    ·
    19 days ago

    Things in favor of Peyton here:

    • Corporations in general
    • There is no rule against it
    • 7-11 has a pretty regular event where “fill a silly cup, feel free to be absurd” is a thing, so there is precedent
    • That amount of soda is still probably profitable for the company, fountain soda is incredibly cheap
    • This isn’t regular consumption and clearly not a regular occurrence, if beverages were regularly freely available, it wouldn’t be exciting to do this and this type of behavior would go away – you have to hoard service when public service is an artificially limited quantity.
    • This didn’t deprive any other customer of soda – the only downside here is a corporation losing a few cents of profit.

    Things against Peyton:

    • Hoarding is a bad mentality to be in (agreed with you here)
    • It will take days to drink that much soda, and it will be flat and nasty

    When poor people get a windfall of money, they tend to spend it all. It’s why lottery winners tend to wind up broke. Because historically, money is a “use it or lose it” for those people. If you’ve been trained your whole life to adapt to things, it can be hard to do the right thing when those things no longer hold true.

    Americans cant have decent public services because they abuse them… results in Americans desperate for public services… which results in Americans taking extra advantage of any public service that is available… which results in a mindset that Americans abuse public services… which results in less funding… Its a vicious cycle.


  • It’s not a sensory issue - I just like wearing socks.

    This part feels like you talking about yourself, and everyone agrees.

    Not everything needs to be pathologized.

    People are taking this as an assertion that sock preference should not be pathologized and cannot be related to ADHD.

    Clearly not what you meant, but the phrasing you used is ambiguous enough to not differentiate between “not everything about myself is pathologized” vs “please stop pathologizing everything”



  • You don’t have to have been a slave to have dealt with racism. Enough people still get really excited about their confederate flags that clearly the era is still heavily topical.

    The word “confederate” means nothing beyond referring to a type of government, but when I hear it, I think immediately of the American civil war. Even though that ended in 1865 so I was never alive to witness that.

    That’s not how word associations work.


  • Yeah. theres a fine line between advocating for positive change because it’s the right thing to do vs because it makes you look good. Theres a fine line between being an ally and empty virtue signalling, and those things may not look different within the scope of a single interaction. It can sometimes take a bit to understand if someone is genuine or just performing.


  • bisby@lemmy.worldtoProgrammer Humor@programming.devmaster vs main
    link
    fedilink
    arrow-up
    52
    arrow-down
    3
    ·
    25 days ago

    The point of political correctness is that it’s always things you’d never consider… but someone else does. I’m not here to say whether things are right or wrong or if “master” is good or bad. but you perfectly highlight the reasoning behind it.

    To you, the only thing that comes up is the technology context. And that’s perfectly reasonable. To someone else, the unrelated slave owning context may just be tightly coupled with that word, and that immediately comes to mind when they hear the word regardless of context. And someone in that scenario is probably not having a positive correlation with the word.

    So a group of people have a very understandable reason to have a negative correlation with the word, and it’s super easy to use a different word, so it seems to make sense to just use the other word.

    All my git scripts these days have a $(git remote show origin | sed -n '/HEAD branch/s/.*: //p') in them, which just fetches whatever origin calls the head branch. so if I want to rebase from main/master/prod/lead/front/etc … the command will figure out which one to use for me.






  • Not detecting case fans sounds like it would be not communicating with the motherboard properly. Unfortunately every specific motherboard is going to have it’s own unique set of constraints. But generally this is all handled through “it87” i believe? But it87 can sometimes take some nonstandard params.

    Here’s an example gist of instructions for getting things working on one specific motherboard. https://gist.github.com/bakman2/e801f342aaa7cade62d7bd54fd3eabd8

    The wifi7 on my motherboard causes kernel panics pretty regularly, and the RGB isn’t properly exposed so I cant control(/turn off) any of the lights. Usually these things work themselves out with time as drivers for the new/nonstandard chips make their way into the kernel/libraries.



  • I think this is just a “person” thing sometimes. It is very commonly recommended in a lot of fields that if you are stuck on a problem, to stop what you’re doing and take a walk and often your subconscious will continue processing the problem, and you will view the problem differently when you get back to the problem.

    How that may play out in your emotional/shock examples may be different. But processing things while not “actively” thinking about things is something everyone does.



  • Yeah. In college world, one needs to be prepared for the school to not care at all and declare that it is the student’s responsibility to make sure any required software runs on their machine. And college can be a hectic stressful time, so finding time to be able to get things working on Linux may not be worth it. Having the Windows escape hatch ready is very important to be able to not lose your mind while on a deadline.


  • I’m not raging and I’m not even saying that Debian is bad. I’ve just been told MANY times over the years (including on Lemmy), when I’ve commented about bugs and issues I’ve had on Debian, that stability doesn’t mean “without bugs, always upright” it means “not moving, not changing.”

    Debian has a very specific use case. And when people say Debian is stable they mean the base platform isn’t going to change under you and suddenly a config file doesn’t work anymore because Package v2.0 uses a different format.

    This is good for people who want a low maintenance system that won’t unexpectedly break due to a random Windows update.

    This is good for probably the vast majority of people that fall under “normal” computing habits. If there was a major groundbreaking bug that affected everyone, it probably would have been caught in testing.

    This is not good for people who have quirky computing needs or otherwise do things in slightly niche ways, IF a bug shows up. Some bugs are minor annoyances, some require different workflows to get around.

    But ultimately, people should know that if they are experiencing an issue with Debian, and it’s not just a configuration issue, they either need to have a solution for themselves (recompiling), or switch distros.

    I personally stopped using Debian for my desktop around linux 3.16 days, but I do still use it for my home servers (where I don’t want to be updating things constantly). If Debian works as a desktop platform for you, that’s awesome.

    But OP was having issues with Debian. So OP should know that due to Debian’s unchanging nature, it will be quite a while before things start working. And they shouldn’t expect otherwise. And that’s ok, their use case is going to just be a bit more bleeding edge.


  • Ok? “You only have to wait a few months for this crash to be resolved.” still doesn’t resolve people’s issues.

    “Fix playing of custom alarm sounds” doesn’t sound like a severe issue to you, but it was also something that if someone needed, they were forced to wait a few months.

    Debian would rather have broken custom alarm sounds for several months, even if it was fixed earlier. Fixing a bug to me lands closer to a security issue than “shipping bleeding edge feature sets”.

    It ultimately means if something you need is broken for a non-security reason, it is not being fixed until the next point release. There is a fixed unit of time in which you know your problem will not be resolved.

    Packages are individually updated for security fixes. Individual packages are NOT updated for bugfixes.


  • I’ve been told plenty of times that when I had bugs that weren’t getting fixed that “stability means no unexpected changes, not uptime, compile the package yourself if you need it fixed.”

    There are plenty of examples of upstream projects asking debian to not package their stuff because they get bug reports for things that were fixed months ago.

    Debian does not ship bugfixes. Debian only ships security fixes.

    If something works, it’s not going to break. But if something doesn’t work, it’s not going to unless you fix it yourself by going outside of the official packages.