122 karma · joined June 5, 2014
https://archive.org/details/AmericanBlackChamber
"The cryptography historian David Kahn called the book "the most famous book on cryptology ever published."
I can't link to the slide because of the way these pages are defined:
slide 11: The presented argument order in the ASCII-art of Red, Blue, Green I think should be Red, Green, Blue to match the usual initialism.
I could not find a way to submit a pull-request for this presentation, and my search-fu on github failed to find the associated repo, and there were no links I could find in the presentation to submit comments.
It is an old idea called "mind share" [1] or in this case technical-mind-share, a vendor should want the largest possible community of technical people interacting with their technology and attempting to use it in as many niches as possible.
I'm not sure it even has to be uniformly cheap, as long as there is a low-cost entry point to hook people. If the price ratchets up from that low entry point but it is a compelling solution people will want it in their technical lives and get it funded somehow.
[1] https://en.wikipedia.org/wiki/Mind_share [2] I would point to RISC-V as another example of a newly popular machine architecture due to its initial low-cost. [3] noting the preferenced technology must meet the minimal acceptable threshold for all the usual dimensions.
"Code availability. The numerical code has been developed
with a dedicated application to the DAMPE data analysis. Due
to the uniqueness of the DAMPE design and the complexity in-
volved in the data analysis, the software package has limited
application to the relevant community. We have opted not to
make the code public."
I'm just an IT guy, and not familiar with how disciplines distribute source-code for this type of analysis, but is this approach common? what does "...limited application" mean here and why not release the code?Extending the Data Base Relational Model to Capture More Meaning by E.F. Codd IBM Research Laboratory published in Volume 1 Number 1 (March 1979) issue of AUSTRALIAN COMPUTER SCIENCE COMMUNICATIONS, which incorporated papers from the 2nd Australian Computer Science Conference 1-2 February 1979 in Hobart, Tasmania.
http://www.retrocomputingtasmania.com/home/projects/history/...
I would argue that our efforts to preserve what is a unique time in computing history, the birth of the electronic computer (and the software abstractions they support), has at best been feeble, and at worst derelict.
Generally we have made a passable effort at preserving good examples of the early machines, however our effort around preserving the important milestones for software has been dismal. Trying to reconstruct a coherent view of the history of ideas across the early software arena is now problematic and daily becoming more difficult.
Summoning a small amount of polemic our attempts so far at preserving the software side are akin to burning 99% of oil paintings, since "surely one example of an oil painting represents all of them" approach to the history of software.
A small group is making an effort to find and capture software artifacts:
http://www.softwarepreservation.org/
My own list (solely reflecting my interests) is here:
http://www.retrocomputingtasmania.com/home/projects/spg
If anyone is interested in these efforts please consider helping or chasing down software that you consider is important and seeding the Internet where practical.
One terabyte in 1.5mm thick device, 15TB capacity in the usual 2.5 inch SSD form-factor.
Byte-addressable, unlike block-based SSD. Optane could nicely complement burst-buffer implementations in HPC.
• 32-bit processor core
• IA-32 instruction encoding [1]
• 5 stage pipeline
• Harvard architecture
• 8KB of on-chip data SRAM
• 32KB of on-chip data/execution FLASH
• Deterministic 21 Cycle interrupt latency
• Minimal processor initialization for fast power-up
Above from the PDF
[1] IA-32 architecture subset, no segmentation support.
http://www.softwarepreservation.org/projects/apl/Manuals/APL...
If we can get a working Burroughs B6700 emulator (see elsewhere in this thread) we may have enough pieces to see APL\700 working again. We're seeking the APL\700 Installation Manual (Form 5000805) if anyone has a copy.
Note the use of the "\" in the name was intentional according to Jim Ryan, "APL "expands" the '700 series" (comp.lang.apl)
As drallison notes, APL\700 was a compiler to an intermediate language.
including Kildall's APL implementation (still needs to be proof read), but also note that Niklaus Wirth's programming language predecessor to Pascal known as Euler is there too.
Another interesting piece of source-code you will find there too is a Burroughs B6500 emulator, B6500 MCP and B6500 ESPOL compiler written for the B5500. The B5500 was used by Burroughs as the development platform for the B6500 which was the follow-on from the B5000 family.
You can see the B6500 emulator running in this short film: https://www.youtube.com/watch?v=KOElQuCqj0Y#t=3m37s
I'm hoping we can re-create those few seconds of video once we have this B6500 software functional again.
http://www.retrocomputingtasmania.com/a/retrocomputingtasman...
There are also several other interesting or unusual Ada compilers still to be found too, notably:
Ada for the Intel iAPX-432 (arguably an instruction set architecture tailored to Ada)
Symbolics Ada - an Ada implemented in Lisp
Ada for the inmos Transputer - an Ada for a parallel computer architecture