Random Thoughts – Randocity!

WordPress Review: Gutenberg Editor

Posted in blogging, fail, writing by commorancy on June 11, 2020

This will be a no hold’s barred review of using the “new” Gutenberg editor in WordPress.com (and WordPress of any install). Let’s explore.


Several years ago, WordPress introduced the then “new” Calypso editor. It had a blue-ish color style and was a straight up type of no-frills editor. It had some flaws, to be sure, but it worked well.

About 2 years ago, along comes the newest new editor named Gutenberg. This editor was thought to be intended as a what-you-see-is-what-you-get (WYSIWYG) editing experience. Well, let me just say straight up and flat out, it isn’t. Yes, this review will be very critical of this editor. I generally refrain from reviewing my blogging platform, but in this instance I felt compelled and justified to review this editor and its massive set of usability and ergonomic flaws.


Several years ago, the Gutenberg project started. This editor was intended to be the eventual replacement for Calypso. ‘Eventually’ has arrived and the hour for replacement is at hand. Yet, Gutenberg is still not yet prime time ready. It is so far from being prime time ready, I can’t even adequately justify how badly it isn’t ready. Where Calypso had some flaws, these were easily overcome with a small amount of fiddling.

With Gutenberg, fiddling takes minutes at a time (and many times way longer) and sometimes there aren’t even ways to address the problems inherent in this new editor.

Let me start by addressing Gutenberg’s positive features before I get down into the nitty gritty problems with it.

Gutenberg’s Benefits

I want to make sure to cover both the positive and negative sides of the Gutenberg editor so that I’m not called out for unfairly representing this editor. With that said, let’s get going. Gutenberg’s positives include:

  • Block editing capabilities
  • Some additional text styling options (superscript, subscript, etc)
  • Not much else of note.

Block editing is pretty much where Gutenberg’s positives end. Block editing doesn’t greatly enhance the blog editing experience and, at the same time, Gutenberg adds an unnecessary layer of complexity to Calypso’s formerly simple editing design.

What does block editing do for the blogger exactly? It allows you to more easily move blocks around within an article. That’s pretty much its claim to fame. Though, I don’t see how that really buys much when most computers today offer copy and paste capabilities that allow this same functionality through drag, highlight, cut and paste. The fact that they spent gobs of time designing a new editor solely to solve a perceived copy-paste problem (that doesn’t really exist) speaks volumes of this editor’s design goals.

Gutenberg’s Drawbacks

There are many. First, the width of the editor is too narrow. Calypso had an editor width far greater than Gutenberg. This means that Gutenberg is not in any way a WYSIWIG design. Second, you must still preview your document… which in and of itself says that Gutenberg is NOT a WYSIWIG design.

Basically, Gutenberg’s team redesigned an editor for no reason at all. It was simply a new design to be a new design, but not to solve any actual editing problems. In fact, they’ve introduced new problems where in Calypso’s editor they didn’t exist.

For example, the bottom status bar in Calypso showed us the word count and other pertinent document information front and center. We didn’t have to click into or move our mouse to get to this information. Yet, in Gutenberg, this information is now hidden behind an icon that 1) makes no sense and 2) now requires active effort on the part of the blogger.

The block editing system also fairs just about as well (or not, depending on your point of view). There are a number of block types like paragraph, heading and image with an additional array of way lesser used block types like Star Rating, Highlighter, Quote and Pullquote.

As I said, the team has made this editor unnecessarily more complicated without the need to be this complicated. A text editor, in fact, should be much more simple, friendly, fast and easy. Many of these functions were handled in Calypso more elegantly, by highlighting text, then clicking to apply an attribute to that text. Basically, 1-2-3. In Gutenberg, you have to create a new block type by clicking many times, then placing that specific text into that block type.

Whoops! You chose the wrong block type? There’s almost never a way to convert from one to another. You must copy the content out, create a new block, and paste it in. Even then, sometimes copy and paste won’t work.

So, here’s where the block difficulties begin. Because blocks are now discrete elements within the body of the article… think of them as <div></div> sections, it’s difficult to get exact placement. In fact, trying to style any of these blocks using inline CSS is almost impossible. With Calypso, the text was straightforward and could be easily styled within the body of the article. In Gutenberg, if you want complex style options, you’re forced to use the Classic Block, which is effectively most of Calypso in a block. By being forced to use the Classic Block, you’ve pretty much negated the reason to even use Gutenberg in the first place.

That’s not to say you can’t style within Gutenberg, but it’s more about what happens after you do it. When you go into the HTML and muck about with styling of the paragraphs, Gutenberg’s parser typically fails to understand this HTML CSS addition and forces conversion of the entire block into HTML with no more instant preview available. Now you’re stuck viewing this individual block as ugly HTML forever. If you want to see what it will look like in the actual article, you must click ‘Preview’. Calypso happily and fully rendered in-line CSS and still allowed a preview. It never once balked at adding in-line CSS, though it might strip it out if it didn’t like what you did. This is one of Gutenberg’s biggest failures. Blogging is driven by HTML. Styling HTML with CSS is probably one of the simplest things you can do… yet Gutenberg can’t even understand simple CSS styling? Yeah, that’s a #fail.

For styling images and placing them in very specific locations within Gutenberg block articles, here’s where Gutenberg again fails. While you can create an image block and it auto-wraps text, there is no exact placement or altering margins of white space around the image block within Gutenberg. If you want exact placement or specific spacing for the text wrapping around your image, you must again revert to using the Classic Block. Again, another of Gutenberg’s failures.

If you’re going to spend time creating a complex block editing system, you’d think that exact placement of blocks in space within the document (i.e., drag and drop) would have been part of the design. Unfortunately, you’d have thought wrong because this aspect of Gutenberg simply doesn’t exist. There is no drag and drop or exact placement here.

What exactly is Gutenberg then?

That’s what I keep asking myself. Reinventing the wheel without actually offering us something new, improved and innovative is a questionable design choice. In fact, because of the overreaching complexity introduced by Gutenberg into a platform that should be all about simplicity is, again, questionable. WordPress has always been about making it easy and simple to blog. This convoluted, complex and difficult to manage editor only serves to make the blogging experience more difficult, not easier.

I’m not saying Calypso is a perfect editor by any stretch. Hardly. Calypso has a fair number of problems that also need to be addressed. Unfortunately, that editor’s updates had been abandoned about to the time the Gutenberg team started up. This left Calypso mostly unfinished, yet still reasonably simple to use and definitely easier to manage an article’s overall content.


I keep talking about unnecessary complexity. Let me expound on that. Part of the complexity of Gutenberg stems from the block system itself. The fact that we now have to select a specific block type, not really knowing what each do in advance, means we now have to understand the block’s features and their usefulness. That means trial and error. That means a learning curve. That also means needing to understand the limitations of this new unfriendlier editing system.

Yes, it goes deeper than this. The blocks themselves, as I said, are discrete separate entities. You can’t embed one block within another. For example, you can’t make a block quote show up word wrapped next to basic text within your article. An example of a block quote block type is immediately below:

This is a block quote

forces a citation

Unfortunately, a block quote must sit in that position where it is. It can’t be moved into a wrapped position within another block (like an image). You’d think that this kind of innovation would be possible in a new editor. Unfortunately, no. Worse, as you’ll notice, this paragraph is too closely abutted next to the block quote. With Gutenberg, you can’t fix this horrible spacing issue. There’s no way without using inline CSS styling. If you attempt to use inline CSS styling, the entire block may be forced into HTML mode leaving no way to preview the block in the editor.

Now begins a Classic Block.

This is a block quote

The block quote in the classic block doesn’t force a citation footer, leaving much more white space without leaving this paragraph feeling so cramped. Remember, white space is your friend.

Let’s talk about images and placement

To place an image using Gutenberg, this is what you get. You can align left, center or right.

Here is a paragraph next to an image using blocks. You can word wrap next to an image, but you can’t change the spacing of the text around the image.

In a Classic Block, I can style the image to add margin-left and margin-right to change the spacing next to the words. I can’t do this in Gutenberg’s blocks.

Unfortunately, using Gutenberg to perform image wrapping has some unnecessary complexities. There’s no way to ensure that the block just below it is separate. Instead, it wants to pull up and wrap that block too. There’s no way to make sure that the block just below the image doesn’t wrap. Gutenberg attempts to wrap everything. With Calypso, this editor has more fine grained control over this problem because you can add HTML pieces that enforce this.

mask-businessHere begins a Classic Block with some text and an image. I’m writing just enough text here so that I can insert an image and do word wrapping around the image. Keep in mind that a classic block is basically Calypso in a block.

As you can see, this image has more space to the right of it. I styled this image with a margin-right CSS tag which is impossible to achieve using a Gutenberg image block.

Importing Older Articles

If you’ve used Calypso to write articles in the past in WordPress, you may find that Gutenberg’s importing system to be questionable, if not downright problematic. If you attempt to convert a Calypso written article into Gutenberg blocks, expect failure and LOTS of re-editing. Yeah, it can be that bad. Though, it can import without problems too. It all depends on the article’s content. Importing a Calypso document into a Classic Block has much more likelihood of succeeding… after all, the Classic Block is pretty much compatible to Calypso.

There may be instances where importing an older article may not work in either the Classic Block or as Gutenberg blocks. Basically, you take your chances when attempting to edit older articles within Gutenberg. Most times it works, but it may mangle portions of your article’s spacing and other attributes that may see you spending time re-editing. You’ll want to be sure to scrub your article from top to bottom if you attempt to import an older article into Gutenberg. You may find your formatting has been stripped or other features become unavailable.

Gutenberg not Prime Time Ready

The problem with Gutenberg is that there are so many small nuances that are ergonomically incorrect, flat out wrong or of bad design that using it to blog can easily turn into a lengthy chore. While I did use Gutenberg to craft this article, it wasn’t by any means easy to achieve. I did run into quite a number of problems. For example, there’s a Gutenberg open bug report that prevents editing any block’s HTML without crashing the editor entirely. This means that once you edit HTML, the menu that allows you to convert back to visual editing disappears entirely.

You are then forced to quit entirely out of the editor back to the WordPress posts area, then re-edit the article again by relaunching the editor. The Gutenberg team is aware, but it is as yet unfixed.

The small floating menu that appears above the block when selected is problematic. Not only is it the same color as the editor itself (white) the imagery used on the icons is questionable, with none of the images looking professionally designed. In fact, it looks like someone hired their teen art student kid to design the images. They’re not only too simplistic and basic, many don’t read as to the function they perform. This whole area needs an overhaul… from the questionable floating menu to the coloring to the icon imagery. It’s awful and amateur.

If you blog with WordPress, please let me know your thoughts on this new Gutenberg editor. Yes, it does work to a degree, but that all ends fairly quickly if you decide you want to go deeper into the HTML to style things.

Otherwise, too many times you get the below (note, Classic Block used for the below image as the spacing needed to be styled):

Screen Shot 2020-06-11 at 10.04.18 AM

Out of 5 stars, I give Gutenberg a solid 2.2 star rating. I give Calypso a 3.8 star rating. Calypso is simpler, easier to use and overall gets the job done faster. The lower rating for Gutenberg isn’t necessarily because of its failures, but mostly because its design goals didn’t seek to improve the overall WordPress blogging experience or help us making blogging faster. Complexity is a double edged sword and doesn’t always make things “better”. If anything, that’s the primary takeaway from this updated editor’s design.

There are even more usability and ergonomic problems that I simply can’t get into here. You’ll simply have to try it and compare. Though, I’m never a fan of designers who feel the need to place stuff behind increasing layers of menus. If it’s a function that can be front and center, it should be front and center. Placing that thing behind layers and more layers of menus only serves to waste my time.

Launch Speed Benchmarking

Here’s where Gutenberg fails again. The amount of time it takes to launch Gutenberg is excessive. Calypso takes slightly under 2 seconds to completely launch and be ready to edit your article. Unfortunately, it takes almost 10 seconds for Gutenberg to launch before you’re ready to edit. Yeah, that’s a big step backwards in performance. Time is important. Waiting almost 10 seconds for an editor to launch just to make a simple change is a severe waste of time. If you have to do this multiple times in a day, that wasted time adds up.

Gutenberg needs a MAJOR overhaul in the launch performance area.


Star Trek Voyager: Inconsistencies Abound

Posted in entertainment, writing by commorancy on April 2, 2015

I’ve recently decided to rewatch all of the seasons of Star Trek Voyager again. I missed many of the later episodes and decided now is the time to watch them. One thing I have noticed is that time has not been kind to this series, neither have the writers. Let’s explore.

Seasons 1, 2 and 3

The first thing you’ll notice about season one is the dire predicament in which Voyager is placed. After attempting rescue of a Maquis ship, the Voyager gets pulled into an unknown anomaly and is sent hurtling into the delta quadrant. After the two ship crews merge, because they need the Maquis ship as an explosive, they ‘assimilate’ both crews onto the Voyager. This is where the fun begins.

The first season sees a lot of resistance and animosity from the Maquis crew towards Star Fleet. Captain Janeway makes some questionable decisions, like blowing up the caretaker array instead of trying to salvage it, thus stranding everyone in the delta quadrant. From here, we see many a shuttle accident in among holodeck romps. It seems that every time a shuttle tries to land somewhere (for whatever reason), it ends up crashing and Voyager has to come to the rescue. If we’re not seeing rescued downed shuttles, we’re playing with stupid characters on the holodeck or beaming critical staff (sometimes the Captain herself) into inexcusably dangerous situations.

The second and third seasons keep expanding what was started in the first. But, one thing you’ll notice is that while Janeway keeps close tabs on stock depletion in the first season, all that subtext is dropped by the second season. By the third season, it became a monster of the week series where Voyager was ‘reset’ at the beginning of each episode to have a full crew, full armament of torpedoes and a full complement of shuttle craft. Additionally, any damage sustained in a previous episode was non-existent in the next episode. The only continuity that was pulled forward was the replicator rations. And, that plot device was only pulled forward to give the Neelix character some work to do as a makeshift chef in the Captain’s private dining room.

Unfortunately, dropping the limited stock, rations, crew complement and limited shuttle craft supply was a singly bad move for the writers and this series. Seeing Voyager become increasingly more and more damaged throughout the series would have added to the realism and cemented the dire predicament in which this ship was placed. In fact, in the episode Equinox (straddling seasons 5 and 6), the Equinox ship is likely similar to how Voyager’s ship and crew should have looked by that point in their journey. Also, at some point in the journey through the delta quadrant, Janeway would have had to drop the entire Star Fleet pretext to survive. If, like the Equinox, half of the crew had been killed in a battle, Janeway would have been forced to reconsider the Prime Directive and Star Fleet protocol. In fact, this entire story premise could have started a much more compelling story arc at a time when Voyager’s relevance as a series was seriously waning and viewership dropping. Taking Voyager out of its sterile happy-go-lucky situation and placing it into more dire realistic circumstance could have led to an entirely new viewership audience. Situations not unlike this would ultimately be played out in later series like BSG where this type of realism would become the norm and a breath of fresh air in the previously tired formulaic series.

Star Trek, up to Voyager, had always been a sterile yet friendly series where each episode arc always closed with a happy-ending. Each episode was always tied up far too neatly in a pretty little bow, possibly also wrapped in a morality play. While that worked in the 60s and seemed to work in the 80s for TNG, during the 90s that premise wore extremely thin. By the 2000s, gritty realism was the way of series like Stargate, 24, Lost, BSG and Game of Thrones. Unfortunately, by comparison, the new influx of gritty realism in other series made Voyager, DS9 and TNG seem quaint and naïve by comparison. Instead of perfectly coiffed hair and immaculately cleaned and pressed uniforms, we would now see dirty costumes, hair that is unmanaged, very little makeup and character scenarios where everything doesn’t work out perfectly at the end.

While Brannon Braga, Rick Berman, Michael Piller and Jeri Taylor should get a few kudos for attempting to keep Star Trek alive, they did so at the cost of not keeping up with the times and sacrificing the franchise entirely as a result. Even when Voyager was introduced, the episodic formula that Voyager provided was already wearing thin. Even during its initial run, it was somewhat quaint and naïve already. Like attempting to recreate the Brady Bunch series exactly as it was in the 70s in the 2000s, Voyager was a throwback to the past. All of this is mostly the reason I stopped watching it during its original airing. Like an old comfort toy from childhood, eventually you have to leave it behind and grow more mature. Star Trek Voyager just didn’t grow up and mature with the prevailing winds of change, its audience age demographic and the prevailing TV series landscape. It’s ironic, Star Trek is about growth, maturity and learning, yet while the producers and writers were churning out weekly stories about these very topics, they couldn’t manage to keep up with the growth trends in their own industry. In short, Voyager needed a drastic mid-series makeover (after season 3) to keep up with the changing times.


In the first season specifically, Janeway institutes replicator rations, power saving measures, yet fully allows the crew to use the holodeck at will. Seriously, the holodeck is probably one of the top energy drains on that ship, and you’re going to let the crew use this power hungry thing willy-nilly? Yet, you force the crew to limited replicator rations? Why not disable the holodeck except for emergency use and let the crew have all the replicator rations they want? It’s seems fair to me.

Again, in the first season, Janeway identifies that the ship has limited shuttle and torpedo complements. Yet, in 3rd and later seasons, Voyager is popping off photon torpedos like candy. I also have no idea just how many shuttles have been destroyed, disabled or otherwise left as junk on planets. Yet, Voyager seems to have an infinite supply of them. It also seems that Voyager has an infinite supply of crew and torpedoes. I believe it was counted that Voyager shot off somewhere close to 98 torpedoes the entire 7 season run. And, considering that 7 seasons was actually only 7 of Voyager’s 23 years in the delta quadrant, extrapolating that out means Voyager would have shot over 320 torpedoes in the 23 years they were in the delta quadrant when they only had 38 on board.

On top of all of this, Janeway is a completely reckless captain. She continually puts her crew in harm’s way intentionally looking for resources, scouring through junk, investigating, exploring, trying to salvage Borg cubes. You name it, Janeway has had her crew recklessly do it, instead of the obvious… trying to find a way home. How that crew managed not to actually mutiny and kick her butt out of the captain’s chair is beyond me. Janeway is seriously the most reckless captain in Star Fleet. Far and above Kirk in recklessness.

Episode Writing Continuity Carelessness

In Season 4 Episode 23 entitled Living Witness, the Doctor is reactivated 700 years in the future on the Kyrian home planet in the Delta quadrant. There was never any discussion that this episode was built from any kind of temporal anomaly. The Doctor finds he is part of a museum exhibit and is called upon to clear Voyager’s name for being part of the ship that started their war. Ignoring the stupid war premise which really makes no difference one way or another, what this episode states is that the Doctor’s holo matrix is downloaded during an attack on Voyager and left on the planet for 700 years.

Let me pause here for a moment to catch everyone up since there have been some questions about this specific episode’s setup (which was, by the way, also inconsistent). Pretty much the entire series before and after the Living Witness episode drilled the point home time and time again that due to the doctor’s expanded holomatrix, ‘he’ was ‘unique’ and ‘uncopyable’. Because this point was driven home time and time again and because it was used as a plot device to ensure both the audience and the Voyager crew understood just how much the doctor was like a human, we are told the doctor is unique, individual, indispensable, irreplaceable and can die. There was even a Kes episode about this whole idea, but not the only one. When the rest of the crew was ready to reboot the doctor because his holomatrix had been degraded so badly, Kes stood by the doctor and vouched for his uniqueness, individuality and stood up for the doctor (when he couldn’t) to continue trying to keep him intact. If it had been as easy as making a backup copy and restoring a doctor copy, the ship could have used a backup doctor several times when the ‘real’ doctor goes on away missions, instead of leaving Kes and Paris to run Sickbay. They could have even used a backup copy to overlay his later degraded version on top and clean his matrix up. Yet, this never manifests not once in any episode. In fact, as I said, the writers did everything they could to ensure we understood that he was uncopyable, not even with the mobile emitter. So, what does this all mean? It means that the mobile emitter that was found contained the actual doctor, not a copy as was theorized.

What this story flaw also says is that there should no longer be an EMH on Voyager after the doctor has been left on this planet for over 700 years. It also means that no other episodes after this event should ever see this EMH program again. In another episode, Harry Kim tries to recreate the EMH after the doctor was thought to be lost during that episode, but after Kim fails, he leaves Paris to fend for himself in Sickbay. This means that there is exactly one doctor and he was left on Kyrian planet. The Doctor serves the Kyrians for a period of time, but eventually finds his way home to Earth 700-800 years after Voyager. Yet, in episodes after Living Witness, the Doctor is happily helping folks in Sickbay once again, including appearing in the final episode entitled Endgame.

Now, one could argue that Living Witness happened sometime later at the end of Voyager’s run, but then why is it in season 4? It also means that for at least some duration of Voyager’s trip, the Doctor EMH program was not available. Though, B’lana might have created a new rudimentary EMH, we never saw it. Yet, in Season 7, Episode 23 — Endgame, we see the Doctor come strolling through the Voyager party 23 years later. Assuming the episode Living Witness to be true, then this is a major continuity error. The doctor should not be in Endgame at all. He should still be deactivated on the Kyrian homeworld.

Let’s consider how it’s even possible that the mobile emitter was left (or was stolen) in Living Witness. Since there was only and ever one mobile emitter, that logically means the doctor should not have had the mobile emitter for any episode after that Living Witness (assuming we accept the ‘backup’ idea, which I don’t). Yet, we continue to see the mobile emitter used on episodes all the way to the very end when Voyager returns. This episode contains far too many consistency problems and should not have aired.

Lack of Season-wide Story Arc

Star Trek The Next Generation attempted to create a few longer story arcs. But, the writers never really embraced such arcs beyond the borders of an episode (or multi-part episodes). Though, some character relationship arcs did reach beyond the borders (i.e., love relationships, children, cultural rituals, marriages, etc), arcs related to alien races, ship resources, ship damage or astral phenomena (with the exception of the Q) were almost never carried forward. So, for example, in TNG, during season 7, the Force of Nature episode forced Star Fleet to institute a warp speed limited due to warp drive destruction of subspace. That speed limit arc carried through a few episodes, but was ultimately dropped and ignored during Voyager. It was dropped primarily because it didn’t help the writers produce better episodes. By forcing starships to travel at slower warp speed, nothing good came from this plot device. In fact, this speed limit would have only served to hinder Voyager in getting home. Clearly, the writers had not yet conceived of Voyager when TNG’s Force of Nature aired. Otherwise, the producers might have reconsidered airing this episode.

Also, because warp speed is a fairly hard to imagine concept in general, artificially limiting speeds in a series where fantasy and space travel is the end goal actually served to undermine the series. There were many ideas that could have created larger more compelling story arcs besides setting an unnecessary speed limit. The sole purpose for the speed limit, I might also add, was only to make Star Trek appear eco-friendly towards the inhabitants of the Milky Way… as if it even needed that moniker. I digress.

Even at the time when TNG was ending, other non-Trek series were beginning to use very large and complex story arcs. Yet, Star Trek TNG, DS9 and Voyager clung tightly to story arcs that fit neatly within a 42 minute episode border. This 42 minute closed border ultimately limited what appeared in subsequent episodes. Very rarely did something from a previous episode appear in a later episode unless it was relationship driven or the writers were hard-up for stories and wanted to revisit a specific plot element from a previous episode. In general, that was rare. In Voyager, it happens in the season 5 episode Course: Oblivion (which this entire episode was not even about Voyager’s crew) and which is a sequel to the season 4 episode Demon (where the crew lands on a Class Y planet and is cloned by a bio-mimetic gel). These types of story sequels are rare in the Star Trek universe, especially across season boundaries, but they did occasionally happen. Even though such stories might appear occasionally, Star Trek stayed away from season-wide or multi-season wide story arcs, with the exception of character relationship arcs.

Janeway’s Inconsistencies

The writers were not kind to the Janeway character. One minute she’s spouting the prime directive and the next she’s violating it. There is no consistency at all here. Whatever the story requires forces Janeway’s ethics out the airlock. The writers take no care to keep her character consistent, forthright, honest and fair. No, she will do whatever it takes to make the story end up the way the writers want. It’s too bad too because in the beginning, the Janeway character started out quite forthright. By the time Seska leaves the ship, I’m almost rooting for a mutiny to get Janeway out of the way. In fact, I actually agreed with Seska to a certain extent. Janeway’s number one priority was to protect the crew and make it safely back to the Alpha quadrant as timely as possible. Instead, Janeway feels needlessly compelled to galavant for 23 years all over the Delta quadrant making more enemies than friends, killing her crew one-by-one, destroying shuttles, using up torpedos, using up ship resources and generally being a nuisance.

Worse, Janeway’s diplomatic skills with alien races is about as graceful as a hammer hitting your thumb. She just didn’t get it. The Sisko character in DS9 got it. The Seska character got it. Janeway, definitely not. While she may have been trained to Captain the tiny Voyager ship, she had absolutely zero diplomatic skills. I’m guessing that’s why Star Fleet never tapped her to helm a Galaxy class ship and, instead, forced her into the tiny Intrepid class for scientific exploration.

I’m not even sure why Star Fleet tapped Voyager to go find the Maquis ship. While Voyager may be somewhat more maneuverable than a Galaxy class ship, a Galaxy class ship would have been better suited to find and bring back the Maquis ship in the first episode, not Voyager. So, even the series started out wrong.


Time has also not been kind to the Voyager episodes themselves. Both the Next Generation and Voyager relied on the weekly episodic nature of the series. The 7 day span between airing of episodes gave viewers time to forget all about the last episode before the next one aired. This time gap helped the series.. a lot! But, in the age of DVD sets and Netflix where commercials are devoid and there’s no need to wait any length of time to watch the next episode, watching Voyager in rapid succession shows just how glaring the continuity flaws are. No, this format is definitely not kind to Voyager. It’s not even just the continuity errors. It’s stupid decisions. Like arbitrarily deciding that it’s perfectly okay to leave Holodeck simulations running even when the ship is running out of power with no way to replenish. Like firing yet another large volley of photon torpedoes at a Borg ship when you only have 38 on board. Like continually and intentionally sending shuttle crafts into known atmospheric disturbances only for them to be disabled and downed. Janeway is the very definition of reckless with her ship, with her command, with her crew and with their lives. Yet, no one on board saw it, commented or mentioned this. Seska came close, but she left the ship before she got that far with Janeway.

Overall, when it was originally on, it was more enjoyable. Today it’s a quaint series with many glaring flaws, no overall story progression and a silly ending. Frankly, I’m surprised this series actually ran for 7 years. It should have ended at about the fifth season. Basically, after Kes (Jennifer Lien) left and the series picked up Seven of Nine (Jeri Ryan), it all went downhill.

If anything is responsible for killing off the Star Trek franchise, it’s Voyager. Yes, Enterprise came after, but Enterprise was just too foreign to really make it as a full fledged Star Trek. It was really a casualty of Voyager instead of being to blame for the demise of Star Trek.

%d bloggers like this: