2 ms·
> None of these problems are ever going to be solved by a programming language. Indeed but that wasn't the intention, the problem that the DoD had was that dis
by noir_lord 11y ago
> None of these problems are ever going to be solved by a programming language.
Indeed but that wasn't the intention, the problem that the DoD had was that disparate systems with decade long service lives written in a huge variety of languages was going to cost them more and many of those languages where relatively unsafe languages.
Ada was built as a safer systems language that could replace many of those prior languages, a role it very much succeeded in - dysfunctional organisations are going to be dysfunctional whatever language you use but that doesn't stop one language been "safer" (against a given set of metrics) than another.
Lots of modern systems are still written in C or C++ but largely because of organisational/real world reasons (availability of programmers fluent in those languages, the sheer complexity of modern systems, you can argue that writing Ada on top of a Linux kernel might not be the sanest choice).
Ada still has it's niche though and if nothing else it showed that a language can be designed with safety in mind and it also prototyped many of the features that cropped up in later languages.
- pjmlp 11y ago> Ada still has it's niche though and if nothing else it showed that a language can be designed with safety in mind and it also prototyped many of the features that cropped up in later languages. Algol already showed that in the mid-60s, check Burroughs computers for example. It was the C designers that decided to ignore safety.
- hga 11y agoBCPL, actually, given the really minimal computer resources the group that started it started out with. BCPL had one data type, the word, which for any given port was chosen to be the natural machine word size, like C's int ideally is. Team UNIX(TM) continued that approach, since they also had meager computers to start with, a PDP-7 with I suspect not a lot of memory, then a PDP-11(/20) with the extra memory bank option, then a PDP-11/45, which while a big and fast minicomputer in it's day, still only allowed 64 KiB of instructions, 48 KiB of data, and 8 KiB of stack for a program (the latter was the usual way to split up data space with its 8 KiB page MMU).
- pjmlp 11y agoStill memory requirements had nothing to do with ignoring safety, given what was already possible with Algol in 1961.
- hga 11y agoWhen you start out with 256 36 bit words on a good day and never get more than 1,024, it can cramp your style: http://pastebin.com/UAQaWuWG http://pastebin.com/UAQaWuWG (by our very own nickpsecurity).
- pjmlp 11y agoHe used information given by me for that article. :) Just as info, here is the brochure of the B5000 from 1961. http://www.cs.virginia.edu/brochure/images/manuals/b5000/brochure/b5000_broch.html http://www.cs.virginia.edu/brochure/images/manuals/b5000/bro...
- gaius 11y agoAlso see https://en.m.wikipedia.org/wiki/JOVIAL https://en.m.wikipedia.org/wiki/JOVIAL Ada by the way is alive and kicking; nowadays it's known as PL/SQL in Oracle.
- noir_lord 11y agoIt's alive and kicking as its own language as well, hell they just released GNAT and its IDE for the rpi2. Something on my long list of things to play with when I have time :).