I think, again, that's where I am completely different. If a show doesn't stick the landing then I just avoid the landing. I'll go back to what I like and continue forward with the things I like. Though, I am obviously OK with Season 3 since the ending works just fine for me, and like the cause of the Burn. So, if a show is leaving a bad taste in my mouth I go find a part that doesn't. ETA: Best example is "These are the Voyages." Ignored, while Demons and Terra Prime works quite well.
Yeah, I think that starts to happen over time (I've basically blocked These are the Voyages from my memory). Still too soon for me for this season though.
Fair enough. I tend to be more proactive when it comes to viewing. Usually because I'm already rewatching things once I finish. I don't tend to move on from shows quickly once they are done so it is easy to do. Mileage will vary.
I’m not a fan of their take on the 32nd century. It just doesn’t feel that more advanced than Discovery’s era. Plus I don’t buy they would be still using warp and Dilithium as their main way of travel. I think this whole warp/burn story would have worked better in the mid 25th century. That way it would have been more believable that they would be still using warp and Dilithium. That way they could explain why the shortage lead to new forms of travel being developed, which leads to things like the proposed “trans slipstream” drive the Enterprise J had and the temporal drive the relativity has later on.
1. I don't understand why its such a bad idea? I mean the whole ship can travel through mushrooms instantly, so the fact the nacelles detach is really neither here nor there at this stage for me. 2. It certainly breaks with whatever it is that fans are calling Rodenberry's Utopia, and it jars a bit with everything we have seen so far. I do think everything is being built for our heroes to rebuild the federation, so starting from rock bottom adds to that story....we will see. 3. We are still building walls now - with flaws in them. 4. I think, it was obviously meant to disgust her. Rather than be scientifically accurate. Its a bit like refusing to answer why do chickens cross the road citing that roads are not within a chickens usual habitat. 5. Horrible, completely broke the world building, made it unbelievable, worst scene so far by a looooooong way. And all of that for a really crappy fight scene. Definitely not worth it. 6. I didn't mind it at all. It was personal. Which is very Trek. Challenging the morality of the federation for not prioritising that child, the guilt he feels when he finds out what he caused, etc etc. Aside from the turbo lifts, I don't enjoy the constant shoe-horning of moral wobbling on behalf of Burnham. There is a constant theme of her going off the rails, before riding back to the rescue. This is getting tiresome. They need to find new ways for her character to grow in Season 4. I want to like her, I want her to be my hero and get behind her despite her moral quandries as we do with other Trek characters, I just couldn't so far.
Out of Star Wars? I've watched a lot of SW, especially lately, but i don't recall such things.I see it more in other science fiction art. But, then, I also don't see the issue so maybe I'm just blind. It's more profound than perhaps is given credit for, at least from my point of view. Largely because human society at large doesn't take childhood trauma seriously. The Burn was devastating-yes, and imagine how he felt. Also, a child causing the Burn? Sounds straight out of TOS.
very rarely and usually not something exploitable. But, especially, not bugs that people knew of centuries ago.
Three years ago a person found a bug in Windows 10 that could be traced back to the Windows NT operating system, 44 years old at the time. No, not exploitable but still possible. And I highly doubt that the hologram OS was nothing more than a deliberate test to see what people knew.
I tend to agree that Kovich merely created holos for Georgiou's level of knowledge to see how she would react because he knew how Terrans behave for the most part, and as he said, the only way he would gleam any information from her is to have her do the talking (and study her actions in the process). Also, on the subject of a person finding a bug in W10 that can be traced back 44 years... for Trek, this is a far more technologically advanced combination of societies. AI and adaptive algorithms would have found that problem and eliminated it (if not them, then someone would have found it long before it could be used - aka, long before the late 24th century, nevermind 32nd)... problem is, Trek writers don't seem to know the full extent of Federation technological abilities (or how to combine them), therefore, they use it in an extremely antiquated (primitive) way for the purpose of 'drama'.
The problem came from the original DOS coding that NT, and other Windows OS, were built upon and designed to be compatible with older DOS programs. At least, if I'm understanding the article right. Basically, the base code had not been fully changed even as new things were added.
In any case, definitely not something so easy to exploit, especially by someone that is centuries out of time and so easily
NT’s lineage is from OS2, which itself dates back to late 80s the x86 architecture wasn’t introduced until 1978 As to the original point, I’m happy Kovich owned the place - he wanted an exploit, there was one to have. Happy about isolationist Earth too. the other points (cause of burn mainly) were a let down I agree. As was the lone federation guy at the start of the season. No sense of scale (or lack of) it with the new federation.
The problem came from the code that NT was built upon, thus creating a much older error. My overall point is that holograms could have errors if the original code somehow referenced the wrong thing. It happens with current tech so why is Starfleet tech immune? I don't buy that Starfleet would have perfected all bugs at all times by any century. But, even that point is moot. I think Kovich was just ing with Georgiou. His dismissal shrug was one of the best parts of the season.
Because it *doesn’t* happen with current tech. Even the rare Decade old bug is usually something so arcane that it can’t be exploited easily so casually by the user. case point: the very famous hearthbleed bug in OpenSSL, which was quite widespread for a few years, but you needed to be a true wizard to exploit. or a bug in macOS that I discovered some 15 years ago that is still there and allows you to totally lock the computer...but you need to have administrative privileges to exploit it and if you do you can do much worse anyway.