The problem was that they had so little room for error. But I guess landing a rocket vertically on a heaving ship is also tricky, so maybe the problem is surmountable.
Many of the Soviet-era textbooks (mainly by Mir Publishers) are now published by low-cost Indian publishers and available on Amazon.in. Just search Amazon.in for Piskunov, Irodov, Vygodsky etc.
Unless it's a verb that ends with -ano. In that case, stress the preceding consonant. It's kind of like the difference between urAnus and Uranus. There are other exceptions, but that's the most common and important one.
It's a general rule of thumb, so it wouldn't apply to proper nouns, but I did edit to specify verbs rather than all words in general. I do appreciate the irony that the example I chose breaks that guideline.
There's also a floating point expression generator that tries to make your calculations more accurate, but it doesn't seem to give an analysis like this. These two tools would seem to go well together.
It's a simple and general method that works in many domains, which is an usual combination.
The other ways of solving the example of arbitrary heat sources and sinks on a plate range from hacky combinations of simpler methods, to tedious math, to complicated general methods. If you switch from heat to pressure distribution, you'd have the same types of options, but the specific methods would be different.
I've read the USB PD spec. What's wrong with it? It seems ok to me compared to other specs. And yeah it's long, but different sections are for different people with different roles.
In my anecdotal experience, the problem is that many programmers just don't like working to a spec.
More importantly the workforce is familiar with C/C++, how it’s listed on so many job listings. Which is kind of sad as a requirement. A programmer who can’t become productive with Ada after a few weeks (productive, not masterful) is not the kind of programmer anyone should be hiring for any job. The syntax is (almost) dead simple, for a reason.
Those jobs require competence from most contributors. Mastery from a few. And you can teach mastery to non-incompetent people, most of the time. Also, most jobs that Ada would be used for aren't time critical (in the sense of "Oh god oh god oh god we've got to ship yesterday!", unless it's F-35, which fortunately didn't use Ada because that would've saved them a lot of heartache). They program in 2-5 years for the project so 1 month to competency and then additional OJT from more experienced (with Ada and the system) over the rest of the time will produce mastery.
Ada is mostly used by professionals, not enthusiasts. It has a captive audience of governments and companies working on safety-critical systems where they have strict toolchain requirements or legacy systems. Pretty much the only thing that can move those users off Ada is to retire older systems, and rebuild their processes for C++. That's tough to justify when the language and ecosystem are still actively developed (paid, not free tools). Things like a language server are unimportant when your IDE must be qualified, and you're not allowed to install or use any software of your choosing. You will never see most of what goes on with Ada outside of a work environment. Its continued use is largely unaffected by anything you'd see in the open source community.
That's not at all what I'm saying. Aside from web development, most professional tools are only used by professionals because they cost money. It wouldn't make sense to judge something by the free toy versions that happen to exist.
Ada was released in 1980. It finally got a free compiler when the Air Force paid for one in 1995 fifteen years later and it took until 2001 for this code to finally be merged with the rest of GCC.
It definitely had no free compiler for a long time.
That it took 16 years to develop a free compiler for a relatively niche language in the era when relatively few people were online yet in any meaningful sense is not terribly shocking.
The language, going with the date of the first spec, is now 41 years old. So 25 years of its existence, there has been a free compiler. Quite a bit longer than the time spent without one.
I binge-read the RAQs a few months ago. So much great information. Thank you!
I also appreciated the consistent URL scheme because it let me easily scrape all the PDFs to read them offline. The one bummer is that the links at the end of the PDF versions seem to be broken now.
