Bayle Shanks's website: notes-computer-computerMisc

---

Software, Boolean Algebra, Turing machines, stored program, Hypertext, subroutines, assemblers, Compilers, Practically Compiling Human-like Notation (e.g. FORTRAN), Stack Principle, Time-sharing, List Processing (LISP), Vendor-Independent Exchange Standards for Software (e.g. COBOL and ASCII), Packet-Switching Networks, Quicksort sorting algorithm, Word Processing, The Mouse, Semaphores, Hierarchical directories, program names as commands (Multics), Unification, Structured Programming, Spelling Checker, Pseudo-Code (p-Code) Machine (in BCPL), Object Oriented Programming, Separating Text Content from Format, The Graphical User Interface (GUI), Regular Expressions, Generalized Markup Language (GML) the ancestor of SGML HTML and XML, Relational Model and Algebra (SQL), Distributed Network Email, Modularity Criteria, Screen-Oriented Word Processing, Pipes, B-Tree, Portable operating systems (OS6, Unix), Internetworking using Datagrams (leading to the Internet’s TCP/IP), Font Generation Algorithms, Monitor (the synch primitive, not the hardware device), Communicating Sequential Processes (CSP), Diffie-Hellman Security Algorithm, Make (automated build system using dependencies), RSA security algorithm, Spreadsheet, Lamport Clocks, Distributed Newsgroups (USENET), Model View Controller (MVC), Remote Procedure Call (RPC), Computer Virus, Distributing Naming (DNS), Lockless version management (CVS), Distributed Hypertext via Simple Mechanisms (World Wide Web), Design Patterns, Distributed Version Control System (DVCS), Secure Mobile Code (Java and Safe-Tcl), Refactoring, Web-Crawling Search Engines, Content-Based Addressing (rsync), Massively-parallel MapReduce?

---

in LaTeX?, sometimes, especially if latex gets interrupted in the middle of processing, the *.aux file may become corrupted; then running latex again gives you weird errors (eg about run-on/unclosed constructs eg "Runaway argument?...! File ended while scanning use of.."). Just delete the .aux file and re-run.

---

idea: 3d imaginary alphabet letter random avatars (instead of just textures etc) (and mb futuristic machine shapes, surrealist shapes, architectures, dresden codak shapes, geometric icon animations, architectures)

---

an article and associated HN comment points out that if you compress information, then the length of the compressed information tells you something about its content. Since encryption doesn't hide information about size, only content, that means that even if you encrypt a compressed thingee, you might get some leaks. So if encryption is desired, don't compress (and i guess, standardize the size of the input to the encryption).

---