• 2 Posts
  • 3.42K Comments
Joined 1 year ago
cake
Cake day: September 21st, 2023

help-circle






  • Changes by shitty apps wanting to start with windows and register for context menus.

    I’ve had windows machines run fine for 10 years, and some having trouble at 6 months. The difference being the problematic machines I’ve made tons of changes, installed tons of risky apps.

    I’ve also run registry cleaners as a test, and it’s made a world of difference.

    In short: crappy apps make windows run poorly.



  • Fear of change? Hahahahaha

    No, I just know what’s involved, with the unpredictable “gotcha” a year from now.

    Not to mention the knowns. Holy hell switching from Windows to Linux is very problematic for typical end users. Yes, the UI is that different, even with “friendly” distros.

    You say your grandma made the switch? OK, so someone who uses a browser for everything and doesn’t actually use office.

    Let’s see Libre office open an excel spreadsheet with tables.

    Or edit a word doc and send it back and have it not be screwed up.

    Not migrating is practicing risk mitigation. Hell, I can’t change a single setting on work systems without validating that change in the lab first. And you want people to switch entire operating systems. For what?

    So stop this fear projection nonsense.

    (And I work with Linux every day on multiple distros).






  • Well before.

    And “refuse to change their ways” - are you going to underwrite the project to implement a transition and hold all the liability for the risks?

    Its not like changing systems is just a click of a button, this is an extensive project, that you better get right or you’re dealing with records going the wrong way, potentially having serious life and safety implications.

    Plus, you have to maintain this legacy fax system because not everyone else has migrated to something new. So for the remainder of your career, it still doesn’t go away, and you’ll have to continue to pay for its maintenance.

    Companies have systems they’ve built up over years, that works. They’ll move forward as it makes fiscal sense.


  • “embedded in many workflows”

    Key statement right there.

    And once people see what that really means, and what it would take to move past it (including time, cost, and risk), they may start to understand. You’re dealing with it first hand, so you know what’s involved.

    It became the de facto way to send stuff with high confidence it went to the right place. Then tech addressed the paper-to-paper over one phone line issue with modem banks into a fax server. So all the same fundamental comm tech (so fully backwards-compatible), but a better solution for the company with that infrastructure. Such a company has little motivation to completely change to something new, since they’d have to retain this for anyone that hasn’t switched. Chicken-and-egg problem, that’s slowly moving forward.

    It’ll be a long time before it’s gone completely. Perhaps in 20 years, but I suspect fax will still be around as a fallback/compatibility.






  • BearOfaTime@lemm.eetoAndroid@lemmy.worldGraphene vs LineageOS what's the diff?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Graphene is technically more secure than Lineage, because you can re-lock the bootloader.

    But wait, the latest versions of Lineage you can re-lock the bootloader on Pixel devices (or is it with DivestOS, a Lineage fork, on Pixels? I forget). Either way, both can be re-locked on Pixel (I know, I’ve done it).

    At that point there’s little difference in my opinion, if you aren’t using any kind of Google services.

    Once you go to use Google services (either sandboxed on Graphene, or microG on Lineage), it can be argued that Graphene is more secure. Though Lineage and Divest install microG as user apps, so you could install them to a second profile and isolate it there.

    But if you’re going to run some form of Google services, you’re kind of negating the advantages of Graphene at that point (though some would argue it’s still more secure, again, depending on your threat model - if a state actor is after you, don’t go putting Google stuff on your phone).

    Really it all comes down to your threat model. I’m currently running DivestOS on a Pixel with microG, because there were a few apps I still needed. My next reset (in about 3 months) that will be gone, and I’ll no longer need anything Google. But I’ll probably stick with DivestOS, as there’s no clear advantage for me to switch to Graphene.