Spoilers Star Trek: Discovery 2x14 - "Such Sweet Sorrow, Part 2"

[Spot261]

I'm thinking that when the blast door is fully closed it also has some kind of energy field to redirect any explosion away from it.
Anyway, most of the power from the torpedoes detonation was going to be forced back out the opening toward the bow following the path of least resistance.

No, it was transparent neutronium.

They invented it a few centuries early because of some shenanigans involving an existential threat, time travel and life forms which unexpectedly proved to be intelligent.

 

[TrickyDickie]

One of the Klingons was played by Glenn Hetrick, their lead makeup guy who helped make the new Klingons

Great catch!

And very interesting, considering the K'Vort-class ships from "Yesterday's Enterprise".

 

[Kor]

Did anyone else love the preposterously dramatic reveal of Spock's new styling decisions at the end? Many a time have I seen a woman's new haircut treated as a monumental sign of growth, the very culmination of her personal development, but I think this is the first time I've seen a man receive similarly overwrought treatment when changing his hair.

Especially since, this is presumably exactly what he looked like before the whole thing with leaving the Enterprise and being institutionalized.

Kor

 

[Roald]

Which should now have been broken but I am not so sure it is to be honest.

Would Control really be so stupid as to not have a backup put away for safekeeping, or use the time it was on the Discovery to duplicate itself ensuring it makes it to the future.

It’s kinda like First Contact where the Borg begin an INVASION of Federation space with... ONE ship.. Sometimes, things are just there to serve the plot, not necessarily to make a whole lot of sense.

 

[XCV330]

Which should now have been broken but I am not so sure it is to be honest.

Would Control really be so stupid as to not have a backup put away for safekeeping, or use the time it was on the Discovery to duplicate itself ensuring it makes it to the future.

Off topic but David Marusek's novel "Counting Heads" has an interesting side plot of the difficulties law enforcement in the future would have hunting down rogue AI's that refuse to shut themselves down specifically because of the many multiple backup locations they might leave for themselves in case of such a problem, especially if they had a directive that required the stay alive. But if ST never bothers going into what happened to Control's backups, I'm fine with that.

 

[Pauln6]

Especially since, this is presumably exactly what he looked like before the whole thing with leaving the Enterprise and being institutionalized.

Kor

He'd taken indefinite leave . I think it was more an acknowledgement that he was back on duty.

 

[ITDUDE]

9/10. Team Discovery have learned how to craft a satisfying conclusion. Loved every minute of it. Some of it was fanwank (like everyone being sworn to secrecy about Michael Burnham), but here it was done really well.

It's the weirdest thing to callout, but I loved the wormhole jump effect, where everything goes 2D and the perspective shifts. Snazzy way to show extra-dimensional travel.

Looking forward to Discovery: 3207.

Star Trek Discovery of the 32nd century! (She only jumped 930 years, remember so still around 3187-3189. What year does second season take place in anyway? I’m getting couple conflicting data sources.

 

[cooleddie74]

2257.

 

[ITDUDE]

I wonder how L'Rell explained Tyler. I mean she said that he killed him because he was a Federation traitor who also killed her son. She showed the Klingons his detached head! Just two episodes ago in 2x12 she said that if the Klingons would know that Tyler is still alive that the Klingon Empire would be vulnerable to sedition. And now he is standing on the Klingon bridge and no one seems to care? Why is no one trying to kill L'Rell and Tyler for being liars and traitors? They faked Tyler's and their son's death because a lot of Klingons lost their trust in L'Rell because they thought she might be a puppet of the Federation. Why are their no consequences for Tyler appearing alive and L'Rell being happy to work with him again?

Ah it’s a clone. Yeah.. that’s it. No wait, it’s the original Ash Tyler, yeah the one that Voq was modeled after. Yeah that it.

 

[ITDUDE]

"Regular ship shake".

Is that when it does it to a beat?

Kinda curious about that blast door which happily ignored a torpedo detonation only feet away, why can't they build whole ships out of that stuff?

And the glass through which Pike looked at. Transparent aluminum has nothing on that glass.

 

[Rahul]

Holy shit talk about over-correcting your series' premise...

The episode itself? Was fine. I actually really liked it, save the last 5 minutes.

But as someone who just this season actually got into this show - invalidating everything what happened in these two years with a big "it's classified, we don't talk about it anymore" doesn't bode well with me at all.

And I honestly don't get what type of story-possibilites the 33rd century has to offer that the 23rd - outside of Federation space, if the ship actually went exploring - couldn't have offered as well. Except for extreme lore-galores of the future of familiar elements, planets and species. Which the previous two seasons have been. Which have now essentially been completely ereased from lore. Ugh.

 

[Tosk]

And the glass through which Pike looked at. Transparent aluminum has nothing on that glass.

I don't get why they use that tough stuff on the door, but they use an easily broken glass-like substance for the window the turbolift crashed through. If you've got explosion-proof "glass" use it for all the windows, damn it!

 

[fireproof78]

And I honestly don't get what type of story-possibilites the 33rd century has to offer that the 23rd - outside of Federationspace, if the ship actually went exporing - couldn't have offered as well. Except for extreme lore-galores of the future of familiar elements, planets and species. Which the previous two seasons have been. Which have now essentially been completely ereased from lore. Ugh.

I'm torn. On the one hand the 23rd century is what I really enjoy about Star Trek, with Pike, and Kirk and Spock and all them. I certainly do not have much love for the 24th century. So, them leaving is a bit bitter.

On the other hand, I am worn out by the lore and canon debates and would like a fresh start(ish) and some unexplored territory.

Mixed feelings.

 

[ITDUDE]

Holy shit talk about over-correcting your series' premise...

The episode itself? Was fine. I actually really liked it, save the last 5 minutes.

But as someone who just this season actually got into this show - invalidating everything what happened in these two years with a big "it's classified, we don't talk about it anymore" doesn't bode well with me at all.

And I honestly don't get what type of story-possibilites the 33rd century has to offer that the 23rd - outside of Federationspace, if the ship actually went exporing - couldn't have offered as well. Except for extreme lore-galores of the future of familiar elements, planets and species. Which the previous two seasons have been. Which have now essentially been completely ereased from lore. Ugh.

They went out of the way to not reset the timeline. But “shhh.... we don’t talk about Discovery, the Spore drive and Burnham” solution is nowhere near perfect. They over corrected for sure, but outside of time reset, anything else that would have kept Discovery in the lore, and fixed canon is probably beyond producers and writers abilities to fix.

 

[Gonzo]

Well, if she 'moved' the file instead of 'copying' it, what is the result on our computers?

A move is exactly that and if you interrupt that move you can actually lose the file itself or corrupt it as it's not complete at either end.

It may not be recoverable either it depends on the media used, if it's a hard drive with a physical media inside then it may be ok but if it's like an SSD it could be gone for good.

That is why it's always best to copy then paste a file and delete it after confirmation of a successful transfer.

Especially if the file is the only copy or holds valuable information.

 

[ITDUDE]

A move is exactly that and if you interrupt that move you can actually lose the file itself or corrupt it as it's not complete at either end.

That's why it's always best to copy then paste a file and delete it after confirmation of a successful transfer.

Especially if the file is the only copy or holds valuable information.

All my important docs are in the cloud. Even if delete something there is always version history of all changes that I can go back to and revert. Too bad they don’t have anything like that in 23rd century

 

[Kor]

A move is exactly that and if you interrupt that move you can actually lose the file itself or corrupt it as it's not complete at either end.

It may not be recoverable either it depends on the media used, if it's a hard drive with a physical media inside then it may be ok but if it's like an SSD it could be gone for good.

That is why it's always best to copy then paste a file and delete it after confirmation of a successful transfer.

Especially if the file is the only copy or holds valuable information.

See earlier posts about how the data is actually still on the disc.

Kor

 

[DEWLine]

Perhaps in the Federation digital rights management has been adopted to an extreme degree.

That is a disturbing thought, deeply so.

 

[Gonzo]

All my important docs are in the cloud. Even if delete something there is always version history of all changes that I can go back to and revert. Too bad they don’t have anything like that in 23rd century

Essentially they actually keep all the different revisions that you make to it.

It's similar to an incremental backup used in data centers.

 

[Gonzo]

See earlier posts about how the data is actually still on the disc.

Kor

I do IT for a living, it's only still on the drive if it uses physical media and even then it could be corrupted, if it is an SSD or NVMe then it's gone if it's not cached.