Top all-time · #5904
Robert Virding
Personal blog · rvirding.blogspot.comprogrammingsystems
Robert Virding writes Robert on anything, a personal blog at rvirding.blogspot.com about programming and systems. Since 2010, 13 different Hacker News readers have linked it 17 times, most often “Virding's First Rule of Programming (2008)”. The last post was in 2019, but the archive is still widely read.
Most-linked posts?
- Virding's First Rule of Programming (2008)9 people · 11 mentions · first linked 2015-04-28
- /2008/01/virdings-first-rule-of-programming.html2 people · 3 mentions · first linked 2018-04-15
What Hacker News says?
Thanks Robert Virding http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Elixir 1.9”Submitted The Erlang Rationale as a story · 211 points
HN discussionhttp://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Notes on structured concurrency, or: Go statement considered harmful”Submitted Virding's First Rule of Programming (2008) as a story · 58 points
HN discussionGood link. As a side note, I see sorokin's posts about DCOM, RPC and multi-threading: > Probably some unique thread-id can be propagated through the calls. And if incoming call has the same thread-id as one of our outgoing call it is handled inside this outgoing call as in nested message loop, otherwise a new thread from thread pool is used. This will create an illusion that two processes share the same set of threa…
Comment linking /2008/01/virdings-first-rule-of-programming.html
on ““DBus is seriously screwed up””Submitted Reacting to the Reactive Programming manifesto (2013) as a story · 3 points
HN discussionVirding's First Rule of Programming: Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang. https://rvirding.blogspot.com/2008/01/virdings-first-rule-of... (he is one of the creators of erlang / stars in Erlang the Movie)
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “What Erlang Taught Me About Distributed Systems”I had always thought that quote was attributed to Robert Virding: http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “The Development of Erlang (1997)”So this sounds a lot like an application of Virding's First Rule of Programming. Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang. http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Scipio: A Thread-per-Core Crate for Rust and Linux”Given the extent to which Erlang feels like microservices, I’ll submit Virding’s first rule for consideration. http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Everything old is new again: Microservices”Virding's First Rule of Programming (2008): Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang. https://rvirding.blogspot.com/2008/01/virdings-first-rule-of...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Why Elixir (2014)”OTOH, it is possible to add some of it back in. Check out Robert Virding's erlog ( http://github.com/rvirding/erlog ) and his explanation of how you can add backtracking to erlang ( http://rvirding.blogspot.com/2009/03/backtracking-in-erlang-... )
Comment linking /2009/03/backtracking-in-erlang-part-1-control.html
on “Ask HN: Who/What will do for Prolog what Clojure has done for Lisp?”Erlang/Elixir/BEAM emphasizes share nothing , allows (encourages) a bezillion user-space processes, then executes with a thread-per-core (by default). The actual number of schedulers (real threads) is configurable as a command line option, but it's rare, approaching unheard-of, to override the default. Virding's First Rule of Programming ... https://rvirding.blogspot.com/2008/01/virdings-first-rule-of...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Thread-per-core”http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “What's special about Erlang and Elixir?”Virding's First Rule of Programming: http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Unpacking Elixir: Concurrency”Virding's First Rule of Programming: > Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang. http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Erlang's not about lightweight processes and message passing”Virding's First Rule of Programming: http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
Comment linking /2008/01/virdings-first-rule-of-programming.html
on “Cancellation in Concurrency”
