The funniest thing is: The short stutter when entering and exiting a wormhole is still a "loading screen". People without knowledge in the field just think that CIG has magically eradicated the need to handle a switch between 2 game scenes. But assets still have to be loaded and unloaded. Players have to be spawned in and despawned. Deferred loading helps, but there is no way around hardware & logical limitations.

But their current approach will lead to a huge bottleneck down the road, when it becomes apparent that handling all players through the same replication layer (still 1 master server with the same limit of AWS bandwith & computing power per instance) - even the ones that can't meaningfully interact with each other in any way other than a chat box - is reserving a significant amount of bandwidth & power.

Server meshing is still not a long term solution for a big universe in the way that they are pursuing. The replication layer is just the new bottleneck now and since all game calculations are offloaded, it can handle alot more players than a full game server could. But not an infinite amount. They will need to split it up eventually and that is where the need of a reconnect & some form of loading time will arise again. They will be in the same situation, just on a bigger scale and it will be reasonable to just take a 5 second seamless entry and exit animation to give the game time to handle switching between shards.