This is also true for the F-35 supplier team. Ada was seen as the technically superior and more robust language...

none of you guys sound like you have a clue

>reddit spacing

How is Ada safer than C?

>>what is debugging and linting
Things that help you get the code to compile, at least.

> (You)
>>reddit spacing
((you))

How is reddit spacing?

it isn't

>being this new

But I only one newline to separate paragraphs

>340,534,53%
...what? why is there a percentage?

>one newline
>not leddit spacing
go back

reddit spacing is

double spaced

fucking retard

only newfags bring

up reddit spacing

the f-35 project probably predates js, yes

>reddit spacing
yikes

Are you really using the F-35 as an example of a successful project?

redditspacingishavinganyspacesinyourpostswedontusespaceshereyoupieceofshitstoner

>Wreckage from a Japanese F-35 stealth fighter jet has been found, a day after it disappeared from radar over the Pacific Ocean.
>pilot not found
>successful

>concern over the ability to successfully staff the software engineers
Why do executives always underestimate the ability of programmers to learn new tools? Imperative languages are not that different from each other. Any decent C/C++ programmer could pick up Ada in a week. Maybe they'll be slow the first month but that doesn't matter in a multi-year project.

This is not like engineering, where e.g. mechanical and electrical are totally separate disciplines. If you want something written in Ada, you don't need to hire an Ada programmer, anyone can pick up the language.

C causes Boeing 737MAX
Ada doesn't cause Boeing

>yikes
soi

Liability.

Selling to third world airlines is what causes 737max. All they had to do was pull back on the yoke enough to cancel out the trim. Lion air captain managed the plane fine until he started trouble shooting and had his first officer take over the controls. Elevator blowback is doubtful given the airspeeds were under mach 1, more than enough elevator authority to cancel out max horizontal stabilizer trim. No question that Boeing had a shit design with no triple redundancy, but the pilots should have been able to compensate.

It allows for easier formal verification of code correctness

Also the language itself encourages care e.g. IF statements must have a closing FI so it's more obvious when control flow is fucked up.

Assembly should be 100%

Thats SPARK a subset of Ada.
A large part of why SPARK and Ada are big name certification languages is because of strong typing. You can't make fuck ups like you can in C due to the weakly typed system that does implicit rules on your behalf. Ada and SPARK also feature many runtime safety checks by default and can be turned off after testing. The whole benefit of these languages is to find bugs and logic mistakes during early dev rather than in the field.

>many of the university students simply refused to work Ada as it was not seen as a marketable experience base.
Kek, but millennials killed off Ada and the F35.

>You can't make fuck ups like you can in C due to the weakly typed system that does implicit rules on your behalf.
C is strongly typed...

That's a shame. I would love to write Ada for a living. Sounds comfy.

C is staticly typed, but is not very strongly typed. Strong/weak is more of a continuum and static/dynamic is more either/or.

C is weak because it does implicit conversion between pointers, ints, floats, different sized types, etc. It's relatively difficult to generate a compile error for types in C. A good compiler will print warnings but the language allows for very loose behavior.

>every single piece of software written in it has severe bugs that need to be ironed out over multiple iterations
Or they could get it right the first time, your post looks like a digital distribution shill to me

I'm sure you can find a job if you're willing to travel. It's a niche language used in weird industries still, but I'm sure as languages like Rust pop up managers are going to shift focus to them because it's cheaper to hire for.

>very loose behavior
that's how i like it

Attached: 1560384993657.jpg (640x800, 99K)

>if you're willing to travel
But I'm not. I have a pretty nice life out in the country. I wouldn't be happy in a city.

>begin / end
>{ }
is there any a priori reason why one is better than the other?

Javascript's type system is not acceptable for use in any security critical system.

{ } is fewer characters.

by that logic, perl is the perfect language

The terseness/verbosity of a language is a spectrum.
Both extremes are shit.

>Arguments about the lack of reliability in either C or C++ are addressed by programming standards restrictions and SCA checks. In truth, this approach is probably more consistent and robust than the manual checks used for previous development efforts including Ada. The typical software engineer develops the software, runs the SCA tool, makes fixes, and then submits the code for inspection – thus there is little difference between developing Ada code where the compiler makes automatic checks and developing C/C++ code where the SCA tool checks for compliance immediately after a successful compilation.

adacucks btfo

Not sure why you're surprised by this. It's not like Ada has exclusive rights to doing various static analysis checks. Lint has been a thing for decades now to supplement what C lacks and there's even better tools when you have people paying for you. Even professional Ada devs supplement with static analysis tools since the language spec won't catch everything.

You are a fucking retard

I can confirm. The more advanced data structures and the contracts take a while to get used to, but after a couple of months you can be completelly proficient.
The std is top noch (funny thing, C++ took inspiration from it) and very well documented too

>Thats SPARK a subset of Ada

Take a look at Ada2012

>one major vote of confidence in this approach is that because processor obsolescence many of F-22 safety critical systems are embarking on a path to recode them in C from Ada 83 language because of many of the same issues we dealt with on the F-35 program. (Nobody wants to code Ada anymore)

Sure seems like a success to me cucks. To date there are hundreds of F-35s in use. This is by far the most advanced and successful fighter jet to date.

google.com/amp/s/www.forbes.com/sites/lorenthompson/2019/01/15/the-f-35-fighter-is-a-success-so-how-do-we-keep-it-ready-reliable-for-the-next-50-years/amp/

>C and C++
Should've been done in Python

>Why do executives always underestimate the ability of programmers to learn new tools?
Because programmers tend to be shitheads who refuse to learn anything ever again once they've graduated from school

I think there were other reasons and they don't want to publicly say why.

adacore.com/uploads/customers/CaseStudy_Eurofighter.pdf

Europe's Eurofighter Typhoon used Ada and over 500 developers.

Ada > C
but only if you can front load the requirements to a significant degree. The F-35 has been a mess from the start.

Attached: 1429284779965.jpg (328x328, 50K)

>Any decent C/C++ programmer could pick up Ada in a week.
But then you would have to pay those guys more because they would have to learn Ada and be decent programmers to begin with. Why spend money on this if you can give yourself a bonus instead?

>F-35
>not "the F-35"
Fucking stop.

Good, glad to hear the F-35 won't abort and fall out of the sky due to Ada's insane exception handling.

en.wikipedia.org/wiki/Cluster_(spacecraft)?wprov=sfla1

This has nothing to do with overflow or exception handling. They used code for a different rocket.

People here seems to have quite stong opinions about embedded C while not even discussing MISRA.
Confirmed true:

Just a reminder:
The f35 is is the safest and more successful Aircraft program in US's recent entire history.
People don't know about how many f16s, f18s and f15s were falling out of the sky during their development.
F16s killed something like 16 test pilots.
>Inb4 1.2 trillion
That's for over 2,000 f35+ parts intill 2040.
That's 1/3 the cost of maintaining gen 4.5 jets to 2040.
>Inb4 f35 crashes
One cought fire due to a backwards installed fuel line.
Another crashed due to a flightline dumb ass.
The nips crashed one they built, so probably just growing pains from a new production line.

Attached: 1456222746404 (1).jpg (1024x905, 182K)

wtf

It just gets worse the further back you go, too. Combat aircraft development is pretty much always a clusterfuck, it's the worst kind of combination of complexity, political interference and ineptitude, and untested cutting-edge tech (because why build something that ISN'T cutting edge when your enemies might be?), and historically it's not uncommon for fighters to be awful in their first iteration and not get good until later models.

>and historically it's not uncommon for fighters to be awful in their first iteration and not get good until later models.
Replace "fighters" with "any milspec hardware" and it would still be correct.

I bet a decade of development went into just configuring the static analysis tools for C to not puke out ungodly amount of false positives

Always the same fuckig example that has nothing to do with Ada.

They used the code, with the acceleration ranges, of the ariane 4 for the much more powerful ariane 5. In the specification the security system was suposed to, and did, explode if the accelerometers started doig something stupid.
The overflow was a design solution as it mas much easier to handle than a exception, both would mean a too big acceleration and thus a faulty rocked.
It was fucking made that way, but C cucks can't still understant it after 20 years and still cry "but muh 501!"

Fortran2018 is the only sane choice. Too bad this is an insane world.

Attached: 1534612691612.jpg (480x275, 31K)