It has been suggested I should try out Go, it was someone on /prog/
Please share any intensely commented code you know of written in it. Or any documentation besides the tutorial, effective go, and the google tech talks which are all shit.
The only thing remotely useful is the reference manual but it suffers from the same issue: They describe everything as a concept not a function and the examples have context.
>>11
So I am not smart enough?
that's sad so I should stick to C and never ever learn something else?
>>8
Code: Not commented enough, written for an by people who already know it
Documentation: Again they provide not enough context for the examples and the explanations are descriptive not functional.
I am looking at the 2011 Ants AI challenge example that seems helpful.
>>20
Stillborn and unoptimized. Surely not a candidate for serious mission-critical apps.
The syntax sucks. Admit it. Pike was never a good language designer to begin with. If memory serves me right, they had a few WTFs early on regarding Go's syntax. Obviously a hack job, it was never designed with solid understanding of what they're trying to achieve. It's practically PHP all over again.
>>30
you cant make Erlang run faster, they tried making an Erlang compiler that compiled to machine code and it only ran slightly faster than the regular interpreted one
Forced OOP is where I draw the line. And python has version bloat, I rage about it even when I am just a user not a developer.
Go could turn out to be worse, but you never know till you try it.
Name:
Anonymous2012-08-19 15:01
>>39
If you'd bother to use them you'd actually know they're excellent languages, it's all about using the right tool for the job.
Name:
Anonymous2012-08-19 16:31
>>40
good you used the usual tactic of badmouthing the language and trying to encourage debating something else.
Now if someone were to respond to the topic that would be a really surprising turn of events! I don't care if it is the worst language ever, you understand me?
Just give me some useable free documentation.
>>49
Do you have much prior programming experience? Perhaps Effective Go is too terse.
Name:
Anonymous2012-08-20 9:59
>>48
'fine', 'good enough'... but it can still be shit.
Name:
Anonymous2012-08-20 10:41
>>50 Variables are declared with the var keyword, followed by the variable name, and finally by the type. The existence of a specific keyword for variable declarations makes it easy to differentiate them from other types of statements.
consider this sentence, it is not in effective go and there is no equivalent to it. That might seem not really problematic but the same practice is kept for non-trivial things too.
>>52
Approximately half of that sentence is useless. It can be reduced to: Variables are declared with the var keyword followed by the variable name its type.
>>61
Seriously, how can /prague/ be so hostile towards force indentation, which is practical, yet completely accepting of the fact that Go forced you to capitalize variables, which nobody in their right mind does in any other programming language?
>>62
This is especially troublesome giving that Go pride itself on being 100% UTF-8 compliant, yet you can't even have a Korean variable because there's no way to capitalize it.
>>62`
>implying FIOC isnt the most obtuse unpractical shit ever
>implying anyone on prog accepts Go in any way shape or form
/a seabed camelspore kilobag/
Was on the cat-v site, I don't know maybe that's just me but I need documents to tell me exactly what is going on instead of just a sparse description when learning something new.
Maybe that is helpful for somebody.
I learned something from this thread to: even if this is the most popular programming board among the chans it seems generally better to post on some other chan. Sadly that even has become some universal truth.