• 0 Posts
Joined 1 year ago
Cake day: June 9th, 2023

  • imagine you are watching youtube on this thing and when an ad shows up, you can’t look away, even if you try to they can track your eye movement and just move the window, you can’t mute it, you certainly cannot install adblock on it, you are forced to watch the ad until it satisfies apple

    WUT? Apple is very focused on privacy and the idea that a user can’t mute or install Adblock is… weird. Safari has good ad-blocking options as well as built-in anti-tracking features to protect users, applications can’t usually prevent the system from muting content and Apple doesn’t really sell ads outside of the App Store.

    If you want to worry about that stuff I’d suggest focusing on the Meta VR goggles or god forbid Google starts making goggles, both of those companies survive on ad revenue and have an incentive to enshitify their experience in ways that the Apple we know today would never do. Of course companies can change over time, but the ethic at Apple is to only make products they feel comfortable with their families using.

  • if you compiled some code and then uncompiled it you would get the most efficient version of it … ?

    Sorta, an optimizing compiler will always trim dead code which isn’t needed, but it will also do things that are more efficient but make the code harder to understand like unrolling loops. e.g. you might have some code that says “for numbers 1-100 call some function” the compiler can look at this and say “let’s just go ahead and insert 100 calls to that function with the specific number” so instead of a small loop you’ll see a big block of function calls almost the same.

    Other optimizations will similarly obfuscate the original programmers intent, and thinks like assertions are meant to be optimized out in production code so those won’t appear in the de-compiled version of the sources.

  • Historically, reverse proxies were invented to manage a large number of slow connections to application servers which were relatively resource intensive. If your application requires N bytes of memory per transaction then the time between the request coming in and the response going out could pin those bytes in memory, as the web server can’t move ahead to the next request until the client confirms it got the whole page.

    A reverse proxy can spool in requests from slow clients, when they are complete, then hand them off to the app servers on the backend, the response is generated and sent to the reverse proxy, which can slowly spool the response data out while the app server moves onto the next request.