golang-design / history Goto Github PK

The TOC doesn't work on our website. Filter it out using doc.go

The origins of Go

1. Thefirs twas cal le dSque ak (‘‘Alangu agefor communic atingwit hmice’’), whichprovide dalan-gu agefor handlingmou seand key board events, with statically created channels
2. The Plan9 operating system carried these ideas forward in a language called Alef.
3. iota is loosely from APL

From: https://www.gopl.io/ch1.pdf

Go 语言的起源

1. 第一次尝试引入CSP特性的编程语言叫Squeak（老鼠间交流的语言），是一个提供鼠标和键盘事件处理的编程语言，它的管道是静态创建的。
2. Newsqueak是一个带垃圾回收的纯函数式语言，它再次针对键盘、鼠标和窗口事件管理。
3. 在Plan9操作系统中，这些优秀的想法被吸收到了一个叫Alef的编程语言中。Alef试图将Newsqueak语言改造为系统编程语言，但是因为缺少垃圾回收机制而导致并发编程很痛苦。
4. iota语法是从APL语言借鉴，词法作用域与嵌套函数来自于Scheme语言（和其他很多语言）

摘录：https://books.studygolang.com/gopl-zh/ch0/ch0-01.html

we can dig more about the origin of Go and list this code compare.

as per golang.design/under-the-hood does.

Can we add all go package management history with tools or repos or discussion.

Such as:

References

https://github.com/golang/go/wiki/PackageManagementTools

We can add a gopher count history stats.

from https://research.swtch.com/gophercount

I think its necessary to know and research why _ was specifically chosen as the identifier to ignore values as Go was the first one to adopt it.

This link design/gobind return not found.
Standard Library -> Mobile -> design/gobind

See https://go.dev/cl/364859

Such as CSP etc.

https://github.com/golang-design/history#scheduler
for example:

I found golang/go#24499, and wrote a blog article about it.

@nigeltao : Amongst other things, standard library code is often read by people learning Go, so for that code, we favor simplicity and readability over raw performance more than what other Go packages choose. Neither position is wrong, just a different trade-off.

Maybe we can find more issues.