• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle




  • Windows is an industry standard. And so is office. As long as we treat it as such. If we want things to change we have to go against such standards.

    The big difference between Office and Photoshop is: Microsoft opened their file format. And has support for open standards.

    Adobe locked their eco system down to build a monopoly. This is not gimps fault. It is 100% on Adobe.

    While the outcome is the same, I would love to see a different wording: nothing is an alternative to Photoshop, because Adobe has a monopoly.



  • I think some parts are just a question of perspective. I am not a GFX person. But I have friends that work in this field. One of them starter learning with gimp. And he constantly is ranting about photoshop at work. He claims the interface of PS is garbage, support for some obscure file format is not even there and so on.

    So, I think it depends on what your are used to.

    For the documentation: yes! And raw image support is an issue to. Mostly because of proprietary bullshit standards, but yes. This is missing.

    Does this make gimp to a shit software? No








  • There us so much wrong with this article. From installing a fucking browser via flatpack, over ignoring the fact that office 365 is a thing to the fact that there are alternatives to Adobe.

    Sure, not everything is perfect right now, and people have to learn new stuff.

    I have migrated multiple people to fedora in the last two years. And guess what, regardless of type or age of user, they had no troubles with it to this day. They use gimp, play, have browsers with password managers, and write office documents. Yes. MS office.

    Articles like this are one reason why people hesitate to make the switch. Doompainting, that’s all it is.

    And what the hell are you talking about vrr? Kde, sway and hyperland support it for years now under wayland. Gnome still does not have it, but that is gnome.

    And if more distributions would not per default use gnome, such misconceptions wouldn’t exist in the first place.




  • Sure, Firefox introduced a security feature: DNS over HTTPs. So instead if asking some DNS server that is configured on the local system, for the IP that belongs to a Domain name, am external service is asked via HTTPs.

    While this is in theory a good idea, and has some benefits, the Firefox implementation was bad:

    • the external partner was cloudflare. There where no additional informations out at that time.
    • there where no opt out option

    Users, that where forced into DNS over HTTPS could no longer resolve internal hostnames. This was a killer in office environments. And after the fix for that, everything was first submitted to cloudflare and only if cloudflare could not resolve the hostname, the local DNS server was asked, leading to potential information leaks. Also a no go for companies.

    Firefox has fixed these issues by providing privacy policies, the option to choose other DNS over HTTPS providers and the option to define what domains should never be resolved externally.

    But they lost trust in many professional environments because of that move.