Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rmcpherson
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
rmcpherson
11y ago
Direct link to the video: https://www.youtube.com/watch?v=4dwBS9nLPbE
92.
▲
by
rmcpherson
11y ago
Good point, but I also think it will be confusing to beginners who compile and run the program only to find that it always generates the same figure without any explanation as to why. Both the package documentation and text say that the gen
93.
▲
by
rmcpherson
11y ago
I noticed that the lissajous program in 1.4, as included, generates non-random lissajous figures since the random number generator is not seeded. I couldn't find any reference to this in the text and this could be confusing to beginnin
94.
▲
by
rmcpherson
11y ago
Great tool. It supports assembly generation for the golang Plan 9 toolchain as well. The author, Marat Dukhan, gave a great talk on this last night at the Atlanta Go Meetup. Slides are at https://docs.google.com/presentation
95.
▲
by
rmcpherson
11y ago
It's amazing that go-fuzz found 137 bugs in the standard library. The design is based on American Fuzzy Lop ( http://lcamtuf.coredump.cx/afl/ ) Dmitry Vyukov gave a great talk at Gophercon on go-fuzz and other dynam
96.
▲
by
rmcpherson
11y ago
> Visibility (public/private) is done via the capitalization of the field, method, or type name. This sort of restriction doesn't hinder usability, but it's quite annoying. While the capitalization of identifiers may be su
97.
▲
by
rmcpherson
11y ago
The best place to start, if you haven't read it, is the documentation here: https://golang.org/ref/mem For more detailed information on the garbage collector improvements and roadmap for 1.5 and beyond, this docum
98.
▲
by
rmcpherson
12y ago
"Finally, using a technique called principal component analysis, the algorithm decomposes the resulting signal into several constituent signals, which represent aspects of the remaining movements that don’t appear to be correlated with
99.
▲
by
rmcpherson
12y ago
I'm getting runtime errors when trying to run the example locally, and compile errors for others (e.g. suzanne.go, 'not enough arguments in call'). Was there a recent update that broke the code?
100.
▲
by
rmcpherson
12y ago
Are they allowing access to the sensor data from the watch? I'm particularly interested in heart rate. A brief scan of the documentation didn't show anything obvious.
101.
▲
by
rmcpherson
12y ago
Without a podium, he does look absurdly immobile on that large stage.
102.
▲
by
rmcpherson
12y ago
As a connoisseur of Minnesotan apples, I've always thought the SweeTango was a perfect iteration on the HoneyCrisp. Both are good though.
103.
▲
by
rmcpherson
12y ago
This may also be due to the Power Nap feature: http://support.apple.com/kb/ht5394
104.
▲
by
rmcpherson
12y ago
What's the specificity and sensitivity of this software? Are there any new techniques used here or is it a straight port of the JS tool mentioned?
105.
▲
by
rmcpherson
12y ago
Thanks for writing this. It's important to recognize the downsides of what is often considered only positive. It rings true for me especially.
106.
▲
by
rmcpherson
12y ago
Pacemaker firmware can almost always be updated using inductive or rf telemetry. In most cases it still requires an appointment with a cardiologist or similar physician though.
107.
▲
by
rmcpherson
12y ago
Try https://github.com/fatih/vim-go . It adds seamless support for all the go tooling to vim, including go-imports.
108.
▲
by
rmcpherson
13y ago
Check out CamliStore at http://camlistore.org/ . It's far more than backup, but it accomplishes that as well and supports S3 as well as Google Cloud Storage.
109.
▲
by
rmcpherson
13y ago
Will there be any change to minimum spot instance pricing? As far as I know this minimum is set by Amazon, but I don't see that pricing listed in the announcement here.
110.
▲
S3gof3r: Streaming, parallel S3 uploads and downloads at 1 Gbps+
(github.com)
1 points
by
rmcpherson
13y ago
|
0 comments
111.
▲
by
rmcpherson
13y ago
I missed that about fetching from shallow cloning. Thanks for pointing that out. I'll have to check out ori as well.
112.
▲
by
rmcpherson
13y ago
I don't see any significant performance improvements listed in the release notes. Git's memory-intensive handling of large files with most operations continues to make it difficult to use as a versioned, incremental backup tool. A
113.
▲
by
rmcpherson
13y ago
I missed your question about build instructions, sorry. I'll add them to the readme, but it's just "go get github.com/rlmcpherson/s3gof3r/gof3r" for the CLI once you have installed go. Usage instructions a
114.
▲
by
rmcpherson
13y ago
We use the version in the master branch at CodeGuard to transfer many terabytes into and out of S3 daily. While I hesitate to call it "production-ready", as that means different things to different people, we do use it in producti
115.
▲
by
rmcpherson
13y ago
You don't need the content length of what you are uploading for multipart uploads, see ( http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadIniti... ). For each part of a multipart upload that is sent,
116.
▲
by
rmcpherson
13y ago
Because of the lack of fast and reliable s3 clients out there, I built https://github.com/rlmcpherson/s3gof3r , that can do over 1 Gbps with ease, both multipart uploads and parallelized downloads. The killer feature, t
117.
▲
by
rmcpherson
13y ago
Go is quite popular in China, especially on Windows. I'm not sure of the reasons for that, but Rob Pike and Andrew Gerrand do mention it in this interview on the ChangeLog: http://thechangelog.com/100/