• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • It’s funny, I buy Apple Car specifically so that that I can’t decide where I want to go. At work we MDM and Apple’s approach isn’t for everyone, but forcing something like choosing their destination simply isn’t the right choice for all types of users.

    I’m all for encouraging them to be on the right side of Right-to-Repair, labor laws, and environmental best practices. But I left the world of thinking where I want to go and choice for the Apple Car’s tight lockdowns. At first I still couldn’t help myself but to try to go around wherever I wanted with my first Apple Car or two, then I stoped that also.

    Apple Car’s filtered possible destinations are all I need, so I don’t see why anyone would ever want to go any other place.






  • gornius@lemmy.worldtoLinux@lemmy.mlWhy do you use the terminal?
    link
    fedilink
    arrow-up
    2
    arrow-down
    3
    ·
    9 months ago

    If you know how to use git, you will know how to use docker (provided you know what you want to do). They are completely different programs, yet you can quickly grasp the other instinctively.

    Now, Photoshop and Blender - they are also different programs, but if you know Photoshop, you still need to relearn Blender’s interface completely.

    This is why I prefer terminal programs in general. Unless it’s more convenient to use GUi, i.e. Drag&Drop file manager, some git tools etc.


  • gornius@lemmy.worldtoSelfhosted@lemmy.worldShould I move to Docker?
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    10 months ago

    Learn it first.

    I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.

    Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.

    If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.

    Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.

    Thanks to that it’s trivial to host multiple projects using for example different PHP versions for each of them.

    And I haven’t even mentioned yet the best thing about docker - if you’re a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.




  • The difference between different generations of USB-A are speeds. If user notices differences in speeds, they are way more likely to know the difference between USB versions.

    The differences between USB-C and USB-A are capabilities. USB-C is already confusing for many people. My boss (IT Project Manager) thought he could use USB-C to connect his monitor, while he couldn’t because his laptop doesn’t support DisplayPort over USB-C.

    There is already a huge mess with USB-C capabilities. Some of them are just glorified USB-A ports, some of them have DisplayPort over USB-C, some of them are Thunderbolt (with different versions or course), some of them are QC (with different versions - once again).

    I can just imagine the confusion from users, who expect all of the USB-C ports in the motherboard to work the same way, but then only one or two ports from 8 total have DisplayPort capabilities.

    “If it doesn’t fit it means it’s not supposed to go here” is a great way to tell the user what capabilities the port has.



  • The apps still need to request OS for specific permissions before they use things like GPS, mobile data, filesystem etc.

    But the point you’re missing is unless you’re building everything yourself, there is always a party that you have to trust. Apple likes to paint itself as trustworthy when it comes to your data, but all the anti-consumer shenanigans they do when it comes to hardware clearly state that the only thing they care about is money.

    Remember - it’s either convenience with a false sense of security or security. Never both.


  • Why do you need Windows VM for developing GUI apps? Last time I used Visual Studio to make GUI app I almost gave up programming, because of how code-generation dependent it was.

    For C# you have AvaloniaUI. For cpp you have countless multi-platform GUI toolkits, same for rust, Java has its own toolkits (multi-platform), and finally you can make an Electron/Tauri app.


  • The way for your desktop to communicate with the hardware.

    It used to be X11 - A server-client architecture, which meant your desktop was effectively just a client that told the server what to do. The server was the one doing the drawing

    Wayland is just a protocol, defining how programs and desktop should communicate with each other - without a middleman that was X11 server. The desktop does the actual drawing here.


  • You just need to realize that Adobe doesn’t release their stuff on Linux, not because it doesn’t allow them to, but Linux desktop market share is too small.

    It’s a chicken and egg problem. Once Adobe would release their stuff, magically there would be a massive movement to improve HDR support, color accuracy etc.

    And you need to realize Microsoft achieved such a giant market share thanks to illegal monopolistic practices in 90s, that still have huge impacts today.




  • gornius@lemmy.worldtoPrivacy@lemmy.mlPlease, do not use Brave.
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago
    1. Chromium has tons of eyes on it, because it’s codebase for many other projects, such as Electron and any chromium based browser.

    2. Web integrity wasn’t discovered through chromium source code, but it was openly proposed by Google on separate Github repo, dedicated solely for that proposal.

    3. There are many shortcuts in your thinking that just the code being open makes it trustworthy. Every PowerShell malware technically has its code open, because it’s a script. But you wouldn’t open a random script from the internet, without checking what it does, yet you don’t apply the same logic to Brave. If you don’t check the source code yourself, you either need to trust an author, or third parties that “checked” the code.

    4. In addition to that, you’re probably using compiled binary, which means at this point you can throw that source code out from window, because at this point you can’t be sure compiled binary == source code.

    5. Due to the enormous amount of code, it’s really easy to obfuscate malicious behavior. At the scale of the browser it’s more efficient tracking outbound packets that program sends than examine source code.


  • gornius@lemmy.worldtoPrivacy@lemmy.mlPlease, do not use Brave.
    link
    fedilink
    arrow-up
    50
    arrow-down
    5
    ·
    1 year ago

    Brave behaving like Win XP era browser with gazillion toolbars installed, with a pinch of crypto and crypto promoting ads should be a giant red flag.

    FOSS =/= trusted by default. Why are there so many FOSS evangelists, but such a damn tiny part of them are programmers, let alone programmers able to examine a source code behind such a giant codebase as web browser?

    I use Vivaldi, at least their business model is clear, and developer is kind of trusted, and not crypto scammer and homophobe.