f2f

> It would be neat if there was a Go Playground running the latest beta/RC version of Go. (Or is there?)

umm, no, not automagically. the playground is restricted. it would require some work to be put in to make it work with the latest release. that work isn't available for free.

instead, programmers are given a fips-compliant "black box" drop-in openssl replacement which they're not expected to question, right? :)

> Is anyone aware of scientific stack development in Go?

there's Gonum: https://github.com/gonum

> However, I know that Dropbox is one of the biggest Go users and it isn't in this success stories list. Anyone knows more about it?

they still use go for a lot of things, rust for a niche, which is why i made the other comment in this thread: we need to see more rust success stories (and nim, and elixir, and julia, and R, et cetera) because we need to be able to evaluate the best tool for a particular task. at this point everybody worth their salt in programming is a polyglot. "oh yah, i write everything in Go [but my html templates are all javascript]".

anyway, here's dropbox on go:

https://twitter.com/jamwt/status/629727590782099456

distributed system components talking over the network. this is not my personal opinion.

that said, i use go for everything. although most of the go code I've written has been in end-user applications, tools, and services, I still open up a listening port on localhost and serve web pages for any visualizations that i need to present. get the job done in the most boring way possible. that's its niche.

at this point i don't think Go needs any more fluffing. its niche is pretty well established and people should just get on with writing code that does what they need.

go is asymptotically approaching boring and that's one of the goals of its creators. let other new programming language stars shine: i'd like to see the niche rust settles in for example, and that needs code.

I think you missed the most important contribution of 9front: theo(1). it's like fortune(1), but with quotes from deraadt :)

Note that the std flag package accepts double-dashed arguments just fine, it only never advertises that it does.

VT has first submission for analysis in mid-august and 22/55 vendors convicting. from the comments, it seems like the story broke here in may:

http://news.softpedia.com/news/crooks-used-sql-injections-to...

This is not the first malware to use the Go language. Here is the first, from 2012:

http://www.symantec.com/connect/blogs/malware-uses-google-go...

i believe at the same time symantec decided to block every binary compiled with Go's compiler. because that was easiest.

also statically linked, at least on osx.

because it targets a specific audience. people not interested in editors may look it up because they're interested in Go, and vice versa.

editors written in Rust also announce it proudly: https://news.ycombinator.com/item?id=8734307, so do many other projects.

Great, another wow signal! Now we can rest easy that the first one wasn't a fluke... Regardless of whether this is the making of sentients or a physical phenomena we have one more reason to keep looking up in the sky :)

here's a good description of the wow signal and why it's important. if this one has similar characteristics we just increased chances of observing a really interesting phenomena by 100%:

http://www.universetoday.com/93754/35-years-later-the-wow-si...

it's a joke.

"To create a new node, an application performs any of the various ioctl() operations that accept a handle, passing the special reserved handle number of "3".

what a bunch of jokers :)

from the same page:

"When cgo is available, the cgo-based resolver is used instead under a variety of conditions: on systems that do not let programs make direct DNS requests (OS X), when the LOCALDOMAIN environment variable is present (even if empty), when the RES_OPTIONS or HOSTALIASES environment variable is non-empty, when the ASR_CONFIG environment variable is non-empty (OpenBSD only), when /etc/resolv.conf or /etc/nsswitch.conf specify the use of features that the Go resolver does not implement, and when the name being looked up ends in .local or is an mDNS name."

it's brian who acknowledged you. rob only wrote the code.

exegesis is a nice word to have in one's vocabulary. brian is a good exegesist (or is that exegesisticist?)

that guide is from 2012. things may have changed by now. i know we gave up stack ranking at $GIANTCORP since then.

every beginning is hard, but at least it doesn't deal with resolving DLL procedure addresses by hand, which it would've had to do if syscall.NewLazyDLL wasn't available.

after a while things will settle down and this "hello world" program will boil down to something much simpler, like:

     import "win"
     func PopWin(text string) {
          win.NewWindow(text, ...)
     }

also keep in mind that this is the version that purposely avoids using C and, as a consequence, can be cross compiled for windows on every machine with Go installed. there are benefits to that.

this makes the false assumption that updating dynamic libraries never introduces any new bugs.

> The windowing system is not a compositing window manager

8½ perhaps wasn't, but Rio is a compositing window manager.

previous "discussion" here: https://news.ycombinator.com/item?id=11767597

the time for grand OS ideas has long passed. here's an eulogy by one of the authors of plan9 and inferno (you won't hear anything from the authors of other operating systems except tannenbaum):

http://herpolhode.com/rob/utah2000.pdf

go get is just a mechanism, not the tool. there are other tools build on top of go get that ensure proper versioning.

minor factual adjustment: "go get" doesn't update a package once it's been downloaded. you need to force it.

"there is no guarantee that a build will be the same from day to day" is simply not true.

vendoring the tls library, nice!

it is complete, but it's a conversion, not a rewrite. i doubt anyone will spend the time to rewrite the compiler in idiomatic Go soon. bigger fish to fry :)

read what the post said. less than twice the compile times of 1.4, and that's for tip, not 1.6. 1.6 is way worse.

at los alamos during the manhattan project there were whole divisions comprised entirely of women who did the physics calculations. they were called the "computers".

http://www.theatlantic.com/technology/archive/2013/10/comput...

i'm not entirely sure about your timeline. plan9 came about in 1990. plenty of "sharing" back then was the unique property of distributed systems like amoeba.