Yeah the Klingons changed over time, but once you they have a Klingon in the regular cast it’s kinda set at that point.

Worf is THE Klingon now. All other Klingons will be compared to Worf from here on out. Sure there can still be some variance, but if they stray too far off from Worf, they’re asking people to choose which is the real Klingon: Worf or whatever they’re putting up on the screen now. The answer will always be Worf is the real Klingon, and the new version is not a real Klingon.

It’s just how it is, and it’s really insane they tried to stray from Worf too much under the excuse that Klingons were changed previously. Yeah they were changed previous to a Klingon being a regular cast member on two popular Trek series.

Yeah Into Darkness was just a bad concept all around. Just a bad idea to remake a good movie in general. And then Star Trek II revolved around a villain from Kirk’s past coming back for revenge. Kirk and Khan never met before in the Kelvin timeline, so there really isn’t anything there. It was destined to be a a half-assed remake at the concept stage, and they should’ve scrapped it and done pretty much anything else as soon as someone suggested bringing back Khan.

Still it’s not the worst Trek movie.

Android slaves in Picard conflicts with TNG canon.

Yeah I hear ya on that. When you think about it, Picard S1 is the exact opposite of Measure of a Man. In Measure of a Man they start by thinking it’s ok to disassemble Data against his will because he’s a machine. But then there’s a debate about whether he’s sentient. It ends with Picard saying that since debatable that he’s sentient there is no debate about whether or not to disassemble data because if they do that if there’s even a possibility Data is sentient, they risk being horrible racist monsters and eventually creating a slave race.

Picard S1 starts with the Federation already creating a slave race AND disassembling the androids. And it’s not that they’re assuming they’re just machines, they are overtly racist against the androids. So much so when the androids malfunction they don’t even consider the possibility that it’s a malfunction (run a level 5 diagnostic or whatever), they go straight to hating androids.

I get they were trying to do an anti-racist message (which it’s Star Trek, that’s what they should do) but by doing Measure of a Man backwards they didn’t accomplish anything. Because it’s later revealed the androids were indeed just malfunctioning machines. So the Federation was being racist against malfunctioning machines? What is anyone supposed to learn from this message? If your computer doesn’t work right, don’t be racist against computers… run a virus scan instead.

TNG: Android is a machine -> maybe he’s sentient? -> disassembly might be racist? -> disassembly: NOPE!

Picard S1: Android are people -> people that the Federation is racist against -> no wait, they’re actually malfunctioning machines -> ???

By doing it backwards they watered down the anti-racist message so much it’s non-existent.

I: Am just not interested in

Star Trek:

• Discovery
• SNW

Unspecified (specify): They’re prequels.

I already imagined the backstories for the shows I’ve seen… are you not supposed to? A prequel isn’t going to ever line up to how I imagined the backstory (how could it, everyone has a different imagination) so there’s always going to be dissonance with a prequel. Not that I hate these shows, just not interested in them.

Make Star Trek Legacy and move the story forward pls, thx.

Judging from how much steel they’d have around at a single warehouse near to where I used to live, I’d hazard to guess that it would take much less time than a couple of months to get the steel.

But yeah, it’s a moot point, because like you say it’s going take far more time to design a new bridge and get together the crews to build it. We don’t have some idle SCVs around just waiting to start building as soon as you click on the the location.

And I’m no engineer, but I’m guessing the steel from a bridge that collapsed would be too warped to be useful and the pieces that looked ok would have to undergo testing to make sure the stress they went under didn’t compromise the material in some way. I’d guess it would be more expensive to use that steel than to just use new steel.

Yeah kinda. In politics there’s going to be scenarios someone has to choose between doing the right thing or doing what’s best for their career. And yeah, militaries have politics at the top, just not the left-right politics that’s common in a democracy. These political scenarios filter out the “do the right thing” people and prevent them from advancing to the top. Not all of the time, but often enough that there’s a higher percentage of shitty people in leadership positions then you’ll find in the general population.

The United Federation of Planets was just made up to cover up the fact the Galaxy is actually disc shaped!

Just look at the Federation flag!

The galaxy isn’t round, sheeple!

By my logic the Jedi wouldn’t be able to sense that Palpatine was a Sith even while sitting in a room with him where there was no dangers or distractions. I’m no prequel fan, but I recall that it’s mentioned the Jedi’s ability with the force was being weakened.

And it wouldn’t affect the ability to swing a lightsaber around. Though it would affect the ability to use precognition to predict where the opponent was going to swing their lightsaber. I mean they can deflect blaster shots all day but can’t deflect a lightsaber that’s moving much slower? Why is this? Makes sense if you consider the guys shooting the blasters don’t have much force abilities so they can use the force to predict where the shot will be and deflect it. But another force user’s actions can’t as easily be predicted so it comes down to good old fashioned martial arts abilities.

Leia also has powers with the Force.

Star Wars is basically a more accessible version of Dune. In Dune people had precognitive abilities that would allow them to predict the future. Problem is if someone else can foresee the future one person is reacting to what they predict the other will do, but then the other changes what they’ll do based on what they predict the first person would do. So it results in kind of a stalemate. Two people with precognitive abilities can’t predict each other’s actions. Or the actions of those under the other’s influence.

So the Sith’s abilities are weakened by the presence of a Jedi and vice-versa. Leia’s ability with the force (whether she knew she had them or not) prevents Darth Vader from sensing much about her other. Also the Sith’s abilities wouldn’t be effective in predicting the actions of any rebel following Leia’s leadership.

Yeah but why am I watching one woman in a catsuit with the occasional gratuitous decontamination scene when there was Baywatch on another channel?

They put themselves in a market they couldn’t hope to compete in.

It kinda killed Enterprise for me. The catsuit and the gratuitous “decontamination” scenes. It felt really off.

It’s not like I’m prudish or anything, I like that kind of thing in certain contexts. But it’s Star Trek, I’m watching this thing to get my nerd on. Trying to sex it up just made it weird.

Yeah that was my point. Agile with shitty managers sucks. But any way of doing things with shitty managers sucks.

A binary might still require a specific shared lib version, specific architecture,

Yeah but those issues are dealt with at compile time by a developer. The problems don’t manifest themselves at runtime as they do with an interpreted language.

Doesn’t always work when working with legacy unupdated dependencies.

Also compile time, not runtime.

With JS you can at least see the source that’s being run,

You could disassemble compiled code and read the assembly code. Yeah that’s difficult, but about the same difficulty as reading JS that’s been run through an optimizer. Nobody has time for that, and users certainly don’t have the skill to do that, so the the organizations that make the browsers are ultimately responsible for making sure any new addition to JS isn’t going to cause the security problem.

Wouldn’t having compiled code running in the browser (via webassembly) be actually worse for security?

About the same for security. I don’t know much about web assembly but it has similar problems. I mean the reason I don’t know much about it is because it’s too new, can’t count on it being widely supported, etc. Similar problems as JS. But being compiled to a common language might shift the pain of dealing with a lot of problems with language changes to the people who write the compilers for it. Time will tell.

But the thing is, most languages aren’t designed to be primarily interpreted by a browser. Nobody is going to say “Hmmm we better think about how this will affect web browser security if we add to the language.” Because use by browsers as a web assembly isn’t the primary use case. If a language change negatively affects a browser, that’s their problem to sort out.

But with JS it is primarily being used as an interpreted language implemented by browser makers. Which means the browser makers have a huge amount of influence over the decision making process. If google says “we have concerns over security with this feature so we aren’t using it in chrome” then well it’s not a feature that developers can use because it’s not going to work for most users.

I think you’re trying to make this a fair comparison, but my point is that it is not a fair comparison. What the languages are used for and how they’re deployed impacts process for improving them. The requirements for JS in terms of what it’s primarily used for and how it gets deployed makes it difficult to change, which is why it is as messy as it is. Takes a lot longer to get changes accepted by all the parties that need to accept them.

Yeah but with JS, you have to consider the browsers that are out there already. I think this is getting better now that IE is killed off, but there’s still a consideration about whether to use a new feature that doesn’t work on older browsers.

With C, it’s compiled so if you’re distributing the binary, you’re done. And if you’re sharing the source to another developer, that dev will be likely to be technically proficient enough to update gcc and any needed libraries to the right version to get it to compile.

When it’s an interpreted language that is interpreted by browsers made by different companies and organizations (so they have to agree on changes), with users not being reliable of keeping their browsers up to date, it’s going to be messy. Also there’s security concerns, you need to make sure when implementing the extension it won’t allow bad actors to make scripts to take over the users computer.

It’s not anyone’s fault, it’s just a significantly more difficult problem to extend a language that is going to be sent to user’s computer on the fly from arbitrary websites and have those extensions be reliable, secure, and consistent across the various companies implementing it.

The biggest problem with Agile is bad managers fucking it up. But bad managers will fuck things up no matter which way you do things.

But they’re going to want to somehow see progress, and they’ll leave you alone if they see some cards moving on a board. Even if they have no idea what the cards mean.

Whatever, it’s better than having to do status update meetings.

Yeah that’s trending towards the grey goo scenario, isn’t it?

But it’s also similar to how the Borg operate too. Also I think the OST had the Doomsday Machine episode that had something about a weapon killing the civilization that made it. I think there was a TNG episode like that too.

So it’s kinda covered, just not exactly the replicator scenario. But that’s fine, it’s better to have characters as a threat rather than machines. Controversial opinion, but I even found the Borg to be boring after Best of Both Worlds.

Yeah they never really use transporters and replicators to their fullest capabilities. Knock out their shields, beam the enemy crew to the brig (if you’re good) or into space (if you’re not so good).

Why bother with torpedoes? Just teleport bombs right on the enemy target.

They had self-replicating mines on DS9, why not self-replicating computer controlled starships? Send infinite waves of automated starships at the enemy?

Have your most elite Jem Hadar squad stand on the transporter pad and beam down infinite copies of them down to the planet. They’re cloning them anyway, doesn’t seem like the Dominion would have moral qualms about this.

I think it suffers from the same problem as SQL. A bunch organizations and companies would need to agree to make improvements, you don’t want to break compatibility, so nothing really improves. You just get some extensions to it here and there which just makes it messier.

Yeah creating tests for every single method is insane. If a feature changes it’s more difficult you either have to figure out how to implement the change without changing the method, or you change the method and have update the unit test. But if you’re constantly updating the unit tests, how do you know if you might’ve broken something else that the test was intended for.

It’s way better just to do integration tests that match the feature request. That way the feature that someone asked for will continue to work even if you decide to refactor the code.

Yeah the error list is my friend. Typos, assigning something to the wrong thing or whatever is fixed without having to run the code to test it. Just check the error list and fix any dumb mistakes I made before even running the thing. And I can be confident in re-factoring, because renaming something is either going to work or give a compiler error, not some run-time error which might happen in production weeks later.