Mr_T_

> I hope the golang community takes a thing or two from rust in terms of package management.

Go's dependency management was designed after analyzing Cargo and its problems: https://research.swtch.com/vgo-mvs

> They spent almost 10 years saying "we don't need generics", but now are implementing it

You're making things up. Not a single member of the Go team ever said "we don't need generics". In fact, the FAQ stated from day one that they "continue to think about it", and that "Generics may well be added at some point".

They were pissed nonetheless.

> What happened.

Capitalism came to the internet.

I don't feel awful.

You'll be happy with the latest developments: https://blog.golang.org/generics-next-step

Highly recommendable. It's the next modern classic after K&R's 'The C Programming Language'.

You mixed it up.

Syntax highlighting is like doing arithmetic using colored rods: https://groups.google.com/forum/#!msg/golang-nuts/hJHCAaiL0s...

Roman numerals is object-oriented design: https://groups.google.com/d/msg/comp.os.plan9/VUUznNK2t4Q/Ff...

Summary: http://go-proverbs.github.io

Because Nim is not dependently typed. You can't get sh*t done without dependent types.

If the Unix guys were smart they would have used an Idris REPL as default shell.

The 'String', '~str' dichotomy is really unfortunate.

LLVM is a C++ monstrosity that takes hours to compile. Other programming language projects have to maintain a "temporary" fork of LLVM to achieve their goals: https://github.com/rust-lang/llvm/tree/master

Please correct the title. The original title is correct: "Go generate: A proposal" the rest is wrong. This tool is not a preprocessor. It's as wrong as calling 'make' a preprocessor. It can be used to call preprocessors or more likely generators.

But why? Why not stop time instead?

You almost always need the byte count for protocols, buffers and stuff. For user-interfacing use-cases (e.g. editors) you probably want the glyph or grapheme count, not the rune count. Please remember, runes / code points, graphemes and glyphs are different things:

http://www.icu-project.org/docs/papers/forms_of_unicode/

People are programming in completely dynamic, duck typed languages and say that these languages are best without IDE.

But but but no generics! How dare they write production software without generics?!

See "3.5 Initialization indexes": http://plan9.bell-labs.com/sys/doc/compiler.html

> Looks like a very early dialect. C assumes everything is an int unless specified otherwise.

It looks beautiful, almost like a scripting language. No monster type signatures like

    const std::foo_bar<boost::blah_ptr<const xyz::bar::Bar&, baz::Baz>>&

Too late. Ken Thompson already put the back door in his B compiler.

Recently some ignorant, nescient C++ programmer called me a Java programmer, because I use K&R style and not his preferred Allman style. Even Stroustrup uses hanging braces (with the exception of function body opening braces)!

But does it have syntax highlighting?

You can order it at the Google store: http://www.googlestore.com/Fun/Go+Gopher+Squishable.axd

Clojure has [] and {} and #{} and '() and #() and : and ^ and @ and Foo. and .foo and ->, ... you still have to learn them to understand Clojure code.

> they may be calling those things difficult when comparing them to using an installation wizard

The Windows MSI package and the OS X .dmg have wizards.

I even use proportional font for coding.

He/she probably wanted to say "good": https://groups.google.com/d/msg/golang-nuts/FxELIOik2f4/X5x7...

One of the main selling points of Go is that builds are fast.

To be honest, I often feel as if I was in a brothel on some blogs with CoffeeRubyNodeScript highlighting. (However, the choice of colors on this one isn't too good either)