HN user

ch

942 karma

hellertime.com hellertime@gmail.com

@hellertime

http://www.hackernewsers.com/users/ch.html

(My submissions here are sporadic, and unfocused. I tend to use HN as my set of bookmarks)

Posts74
Comments214
View on HN
vectorized.io 7y ago

Autotune Series: Part 1, Storage

ch
5pts0
www.youtube.com 8y ago

Scylla Summit 2017: SMF: The Fastest RPC in the West [video]

ch
1pts1
senior7515.github.io 8y ago

Smf – We are fast: Latency benchmark vs. Kafka

ch
8pts1
github.com 9y ago

Haskell bindings for TensorFlow

ch
4pts0
rystsov.info 9y ago

Rystsov's site

ch
1pts0
blogs.igalia.com 9y ago

FileTea: low friction anonymous file sharing

ch
2pts0
brightside.me 9y ago

What happens when children don’t have the internet for a whole day

ch
78pts69
www.parsonsmatt.org 9y ago

Rank 'n Classy Limited Effects

ch
1pts0
github.com 9y ago

with – Program prefixing for continuous workflow using a single tool

ch
3pts1
www.scs.stanford.edu 9y ago

Tangaroa: A Byzantine Fault Tolerant Raft [pdf]

ch
1pts0
gist.github.com 9y ago

A composable pattern for pure state machines with effects

ch
3pts0
sprudge.com 10y ago

Is This the Most Elegantly Designed Cafe in New York?

ch
6pts0
news.mit.edu 10y ago

President Obama invites MIT entrepreneurs to give demo at the White House

ch
2pts0
concourse.ci 10y ago

Concourse: CI that scales with your project

ch
3pts0
www.open-scap.org 10y ago

OpenSCAP: Audit, Fix and Be Merry

ch
2pts0
blogs.janestreet.com 10y ago

A better inliner for OCaml, and why it matters

ch
135pts44
www.gsd.inesc-id.pt 10y ago

HyParView: a membership protocol for reliable gossip-based broadcast (2007) [pdf]

ch
6pts0
www.cs.cornell.edu 10y ago

SWIM: Scalable Weakly-Consistent Infection-Style Membership Protocol (2002) [pdf]

ch
3pts1
lgms.nl 10y ago

Faking the TCP handshake

ch
2pts0
www.thetimbre.com 10y ago

The Timbre – Podcast Reviews and Discussion

ch
7pts2
research.microsoft.com 10y ago

A Better Way to Store Data (2012)

ch
9pts0
www.scs.stanford.edu 10y ago

Dprof – Distributed System Profiling and Tracing [pdf]

ch
17pts2
github.com 10y ago

OpenZipkin: Brave

ch
1pts0
pykafka.readthedocs.org 10y ago

PyKafka

ch
2pts0
www.netblazr.com 10y ago

NetBlazr: Wireless ISP

ch
1pts0
www.cis.upenn.edu 10y ago

Mysteries of Dropbox: Property-Based Testing of a Synchronization Service [pdf]

ch
14pts3
blog.chaps.io 10y ago

Creating a BitTorrent Client in Haskell Pt.1

ch
3pts0
www.dspguru.com 10y ago

DspGuru

ch
190pts17
eprints.eemcs.utwente.nl 10y ago

Programming a Multicore Architecture Without Coherency, Atomic Operations (2014) [pdf]

ch
17pts2
staff.fnwi.uva.nl 10y ago

Keeping the PilGRIM at a steady pace [pdf]

ch
1pts1

I helped early on to review this plan for Alex and the Vectorized team, so I’m very excited to finally see it be released to the world.

Vectorized consists of quite the lineup of engineers (https://vectorized.io/team) and anyone who gets to be mentored by them will be gaining a huge advantage when it comes to Distributed System design and implementation!

Allocator Designs 6 years ago

Would the author mind commenting on how the diagrams were generated? They were very clear and useful.

Anatomy of a Scam 6 years ago

Don't investors ever ask to meet the team first? Seems like a fair ask if one is to invest.

Since there is relatively little information on the linked page, I'll put some questions I have here.

1. How does it work? It would appear the list is user curated. New submissions are from users (via submit) and ranking is based on hearts? Is there any future plan to be able to associate # of plays with a given episode (not sure if podcast app apis allow this).

2. In relation to #1 (an asked already by others), how can I subscribe to this in my podcast app?

Honestly, if they aren't asking for help formulating a solution, they also aren't asking for your suggestion to an alternative (even if you try to couch it in terms of a question). So just don't ask and you won't have the issue.

They still retain the global rollout for the other use cases detailed in the write up, so its generally tested, though not for this one use case as you point out. I suspect the tradeoff is reasonable, however having a short pre-stage deploy before global in all cases would be a more conservative option that would prevent an emergent push from becoming an even bigger emergency!

And we certainly have never interfered in any economic sense in Venezuela ... hold on, my producer is telling me that this is incorrect.

You ever sit there wanting to strike up a conversation with a random stranger, and have no idea where to begin?

I think that has more to do with the observed self-imposed isolation than is given credit in the article.

Nice insight into the amount of thought going into this design proposal. It's always tricky to introduce new syntax to a language and re-using the field access notation here isn't as icky an approach as it first looks.

I don't know enough about rust to understand how this would operate during compile time w.r.t if a user tries to define a field named 'async'. Is that no longer allowed or would the compiler be able to disambiguate?