ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Star Trek: The Star To Every Wandering: Thoughts and Analysis on Temporal Physics and Parallels

Updated on April 10, 2017
1701TheOriginal profile image

Leonard Kelley holds a bachelor's in physics with a minor in mathematics. He loves the academic world and strives to constantly improve it.

Source

I frequently find that books I enjoy have a low-presence in online discussion groups for various reasons. Many places do exist but they usually fade out fast and don’t generate deeper debate on the novel in question. Instead, many reviewers are out there that don’t always analyze and investigate the aspects I notice. It is my intention to act like a review and an analysis of key portions of The Star to Every Wandering in the hopes of inspiring new thoughts into this 40th anniversary celebration of Star Trek and perhaps give you new insight into this novel. Will it wander around? Probably. It will also contain portions I loved and hated as I try to weave together some coherent thoughts on The Star to Every Wandering. Plus this is a Kirk story, so portions of him that are relevant in the other Crucible Trilogy novels will be brought here.

Kirk and Pike.
Kirk and Pike. | Source

Parallels and Echoes

One of my first thoughts reading this book was the parallel it establishes between Kirk and Pike, where both ended their lives in an illusionary reality and also with deep pain over an incredible loss. Kirk’s was a loved one while Pike’s was a physical freedom, but Pike ended his life with the Talosians and Kirk with the Nexus. Both are illusions of what we consider reality. Is this meant to be the fate of Kirk? Doesn’t he deserve a rest or should he be committed to a life of saving others but never feeling like he himself is redeemed, which he could get in the Nexus? DRGIII makes sure Kirk gets a better deal than either of these as we find out in the book’s conclusion.

But that was not the only interesting parallel with Pike in the book. The Mojave Desert is once again used as a confrontation between reality and fantasy, just like in “The Cage.” In this case, Kirk confronts Kirk Echo in a stand for ensuring the converging temporal loop (more on this soon) is prevented. Here, we really dig into how the temptation of the Nexus caused his Echo to appear after Kirk left it. But that makes one wonder…does everyone entering the Nexus gain an echo each time they leave? Kirk ends up working with the Picard Echo briefly and we know about the Guinan one from “Generations”, so could an army of Echoes be released some day? Hmm…

This brings me to my next point of discussion. What is the deal with the Echoes of the Nexus? Like many plot points of that realm, they are arbitrary and seem to fit the story’s needs rather than follow a reasonable and consistent set of rules. Guinan implied that an Echo couldn’t leave the Nexus if their counterpart was already outside the Nexus. Yet that is exactly what Kirk does in this book, but to be fair only he could actually perform his plan of stopping the converging temporal loop and so he couldn’t ask different Echo to leave. Maybe Guinan stated that one couldn’t leave because she was afraid of creating a converging temporal loop? But two Kirks were present in 2293, one an Echo and the other the “original”, and presumably that Echo was not in possession of the same (any?) M’Benga numbers mentioned in Provenance of Shadows and thus eliminated the converging temporal loop, so what stopped Guinan? Something isn’t consistent here or I am missing a detail.

The Nexus approaches.
The Nexus approaches. | Source

Physics of the Nexus and Time Travel

Who found the physics behind the converging temporal loop? If you said DRGIII then you pay attention to reality. For those that are future bound, it was Spock, after his successful Kolinahr in The Fire and the Rose. Keep in mind that the physics for this are not even remotely known, but go with it people because its science fiction! If two sets of chronitons and chronometric particles were to exist in an identical space-time, then instead of an infinite amount of energy at a single point (as the equations Spock found seemed to imply implied), the sets of particles would meet each other and the energy dispersed via the destruction of everything between them via some method of connection (of which Spock feels is an unlikely event but as we see happens). This seems to be a huge metaphor for life events of the past coming back to wreak havoc on the present, and we usually have to find some way to disconnect or cope if we want to function. Through the actions of this book, Kirk is able to accomplish a disconnect of sorts but in a more literal way. However, I think it helps him cope for sure and possibly move on from the traumatic event, but like many instances in life they can come back in an explosive manner.

Now, the plot of this book has two basic goals for Kirk: preserve the timeline and prevent the converging temporal loop. But did the timeline really stay the same as he did this? I argue it couldn’t have, for Kirk Echo took actions that were never done in the original past. He reactivated his commission early to get aboard the Enterprise-B, he was likely spotted by public surveillance equipment, and he interacted with Enterprise B crewmembers (especially the “non-essential” bridge personnel). That being said, the Echo did take many steps to try and preserve as best as possible, such as replacing objects and moving at low-traffic chances, and also noting shuttlecraft missing and places of damage to the B in an attempt to take something that wouldn’t be noticed. So, it’s possible, but not probable.

But it gets worse as the ending of this book unfortunately presents problems with believability (I know, sounds weird for a science fiction novel). In the span of 10 pages DRGIII manages to get sloppy and rush things without digging deeper, and I know for regular readers of his work that will sound ridiculous. But would Picard really work with someone claiming to be Kirk without having that Nexus experience, something this Picard never had in Kirk 2’s new timeline? Could he just accept a time traveler from out of nowhere? And because of all that, why did Kirk 2 need to say exactly the same dialogue Kirk 1 used? They wouldn’t have the same context as in the past and were not required to preserve the timeline. But it gets worse, for those of us versed in temporal mechanics will shout about Kirk 1. He now has never entered the Nexus after the actions of Kirk 2 so how could Kirk 1 enter the Nexus and allow the Echo to exist to start the change, much less end up back at the Guardian of Forever? Despite how awesome it would be for Kirk to be still hopping around the galaxy and free of responsibility, it remains a large plot hole. Maybe this was all just a dream before death arrived…

The Possible Order of Events

Favorite Moment

One of the highlights of the book was the moments before Kirk 2 goes into the Guardian to help Picard out. Kirk 2 has just finished watching Picard’s life and is about to ask the Guardian to play again to enable the jump to 2371 but then asks to see the lives of many people close to him like his parents, Spock, Bones, Antonia, and so on. He sees their entire lives. Imagine knowing you were essentially saying goodbye to your closest friends and family members and were given a chance to see their full lives including their deaths? Would you want to? But then he finishes with the life of Edith, something he avoided to dwell on up until the end was near for him. This final embrace is him acknowledging that when he goes to help Picard he will likely die, just like the Echo conveyed to him, and so he wants to spend some of his last moments by seeing those moments with Edith that Kirk considered perfection. And Kirk did all of this for himself, a rare moment for the man who sacrificed so much over the years we have gotten to known him.

© 2017 Leonard Kelley

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)