News for hackers. Stuff that matters.
Re:An Introduction to the Go Language by tptacek on Thursday June 27, 2013 @12:24PM (#5953107)
Python's built-in HTTP server isn't well-suited for production apps. Golang's HTTP server is the production standard. That's not an apples-apples comparison.

Ruby and Python "have" stacks, queues, and (in Python's case) deques, but they're rarely used, because, like Golang, they have a flexible variable-length array ADT and a table ADT.

Golang has lists and rings, along with slices and maps, which capture "queue" and "stack" easily. More importantly, unlike Python and Ruby, Golang provides direct control over memory layout and a safe pointer abstraction; it's much better suited to building fussy data structure libraries than Ruby or Python.

I'm not sure I'd choose a language based on the richness of its UUID libraries.

It's funny to critique a language for "not even having" a tool that few other development environments have "until 1.1".

Re:An Introduction to the Go Language by gnuvince on Thursday June 27, 2013 @02:33PM (#5953917)
> Ruby and Python "have" stacks, queues, and (in Python's case) deques, but they're rarely used, because, like Golang, they have a flexible variable-length array ADT and a table ADT.

When all you have is a hammer...

Re:An Introduction to the Go Language by tptacek on Thursday June 27, 2013 @02:55PM (#5954043)
The reality is that Python lists usually work as serviceable queues and stacks. Criticizing a language for not having a standard queue or stack is a little weird.