summaryrefslogtreecommitdiff
path: root/lib/rob
diff options
context:
space:
mode:
authorcinap_lenrek <cinap_lenrek@felloff.net>2015-09-05 00:37:32 +0200
committercinap_lenrek <cinap_lenrek@felloff.net>2015-09-05 00:37:32 +0200
commitce38e57e97b39b0cde532ff6a83b8881de6d2f3a (patch)
tree0872fa22b2e5315c57d3ed038f83bae1ef361553 /lib/rob
parentfaf3f0df06f7a994d58eb48cff7a6ccaa0b847a6 (diff)
parent891ca82987452bd77281dbd9d43bd5562322111a (diff)
downloadplan9front-ce38e57e97b39b0cde532ff6a83b8881de6d2f3a.tar.xz
merge
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.