862 karma · joined February 15, 2011
My understanding with the suspend/resume stuff they've talked about for the Deck is less about actually suspending/resuming the game by syncing some low-level state like memory or graphics, and more about quickly syncing save games via Steam cloud saves.
I only had a quick look over their docs when the Deck was announced and from what I could tell you basically opt into a new system-level save behavior where at any point the Steamworks library can tell the game "this device is going to suspend now, save your progress" then another computer can start the game and immediately load up the save file, giving the impression of seamless suspend/resume.
So as long as your save game files aren't OS specific in some way there's no reason why this should lock you into any specific platform, Windows or otherwise.
Take Chrome for example, where there's roughly an update every 60 days and the option for them to push out security fixes quicker.
Imagine having to wait for an operating system update (major or minor version) to just get the latest secure version of Chrome. That's pretty much where Safari is, especially on iOS.
Don't get me wrong, I think Safari gets a lot of unwarranted hate and it can certainly be a bit quirky here and there, but if they didn't have to wait for the next major/minor release of macOS/iOS to update Safari I think it'd be in a much better place.
I hope some point in the future Apple untie Safari from macOS and iOS so they can be updated independently without having to wait months to operating system updates to come out..
https://svelte.dev/docs#3_$_marks_a_statement_as_reactive
Is Svelte doing something clever with these labels at runtime, or is it just using the label to do some kind of transformation when the javascript is compiled, anyone know?
I only realised when I finally got fed up with my terminal taking several seconds to start, I dug into why and found that my $PATH had something crazy like >1000 items with the homebrew path taking up pretty much all of them.
Presumably the HTTP request that gets sent when you save an image sends different Accept headers.
Doesn't seem to work all the time, but presumably thats down to a combination of different Cloudflare settings, origin server configuration and what format the original image were in too.
I know in compact mode it's similar to how it was previously, but knowing that's now hidden away and unsupported doesn't exactly inspire confidence it'll stick around for long…
It's probably just a convention they use in the source code that's made its way into the JSON by serializing something? Either that or old habits die hard.
At first glance it probably doesn't sound like a problem, I get it's effectively the same as serving them from Google, but I know fonts can also sometimes have strange licensing requirements… so I always figured it was safer just to avoid it entirely.
I don't think I've ever actually checked, but I always assumed valid CSS property names can only be alpha-dash strings.
Say for example someone setting one up on someone else's phone (without their knowledge) to run every X minutes and using it to track someone's location, without them ever knowing about it.
I'm not entirely sure that's the real reason behind these notifications, but it does seem plausible.
You can now also long press the wifi icon (twice) from the control centre in iOS 13 to quickly switch wifi networks without going into the settings app, you can also do the same with the bluetooth icon.
A lot of this stuff is really hard to just discover though if you're not already aware it exists to begin with.
I suspect most slider captcha's out there are doing something similar or at the very most setting a hidden field to "true" or "1" etc. Very few are probably fingerprinting your mouse/touch movements to actually validate you're a real human being.
[0] https://github.com/kthornbloom/slide-to-submit/blob/master/j...
https://github.com/dshafik/php7-mysql-shim
It won't be 100% perfect and it's definitely not something I'd want to use long term, but it can help with the initial migration to PHP 7.
The setup was a little bit fiddly to get going, but I'm now super happy with it. As a sidenote, it was interesting to see how effective uBlock Origin already was because I thought the Pi Hole's blacklists weren't working at first!
*I imagine I'm not catching every single one of the DNS lookups on my network, but I bet it's now a large percentage of them.