jtolds

27 ms·

91.
by jtolds 8y ago
fair! fixed
92.
Storj releases 90 page v3 white paper(storj.io)
36 points by jtolds 8y ago|4 comments
93.
Open Source Revenue Models in the Cloud Era(storj.io)
15 points by jtolds 8y ago|1 comments
94.
Git-treesame-commit: Create commits that match the file tree of another commit(github.com)
1 points by jtolds 8y ago|0 comments
95.
by jtolds 8y ago
why is this here what is happening
96.
by jtolds 8y ago
I kept waiting for this article to mention Julian Jaynes' hypothesis on the origin of consciousness but it never did. It's super fascinating though! Essentially, ancient history all the way up to Greece had this feature that peopl
97.
by jtolds 8y ago
The article is explicitly saying that green threads are better than callbacks, promises/futures, and async/await, yes. It is definitely making a comparison between those two styles of implementations, and it is saying that (what y
98.
by jtolds 8y ago
Where does it talk about other concurrency models at all? I just reread it to make sure I wasn't crazy.
99.
by jtolds 8y ago
The article isn't about concurrency in general though. It's explicitly about the question of how coroutines are called and implemented. The article is specifically about one facet of concurrent programming that arises when you use
100.
by jtolds 8y ago
On Linux, nonblocking IO has not always been great, so under the covers Go often translates calls to actually schedule blocking work on a threadpool somewhere, but from the perspective of the programmer, everything is implicitly using await
101.
by jtolds 8y ago
Nope! That's what Go does under the hood... and then eliminates keywords like await/yield and promises, because they're always implicitly there.
102.
by jtolds 8y ago
Please read http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y... It illustrates decisively that a language that doesn't hide async behavior balkanizes libraries into (at least) two camps for e
103.
by jtolds 8y ago
As the author of the linked post I would love to correct a misconception here. Go is fantastic about asynchronous programming and the fact that it hides it is one of Go's strengths. Channels are/were overused when I wrote that p
104.
Metrics Collection from Large Scale IoT Deployments at Vivint(infoq.com)
1 points by jtolds 9y ago|0 comments
105.
Time-series histograms with Rothko – metrics collection for large deployments(innovation.vivint.com)
10 points by jtolds 9y ago|1 comments
106.
Learn how to build and train a machine learning model from scratch(goc.vivint.com)
31 points by jtolds 9y ago|2 comments
107.
Learn how to implement Hindley-Milner type inference – Vivint's Game of Codes(goc.vivint.com)
9 points by jtolds 9y ago|0 comments
108.
Vivint's Game of Codes week long programming challenge ($20k in prizes)(goc.vivint.com)
13 points by jtolds 9y ago|1 comments
109.
by jtolds 9y ago
it's easily the thing I'm most proud of
110.
Introduction to Reed-Solomon and Berlekamp-Welch(innovation.vivint.com)
110 points by jtolds 9y ago|27 comments
111.
by jtolds 10y ago
There's an aside about how I've chosen precedence. The way I've defined operator precedence and binding, (\x.x) y is not a valid expression (parentheses only mean function application), and (λx.x y) returns y. You can argue
112.
by jtolds 10y ago
Oh, it definitely can be simplified a bunch. There's all sorts of stuff to prune out. I didn't even attempt to try and code golf at all. There's library definitions included in that snippet that probably aren't needed.
113.
by jtolds 10y ago
deaux!
114.
Whiteboard problems in pure Lambda Calculus(jtolds.com)
200 points by jtolds 10y ago|41 comments
115.
Writing Advanced Web Applications with Go(jtolds.com)
4 points by jtolds 10y ago|1 comments
116.
Monkit: Tracing and metrics library for Go(github.com)
5 points by jtolds 10y ago|0 comments
117.
by jtolds 11y ago
I perhaps communicated poorly, but the point of that section was to try and explain that the CSP model ( only using channels) was untenable in Go (even though it doesn't necessarily have to be in general), and that you'd almost c
118.
by jtolds 11y ago
Oh, so I did.
119.
by jtolds 11y ago
There is a deliberate leak in the example program. The author was attempting to illustrate that fixing the leak using just channels would be a challenge.
120.
by jtolds 11y ago
This post was written primarily as a response to http://www.informit.com/articles/article.aspx?p=2359758 , which, when it came out last June, frustrated me to no end. It then sat in my drafts folder for months until pat

More ›