The first one was portrayed in a clickbait "everything you know about electricity is wrong" way. There have been several response videos to it that lay out why it's misleading that explain it better than I can, but suffice to say that the lightbulb does not turn on immediately like he claims.
There second one takes a mathematical model for the path integral for light and portrays it like that's actually what is happening, with plenty of phrases like light "chooses" the path of least action that imply something more going on. Also, the experiment at the end with the laser pointer is awful. The light we are seeing is scattering from the laser pointer's aperture, not some evidence that light is taking alternate paths.
> There second one takes a mathematical model for the path integral for light and portrays it like that's actually what is happening
I know nothing about this. Is there a more accurate mathematical model available than the one he uses? Otherwise, I think it seems sensible to portray our best mathematical model as "what's really going on". And I didn't get the sense that light was "choosing" anything when watching the video, I got the sense that the amplitudes of all possible paths were cancelling out except for the shortest path (or something along those lines)
There are many equivalent formulations of quantum mechanics, the one the above post takes issue with is the path integral formulation. But because you can show an exact mathematical equivalence it makes all the same predictions as, for example, Hamiltonian evolution.
The words people like to use for the path integral is a sum over histories---that corresponds tightly with the ingredients in the path integral. So in this formulation it's what's "actually happening". But in other mathematical formulations other words are more appealing and what someone claims is "actually happening" sounds different.
+1 I would like to know too. Especially the experimental demo of infinite paths -- I'm a complete noob in quantum physics, and the video made sense of so many topics I "learned" in college but never managed to grok. It'd be good to know what the alternative explanation is.
Is there any sandboxing to prevent access from the SIM card computer to information on your phone? And if so, absent of some (admittedly not very unlikely) 0day allowing sandbox escape, what would a malicious SIM program be able to do?
And, hopefully your USB stack, or your phone's equivalent to SIM interface, doesn't have vulnerabilities that the small computer that is the SIM card could exploit.
Operating systems that center their efforts on protecting high risk users like Qubes dedicated a whole copy of Linux running in a Xen VM to interface with USB devices.
It'd be great if more information were available on how devices like Google's Pixel devices harden the interface for SIM cards.
One thing that people miss out on when they complain about guilding/awards is that being guilded or buying premium will credit your account with reddit tokens that you can use to guild other posts. So there's a chance the users are just using tokens that they have in their accounts already. I purchased premium back in the day to sync visited pages, and I have around 10+ platinum awards I can give out, a lot more if I use a cheaper award.
Thanks for clarification. I'm not really complaining, just found it amusing. Still using the awards looks a little like tacitly supporting the system, and I even wondered if they help the submissions in the algorithm (if so, gilding would make more sense in that case).
"Been moved" strongly implies that it wasn't his choice. Cutler worked on some really cool Virtualization problems in Xbox and is bringing that expertise to Azure as well.
One advantage of it being hardware specific is that I can move my keyboard between machines and not have to worry whether my shortcuts are available. Also, I believe tools can only register themselves so early in the input processing stack in the OS which can prevent you from having your macros/shortcuts available in certain applications. An example of this is for RDP in windows, where if you use fullscreen RDP, it will use the remote instance's keyboard shortcuts instead of triggering the hooks you have on the host. Having the shortcut in firmware makes your shortcuts resolve before even leaving the keyboard.
Of course, there are downsides to having it all in hardware as well.
