3 ms·
Arguably it's more a comeback from Alef, this time with GC faction winning. (C begat a bunch of research languages, those begat Alef, a conflict about whether
by p_l 5y ago
Arguably it's more a comeback from Alef, this time with GC faction winning.
(C begat a bunch of research languages, those begat Alef, a conflict about whether to add GC led to Alef dying and its features reimplemented as Plan9 libraries with side effect of Limbo, years later Go is built on top of Plan9 C compiler & runtime with syntax sugar for Alef-derived libraries).
- pjmlp 5y agoSure, still neither of them have Oberon-2 method syntax nor UNSAFE meta package. Plan 9 compiler was used as means to quickly get a prototype running, and naturally Rob Pike knows the toolchain quite well. I also agree with the Alef remark.
- p_l 5y agoThe legacy of Plan9 compiler stack still remains despite being rewritten purely in Go - I'd say that Pike liked his previous design :)
- monocasa 5y agoLol, I actually realized that the other day, hacking on the golang compiler. The amd64 cpu instruction definitions are in a file called asm6.go and I was all "wait a minute, I recognize this from plan 9", where the amd64 compiler, linker, and assembler are 6c, 6l, and 6a respectively.
- p_l 5y agoBefore Go 1.5, it would literally keep around an alternative port of Plan9 C compiler plus all core system libraries, and I think it still does for C ffi