summaryrefslogtreecommitdiff
path: root/lib/rob
diff options
context:
space:
mode:
authorstanley lieber <stanley.lieber@gmail.com>2015-09-03 17:01:49 -0400
committerstanley lieber <stanley.lieber@gmail.com>2015-09-03 17:01:49 -0400
commit891ca82987452bd77281dbd9d43bd5562322111a (patch)
treeae6ef0104c7f4b7c40ac999dd5c77430a67f5ef6 /lib/rob
parentb9eb7258bdb1b244af91dbe75595d55d3de810d4 (diff)
downloadplan9front-891ca82987452bd77281dbd9d43bd5562322111a.tar.xz
fortunes: Please be respectful in this forum.
Diffstat (limited to 'lib/rob')
-rw-r--r--lib/rob5
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/rob b/lib/rob
index 54206d5a5..ac1376ff8 100644
--- a/lib/rob
+++ b/lib/rob
@@ -312,3 +312,8 @@ I do not understand your criticism.
If you want to do the work, I will review the results.
Now, this is one of the things where the guy who blogged about me being a world-class jackass missed the point.
Please drop this.
+Maybe yes, maybe no.
+Please be respectful in this forum.
+It sounds reasonable and should be easy enough to implement.
+There is a widespread assumption that garbage collection and kernels cannot coexist but history shows a number of examples that demonstrate otherwise.
+Speaking as a one-time kernel writer, I would have loved to have garbage collection available inside the kernel. Hell, half the code in the kernel is tied to memory management.