Message from @Grenade123

Discord ID: 494362509638107147


2018-09-26 04:13:56 UTC  

because it was largely concerned with addressing aircraft which were similar to it

2018-09-26 04:14:34 UTC  

we currently have aircraft which are substantially similar in capability to the competing ones, if slightly inferior in some subset of characteristics

2018-09-26 04:14:57 UTC  

do we? what do we have to fight the new russian jets toe to toe?

2018-09-26 04:15:15 UTC  

22 can't hold its own in a straight up fight

2018-09-26 04:15:26 UTC  

its not designed to either

2018-09-26 04:15:39 UTC  

ask yourself why the Su-34 and Su-35S look so similar

2018-09-26 04:15:50 UTC  

and look substantially similar to the Su-30

2018-09-26 04:16:02 UTC  

and the Su-27

2018-09-26 04:16:17 UTC  

they are all very similar aircraft, in the broad sense

2018-09-26 04:16:17 UTC  

they really don't

2018-09-26 04:16:31 UTC  

or more accurately, they look similar to an f-18

2018-09-26 04:16:42 UTC  

sure, you could say so

2018-09-26 04:17:16 UTC  

Now why is it that we pretend that we're going back to the drawing board on EVERYTHING

2018-09-26 04:17:27 UTC  

when ultimately we are going to produce something substantially similar to its predecessor?

2018-09-26 04:18:14 UTC  

just because it looks the same on the outside, doesn't mean it is the same on the inside.

2018-09-26 04:18:18 UTC  

The Russians know the answer to this question

2018-09-26 04:18:35 UTC  

Have you done design work?

2018-09-26 04:18:39 UTC  

the Su-35, Su-35S and Su-27m are decades apart

2018-09-26 04:19:05 UTC  

the Su-35 is more or less a new Su-27M

2018-09-26 04:19:55 UTC  

30 years later, they are still related enough that they have the same info bar on Wikipedia

2018-09-26 04:20:07 UTC  

you sure that is why?

2018-09-26 04:20:18 UTC  

same-but-different is the approach

2018-09-26 04:20:24 UTC  

it is different in the ways they cared about

2018-09-26 04:20:53 UTC  

i will re-ask my question, you ever done design work? of the engineering or technical kind?

2018-09-26 04:21:06 UTC  

What would qualify as a yes in that case?

2018-09-26 04:21:14 UTC  

I'm a software developer by trade

2018-09-26 04:21:21 UTC  

so no

2018-09-26 04:21:36 UTC  

I've not designed a production military aircraft

2018-09-26 04:23:17 UTC  

they you should know sometimes legacy code gets to a point where it needs to be re-done from the ground up from time to time. The more future proofed the original code the easier it is, but you can only do so much to plan for changes 30 years out.

2018-09-26 04:23:28 UTC  

No, I don't really agree with that statement.

2018-09-26 04:23:48 UTC  

Generally speaking, in systems of a certain size, it is rarely necessary to toss and replace everything.

2018-09-26 04:24:11 UTC  

Even if making a major change, like completely switching programming language or environment.

2018-09-26 04:24:34 UTC  

or most important purpose

2018-09-26 04:24:47 UTC  

making the next iteration as similar as possible to the previous generates a considerable amount of value in itself, if you are willing to do the grunt work.

2018-09-26 04:25:27 UTC  

yes u can make things more efficient

2018-09-26 04:25:30 UTC  

my point here is that the external aerodynamic properties of certain types of desirable military aircraft have not changed, per type, substantially since the '80s

2018-09-26 04:25:52 UTC  

You might get better engines, find out that thrust vectoring affects the desired wing structure

2018-09-26 04:26:12 UTC  

maybe two subassemblies are merged for better rigidity or serviceability

2018-09-26 04:26:22 UTC  

but that's not the same as "starting from the ground up"

2018-09-26 04:26:42 UTC  

which, in my view, is rarely your best option, if the system you want is substantially similar to the one you have.

2018-09-26 04:27:52 UTC  

they key phrase being "if the system you want is substantially similar to the one you have"