3 ms·

None, but this indicates that they're not keeping up with general industry trends, which is nuts.

tclmeelmo 11y ago
The general aerospace defense industry trends don't include C#.
Jtsummers 11y ago
Languages that have no use in my office outside a handful of projects (not intended for end users) include everything that's not: Ada, C, C++, Fortran, Jovial (being replaced), assembler (various forms), Delphi (one project, too costly to rewrite, too lucrative to drop). C#, Java, Python, Ruby, JS, Smalltalk, Rebol, Perl, Bash, C--, Lisp, Forth, Factor, Go, Rust, SML, OCaml, Haskell, Erlang, Racket, Scheme, F#, Visual Basic, BASIC (in other forms), etc. offer no value to the majority of our projects. If they're used, perl and a couple other scripting languages in particular, it's for tools for data analysis (scanning logs, turning hex dumps into useful printouts, etc.). In which case almost any language will suffice. But on our target hardware platforms, and given our target performance constraints, the initial listed languages are pretty much the only options. This is the industry trend.
- tonyarkles 11y ago
  You've done a very good job at illustrating the way I'm interpreting the parent and grandparent comment. Of the list of languages you just wrote out, I've never heard of "C--". I've written code in 22/31 of those languages. Depending on how you want to measure the duration of my career, I've got somewhere between 10 and 20 years of experience. If leaders in an organization haven't at least heard of a language that's in the top 5 of TIOBE (http://www.tiobe.com/tiobe_index http://www.tiobe.com/tiobe_index), I'd have some serious concerns when considering whether or not to work with them. These days I'm mostly hanging out in embedded land, but I at a minimum spend enough keeping in touch with what's happening in other industries, just so that I can at least understand what other people are talking about and what they're up to.

The general aerospace defense industry trends don't include C#.

Languages that have no use in my office outside a handful of projects (not intended for end users) include everything that's not: Ada, C, C++, Fortran, Jovial (being replaced), assembler (various forms), Delphi (one project, too costly to rewrite, too lucrative to drop). C#, Java, Python, Ruby, JS, Smalltalk, Rebol, Perl, Bash, C--, Lisp, Forth, Factor, Go, Rust, SML, OCaml, Haskell, Erlang, Racket, Scheme, F#, Visual Basic, BASIC (in other forms), etc. offer no value to the majority of our projects. If they're used, perl and a couple other scripting languages in particular, it's for tools for data analysis (scanning logs, turning hex dumps into useful printouts, etc.). In which case almost any language will suffice. But on our target hardware platforms, and given our target performance constraints, the initial listed languages are pretty much the only options. This is the industry trend.

tonyarkles 11y ago
You've done a very good job at illustrating the way I'm interpreting the parent and grandparent comment. Of the list of languages you just wrote out, I've never heard of "C--". I've written code in 22/31 of those languages. Depending on how you want to measure the duration of my career, I've got somewhere between 10 and 20 years of experience. If leaders in an organization haven't at least heard of a language that's in the top 5 of TIOBE (http://www.tiobe.com/tiobe_index http://www.tiobe.com/tiobe_index), I'd have some serious concerns when considering whether or not to work with them. These days I'm mostly hanging out in embedded land, but I at a minimum spend enough keeping in touch with what's happening in other industries, just so that I can at least understand what other people are talking about and what they're up to.