f2f

18 ms·

121.
by f2f 10y ago
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...
122.
by f2f 10y ago
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
123.
by f2f 10y ago
also statically linked, at least on osx.
124.
by f2f 10y ago
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/it
125.
by f2f 10y ago
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 g
126.
by f2f 10y ago
it's a joke.
127.
by f2f 10y ago
"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 :)
128.
by f2f 10y ago
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
129.
by f2f 10y ago
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?)
130.
by f2f 10y ago
that guide is from 2012. things may have changed by now. i know we gave up stack ranking at $GIANTCORP since then.
131.
by f2f 10y ago
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 "he
132.
by f2f 10y ago
this makes the false assumption that updating dynamic libraries never introduces any new bugs.
133.
by f2f 10y ago
> The windowing system is not a compositing window manager 8½ perhaps wasn't, but Rio is a compositing window manager.
134.
by f2f 10y ago
previous "discussion" here: https://news.ycombinator.com/item?id=11767597
135.
Plan 9: Part 1: Whither Plan 9? History and Motivation(pub.gajendra.net)
10 points by f2f 10y ago|1 comments
136.
by f2f 10y ago
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&#x2
137.
by f2f 10y ago
go get is just a mechanism, not the tool. there are other tools build on top of go get that ensure proper versioning.
138.
by f2f 10y ago
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.
139.
by f2f 10y ago
vendoring the tls library, nice!
140.
by f2f 10y ago
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 :)
141.
by f2f 10y ago
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.
142.
by f2f 10y ago
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/archi
143.
by f2f 10y ago
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.
144.
by f2f 10y ago
you're being deliberately obtuse. the uniformity in plan9 didn't mean everything spoke the same protocol, but that every resource could be shared everywhere. you wouldn't want your tv tuner card to talk ascii, but with 9p and
145.
by f2f 10y ago
and every single one of those was profitable from day 1!
146.
by f2f 10y ago
but the existence of the proposals assumes there were internal discussions, which is counter to the argument that go devs don't care about generics. had anything good come out of that it would've been published in the open. as it
147.
by f2f 10y ago
"The intent is not to add generics to Go at this time, but rather to show people what a complete proposal would look like. We hope this will be of help to anyone proposing similar language changes in the future." This started in 2
148.
by f2f 10y ago
https://news.ycombinator.com/item?id=8817990
149.
by f2f 10y ago
no, it wasn't. the go compilers initially came from Plan 9, which hasn't seen any C++ code ever :)
150.
by f2f 11y ago
it seems to me that the Go package can easily slot in golang.org/x/unix, where all the extra syscalls not present in the fixed stdlib syscall package go. that's a minor point. if pledge becomes widespread in usage it will get

More ›