"...our understanding of the laws of physics is advanced enough nowadays to describe almost perfectly everything we observe in everyday life." -- nope.
short summary: Quantum teleportation works by taking advantage of entanglement. To teleport a quantum state, you prepare a source qubit and another pair of entangled qubits. One of the pair is sent to your teleportation destination. You take your source qubit and interact it with the one remaining entangled qubit. (this interaction depends on the paradigm of quantum computing you are using, i.e. apply a Hadamard gate to the photonic system) Once you have performed the interaction, you can measure the destination qubit and its state will inform you of the original state of the source qubit. The destination qubit can be arbitrarily far away, thus "teleportation" has occurred.
This new thing in this study is that they use a "hybrid technique" to increase the efficiency of this transformation over 100x. With older techniques, the teleportation transformation occurred according to a probability distribution such that transport fidelity was not always high. This new technique apparently surpasses that barrier so that the teleportation is correct each time.
Your use of the language "passed up to the outside" is interesting... Up and outside imply some sort of intrinsic directionality. Considering that functional programming seems to capture the mathematically inclined, can anyone speak to the concept of topology applied to code structure or interpretation? For instance, does a closure imply some sort of filtration structure on the "code space?" (by filtration here, I mean the concept from algebraic topology)
To clarify, when you say RESTful API, do you mean the client-side MVC framework issues API calls to a server which then updates the backend (database?).
I guess this model is client-centric while the typical Rails app is server-centric (MVC logic executes on the server and then serves the relevant HTML/CSS to the client).
Any particular advantages to the client-side framework over the server-side framework?
For the uninitiated, could someone please explain what we use Ember (and related frameworks like Angular.js) for?
For example, I build a Rails app to handle models, views, and controllers on the backend. Then I can use HTML/CSS/JS to write a frontend to interface with the Rails app. Why do we need another MVC framework on top of Rails?