summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorsl <sl@deckard>2023-03-16 01:27:52 +0000
committersl <sl@deckard>2023-03-16 01:27:52 +0000
commit0411083184b47915745fd3d5f2d29217cf14b4c9 (patch)
tree09177c308f8f6bfa1b376ca30d59f98ac60653b9 /lib
parent2d976ec561716a5ae1ac0739b32b30bc80fd21e9 (diff)
/lib/rsc: The plan9 port is becoming increasingly difficult to maintain and holds back non-plan9 development.
Diffstat (limited to 'lib')
-rw-r--r--lib/rsc1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/rsc b/lib/rsc
index 7abf7f924..6a1bce7ac 100644
--- a/lib/rsc
+++ b/lib/rsc
@@ -249,3 +249,4 @@ This past winter, as a side project, I spent some time getting up to speed on su
So it sounds like everyone is in favor of the entire generics proposal and all the semantics, and all we have left to hammer out is the bracket characters? Do I have that right?
Or perhaps Go will earn a reputation for doing telemetry well and people will say things like "Go is the only software with telemetry you don't need to worry about." I think it's too early to say which would happen.
I am not suggesting that instrumentation be added by the Go compiler to all Go programs in the world: that's clearly inappropriate.
+The plan9 port is becoming increasingly difficult to maintain and holds back non-plan9 development.