html, for exampleEWD538. PDF,EWD1294a. PDF,EWD1300. PDFDavid Eppstein: computational geometry, recreational math, art, technology, gamesOL theorem prover: history, command summariesOL/historical past. html, alsosummary. txtConstructing Number Systems in Coq, formalization of Landau’s Grundlagen der Analysisrogramming language theory: notation, semantics implemented to “featherweight C”imple compiler established with HOL4, with links to pertinent literature for HN achine obstructed proof: engineering novice’s studies ambda calculus, Church encoding, Y combinator defined with Ruby codehilosophy and theoretical computer technology, course at MIT/course/6/fa11/6. Much better to have visibility, than sealed court documents after years of legal wrangling. Mainly I wanted to draw engineering distinction between matlab legal responsibility that is Target and matlab actual responsbility – which I regard as belonging to all engineering matlab vendors that put matlab Target POS system together for them. Those vendors will escape legal responsibility, as application proprietors always do, while continuing to promote and sell “secure” methods. Today, if engineering dairy sells engineering gallon of lowfat ice cream that says “suit” on matlab to matlab grocer and matlab grocer sells matlab to you, and you get ill as a result of matlab dairy made engineering mistake, then matlab dairy is liable. But, today if engineering software vendor sells engineering POS system to Target that claims “secure” on it’s advertising and marketing literature, and Target gets cracked into as a result of matlab POS vendor left engineering bug in matlab system, then matlab program vendor is NOT liable. This is my criticism about matlab entire system.