4 ms·

What restrictive and how? Whole cluster orchestrators have been built with go (k8s, nomad), whole databases have been built with go (cockroachhDB), whole authen

by wg0 3y ago

What restrictive and how? Whole cluster orchestrators have been built with go (k8s, nomad), whole databases have been built with go (cockroachhDB), whole authentication systems have been built with go (zitadel, authelia), whole web servers have been built with go (Caddy, Traefik), whole DNS servers have been built with go (CoreDNS), whole key value stores have been built with go (etcd), some encryption has been built with go (age) so how it is restrictive and why didn't it restrict all those use cases? Not to mention, if you every spawned a container, there are 99.9% chances that somewhere go was involved along the way. There are other run times around (rust comes to mind) but none is production ready. Point is - restrictive should have restricted. It hasn't Minimalist isn't restrictive. EDIT: Added docker and restrictive not the same as minimal.

masklinn 3y ago
> What restrictive and how? The language is restrictive, in that you can't "play" with the language, it has a very fixed syntax / structure and no real way to make your own, much like Java or C#: no macros, limited runtime reflection (to say nothing of wholesale manipulation), control structures are heavily syntactic, etc... Hell, the designers built in a bunch of collections and behaviour (and special syntax) around those collections because they either did not want to or could not be arsed to make the language able to express them. > Whole cluster orchestrators have been built with go (k8s, nomad), whole databases have been built with go (cockroachhDB), whole authentication systems have been built with go (zitadel, authelia), whole web servers have been built with go (Caddy, Traefik), whole DNS servers have been built with go (CoreDNS), whole key value stores have been built with go (etcd), some encryption has been built with go (age) so how it is restrictive and why didn't it restrict all those use cases? That has nothing to do with anything? Literally all you're stating is "the language is turing complete therefore it can't be restrictive". > Minimalist isn't restrictive. No, it's not. And neither is the reverse. And go is restrictive, not minimalist.
kaba0 3y ago
Your comment only proves that one can write useful software with a restrictive language.

by wg0 3y ago

masklinn 3y ago

> What restrictive and how? The language is restrictive, in that you can't "play" with the language, it has a very fixed syntax / structure and no real way to make your own, much like Java or C#: no macros, limited runtime reflection (to say nothing of wholesale manipulation), control structures are heavily syntactic, etc... Hell, the designers built in a bunch of collections and behaviour (and special syntax) around those collections because they either did not want to or could not be arsed to make the language able to express them. > Whole cluster orchestrators have been built with go (k8s, nomad), whole databases have been built with go (cockroachhDB), whole authentication systems have been built with go (zitadel, authelia), whole web servers have been built with go (Caddy, Traefik), whole DNS servers have been built with go (CoreDNS), whole key value stores have been built with go (etcd), some encryption has been built with go (age) so how it is restrictive and why didn't it restrict all those use cases? That has nothing to do with anything? Literally all you're stating is "the language is turing complete therefore it can't be restrictive". > Minimalist isn't restrictive. No, it's not. And neither is the reverse. And go is restrictive, not minimalist.

kaba0 3y ago

Your comment only proves that one can write useful software with a restrictive language.