mononcqc

23 ms·

61.
by mononcqc 8y ago
no idea, did not write that one.
62.
by mononcqc 8y ago
For Learn You Some Erlang, I used hand-made drawings that I would scan, and then trace over using either photoshop (initially) and then Illustrator (when I knew the book would go to print).
63.
by mononcqc 8y ago
I've also written http://propertesting.com/ , which I'm currently working to turn into a full book with Pragmatic Programmers (with Elixir translations included as well, so that everyone on the BEAM can benefit :)
64.
by mononcqc 9y ago
The BEAM will totally interrupt a process that is currently processing a message. It does so based on a 'reduction' count, roughly equivalent to each function call. Since there is no looping construct, any iteration can be interru
65.
by mononcqc 9y ago
Starting with OTP-20, the string module handles unicode, both for binaries and lists (and iolists, which mixes all styles) without a problem.
66.
by mononcqc 9y ago
You could also just reduce driving deaths by having better public transportation and reducing driving overall. Sounds like it would even be better in the long run.
67.
by mononcqc 9y ago
I've since written a fairly complete blog post only on overload management of asynchronous systems at https://ferd.ca/handling-overload.html -- it hasn't made it in the book, though.
68.
by mononcqc 9y ago
I have not read any Rails book ever and they could therefore not be the inspiration for this one :) The true rationale behind the book was to give a better tool to train new coworkers that could help us operate the Erlang routing and loggin
69.
by mononcqc 9y ago
I've tried to explain how I tend to come up with properties in my own proptests in http://propertesting.com/book_what_is_a_property.html -- this could prove useful as well.
70.
by mononcqc 9y ago
It depends. One of the places where property-based testing buys you the most benefit is when testing systems that are conceptually simple, but use a complex implementation. In doing so, you tend to have clearly defined properties that are f
71.
by mononcqc 9y ago
This is, incidentally, one of the oldest arguments Erlang proponents had about the positives of Erlang's generally unfamiliar syntax: it is different because you should approach it differently, and it helps the programmer do a full con
72.
by mononcqc 9y ago
It should still be pretty slow compared to just doing the neural net propagation as matrix operations
73.
by mononcqc 9y ago
you're talking about undoing an architecture that lifts the benefits of an entire platform having done the work for you, in order to pick one that is probably easier to migrate to in the future. You prefer doing all the work mostly fro
74.
by mononcqc 9y ago
You're acting like the distribution and serialization formats of Erlang are not open or documented. If you're going for your C++ layer, try https://github.com/saleyn/eixx for example.
75.
by mononcqc 9y ago
The trick is more commonly used when writing to sockets. A socket owner is required for reading, not for writing. The trick then is that when you need to write lots of data to a socket to just send a copy of it to the writer so they can dum
76.
by mononcqc 9y ago
Aside from macros, pretty much all of these have been covered by build tools for a few years now.
77.
by mononcqc 9y ago
The true evil approach is to send the socket around, not the message, so that there is no copying required no matter what ;)
78.
by mononcqc 9y ago
I have never seen a language or framework used at a large scale that did not require digging, understanding, and tweaking of the underlying machinery for its specific use case. The true failure of the platform happens when you cannot do the
79.
by mononcqc 9y ago
https://github.com/happi/theBeamBook for the VM http://erlang-in-anger.com/ for introspecting it in production
80.
by mononcqc 9y ago
Bit of history on the feature. The hack was an old thing I had written at a hackathon over half a decade ago. It had little cost to regulars who had installed it at least once before. It relied on DETS and had transient issues with corrupti
81.
by mononcqc 9y ago
Yes. For such cases, you'll want to instead use a C-Node or a Port program to interface with the C code.
82.
by mononcqc 10y ago
Wondering if using erlang:halt() rather than init:stop(0) would be better since halt(0) shuts down the VM instantly while init:stop(0) takes time to take down the entire supervision trees in the VM in proper order.
83.
by mononcqc 10y ago
Moose or Elks don't 'bounce over the top' on a small vehicle. They crush it, rip the roof off, or go through it. It may depend on antlers, angles, speed, and so on. I've tried to pick the least graphic images possible:
84.
by mononcqc 10y ago
I think it's probably more of a consequence of the long long discussions that were had at https://github.com/erlang/otp/pull/960 -- with 15 participants from the OTP team, regular Erlangers, and I'm
85.
by mononcqc 11y ago
That's the thing though. Errors can be data in plenty of other languages. It's just that it's not the only tool you're given, and there's other things you can do without having to reimplement it all from scratch eve
86.
by mononcqc 11y ago
"Passing up the stack" is fairly minimalistic in an environment where you could be running thousands of goroutines, some (many?) of which may share memory. If you do it that way, you seem to forego a lot of error encapsulation str
87.
by mononcqc 11y ago
The general principles for fault tolerance require Separation of Concerns vis. Error Encapsulation (make sure that the contagion doesn't spread), Fault Detection (make sure that you know that someone is infected), and Fault Identificat
88.
by mononcqc 11y ago
You may want to use the procket library: https://github.com/msantos/procket/
89.
by mononcqc 11y ago
No. The conference organizers didn't have the time to set a recording setup up. Maybe if I end up giving the talk again somewhere there could be a recording.
90.
by mononcqc 11y ago
That's because I changed the image :)

More ›