|
The designers of Go agree with the collective experience of the last twenty years of programming that there are three basic data types a modern language needs to provide as built-ins: Unicode strings, variable length arrays (called “slices” in Go), and hash tables (called “maps”). Languages that don’t provide those types at a syntax level cannot be called modern anymore. (And what’s up with all the languages that claim all you need are linked lists? I’m sorry, this is not 1958, and you are not John McCarthy.) Go strings are UTF-8 because Go was designed by the guys who invented UTF-8, so why not? Everybody's talking about Go this week. What do you think about it?
|
|
|
|
|
Terrence Dorsey wrote: Go strings are UTF-8 because Go was designed by the guys who invented UTF-8, so why not?
You learn something new everyday!
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
"the directory the fundamental unit of packaging"
"this leads to the convention of using domain names as directory names"
The code still has to be stored in the file system? I thought he said this wasn't 1958.
I prefer to be able to have all the code in one directory.
And the ability to have all the code in one file (for trivial stuff at least).
Seriously, we shouldn't need to store code in files anymore.
|
|
|
|
|
Excellent point, I particularly dislike the use of domain names for packages.
I work on some of my own projects, and shouldn't haven't to register for a domain name to follow naming conventions.
|
|
|
|