So Rust is stuck with <>/::<> while Go might be getting it right with []?
<>
::<>
[]
Oh, the irony.
I should have posted a link to https://groups.google.com/g/golang-nuts/c/7t-Q2vt60J8/m/daacBE2tBQAJ that expands the first post in the thread and makes reading easier. Can a moderator please update the post link to this URL?
it seems to require a google account to read… too bad
This one doesn’t require a google account (taken from HN):
https://groups.google.com/forum/?_escaped_fragment_=topic/golang-nuts/7t-Q2vt60J8
Good grief just pick something already.
This is turning into a undergrad designing their first language.
With the number of bad choices requiring huge transition phases a various well designed languages have had why rush now?
Quite the opposite. An undergrad would have just picked something & run with it. It takes many years of painful experience to know that this is a very risky proposition.
So Rust is stuck with
<>/::<>while Go might be getting it right with[]?Oh, the irony.
I should have posted a link to https://groups.google.com/g/golang-nuts/c/7t-Q2vt60J8/m/daacBE2tBQAJ that expands the first post in the thread and makes reading easier. Can a moderator please update the post link to this URL?
it seems to require a google account to read… too bad
This one doesn’t require a google account (taken from HN):
https://groups.google.com/forum/?_escaped_fragment_=topic/golang-nuts/7t-Q2vt60J8
Good grief just pick something already.
This is turning into a undergrad designing their first language.
With the number of bad choices requiring huge transition phases a various well designed languages have had why rush now?
Quite the opposite. An undergrad would have just picked something & run with it. It takes many years of painful experience to know that this is a very risky proposition.