• 0 Posts
  • 48 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.








  • 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.


  • gornius@lemmy.worldtoProgrammer Humor@lemmy.mlPHP is dead?
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    The language itself is not that bad. Especially the newest releases are really great, thought out DX improvements. What stinks are its legacy parts and how it needs to be run.

    My biggest pain is that for it to actually behave like it should it requires some sort of an actual web server like apache or nginx.

    Also, servers written in are actually request handlers - every time a request comes, the whole app is reinitialized, because it just can’t hold its state in memory. In many apps every request means reinitializing connection with database. If you want to keep some state, you have to use some caching mechanism like redis or memcached.

    Also had one time when Symfony app was crashing, because someone forgot to close class braces, and everything was “working” until some part of code didn’t like it and was just dying without any error.

    And one time when someone put two endlines after php closing tag at the end of the file, confusing the entire php interpreter into skipping some lines of code - also without warning, and only in specific php version.


  • 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.




  • Lockfile contains exact state of the npm-managed code, making it reproducible exactly the same every time.

    For example without lockfile in your package.json you can have version 5.2.x. In your working directory, you use 5.2.1, however on repo, 5.2.2 has appeared, matching your criteria. Now let’s say a new bug appeared in 5.2.2.

    Now you have mismatched vendor code, that can make your code behave differently on your machine, and your coworker’s machine, making you hunt for bug that wasn’t even on your side.

    Lockfile prevents that by saving an actual state of vendor code.