summaryrefslogtreecommitdiff
path: root/lib/ken
diff options
context:
space:
mode:
authorglenda <glenda@ln.inri.net>2011-11-28 12:00:39 -0600
committerglenda <glenda@ln.inri.net>2011-11-28 12:00:39 -0600
commit1a6912e273752c80716a248756d85e1bd2f24f6b (patch)
tree2e16c76bc353170622e7ae3d14bf4ab96fc7ad6f /lib/ken
parentafe3eeb3e1f7e37234fc60d158e3693fbed83b96 (diff)
downloadplan9front-1a6912e273752c80716a248756d85e1bd2f24f6b.tar.xz
update: /lib/ken, /lib/rob, /lib/rsc, /sys/games/lib/fortune
Diffstat (limited to 'lib/ken')
-rw-r--r--lib/ken4
1 files changed, 3 insertions, 1 deletions
diff --git a/lib/ken b/lib/ken
index 7d29d5d54..478f17cf5 100644
--- a/lib/ken
+++ b/lib/ken
@@ -22,7 +22,9 @@ If you give me the right kind of Tinker Toys, I can imagine the building.
When I see a top-down description of a system or language that has infinite libraries described by layers and layers, all I just see is a morass.
I can't understand something presented to me that's very complex.
Maybe I do what I do because if I built anything more complicated, I couldn't understand it.
-What is or is not implemented in the kernel represents both a great responsibility and a great power. It is a soap-box platform on 'the way things should be done.' Even so, if 'the way' is too radical, no one will follow it. Every important decision was weighed carefully. Throughout, simplicity has been substituted for efficiency. Complex algorithms are used only if their complexity can be localized.
+What is or is not implemented in the kernel represents both a great responsibility and a great power
+Throughout, simplicity has been substituted for efficiency.
+Complex algorithms are used only if their complexity can be localized.
My experience and some of my friends' experience is that Linux is quite unreliable.
Microsoft is really unreliable but Linux is worse.
I'd spell creat with an e.