minimal

TwitterFacebook
Get flash to fully experience Pearltrees
chess

writing

Last weekend I was thinking about Ashwin Ram's Short Ballad Dedicated to the Growth of Programs and the result is LYSP: a tiny, lightweight Lisp interpreter closely following the tradition of the earliest implementations. It is dedicated to the inventor and early implementations of that language, which is 50 years old this year. If you partially evaluate LYSP in Latin it yields "50 Years of Symbolic Processing". (IBM once made a dialect of Lisp called Lysp and published a paper about it. As far as I know, it died shortly thereafter and so I have unilaterally swept and reallocated the name. If you know differently, please tell me.) http://www.piumarta.com/software/lysp/

LYSP

The Definitive Guide to a Minimalist Mac Setup mnmlist.com

http://mnmlist.com/minimalist-mac/ I highly recommend this setup for anyone looking to keep things simple and fast. It’s not recommended for those who are into the latest, coolest applications or who aren’t into simplicity, or who have heavier needs than mine. Philosophy 1. No clutter . A cluttered desktop is a distraction.
http://www.tinycorelinux.com/ It starts with a recent Linux kernel, vmlinuz 3.03, and a 5MB core.gz. MicroCore 8MB is simply the kernel + core.gz - this is the foundation for user created desktops, servers, and or appliances. TinyCore is simply the kernel + core.gz + Xvesa.tcz|Xorg.tcz + Xprogs +fltk-1.10.tcz + (user's choice of Window Manager) + wbar.tcz TinyCore becomes simply an example of what the Core Project can produce, an 12MB FLTK/FLWM desktop. CorePlus ofers a simple way to get started using the Core philosophy with its included community packaged extensions enabling easy embedded frugal or pendrive installation of the user's choice of supported desktop, while maintaining the Core principal of mounted extensions with full package management. It is not a complete desktop nor is all hardware completely supported.

Tiny Core Linux, Micro Core Linux, 10MB Linux GUI Desktop, Live,

http://www.daemonology.net/blog/2009-09-04-complexity-is-insecurity.html

Complexity is insecurity

As I've been writing code for my Tarsnap online backup service over the past three years, I've gone out of my way to make it as secure as possible. I've written previously about the importance of carefully designing security systems before writing any code, thinking about mathematical proofs-of-correctness while writing code, cryptographic research concerning key derivation functions, and recommendations for using cryptography , all of which have informed my work on tarsnap; and I've made the tarsnap client source code available for public review -- after all, I refer to tarsnap as being "Online backups for the truly paranoid", and nobody who is truly paranoid would want to download and run code without inspecting the source code and compiling it themselves. However, there is a very important aspect of tarsnap's security which I haven't discussed previously: Complexity -- or rather, a lack thereof.
Floppy booting, Open Firmware, Bitlash, more Movizt. As a child, I was fascinated by small, intricate things. Wind up clocks and tree seeds were two of my favorites. This continues through my programming. http://kmkeen.com/tiny-code/index.html

Tiny Code: New additions: Movitz Lisp, Ocaml Mindstorm

scratch.py -- hyper-fast mini-webapp production, in Python

http://www.speakeasy.org/~lion/proj/scratch/ Take your webbrowser to http://localhost:8000/ and you should be greeted with a page listing helloworld as a function. Click on it, and you'll see: "Hello, world!" Note that when you specify field width & height w/ _80 or _40_20 (or whatever,) that you have to change the variable use within the code, too... Real bummer, hunh? I know.