Calling Postel's Law the "Making matters worse" Law is very fitting. Also a wonderful example for why Programming and Engineering are two very different disciplines.
I hate steve jobs but this joke is out of bounds. If anybody laughs that he become hating himself. I think a very interesting psycoplogical thing going on there. I can see they hate themselves already for laughing the balmer joke. They are probably regreting for giving him courage to make the jobs joke by lauging the balmer joke.
For anyone else who wished there's better view of the slides, here is another version of this talk which displays he slides much more clearly: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE--4Yp3j_jk8Q.html
i report (startTime, eventCount, stopTime) rather than simply (timeDiff, eventCount). Because if you don't keep the actual stop time, then you don't see the overlaps (concurrency/queueing)
Nice remarks about functional languages and event processing. Really good talk overall. But I don't buy arguments defending JS usage here. Scala, Clojure, Erlang, Java 8 seems like so much better choice... And with Nashorn/Rhino it would be possible to make a JS interface for "Juniors". Although I doubt juniors know how to write functional code even in JS... Or maybe develop a DSL? And in general - should we use and create technology that we believe in or technology that is junior-friendly? I believe we should encourage juniors to learn more languages and show them how to become regulars instead of keeping them in JS-bubble. Also event sourcing is a more advanced concept that requires some experience anyway. If someone is designing CQRS with event sourcing or algorithms for detecting user profiles, learning a proper language should not be a problem.
I think all these stuff are almost 20 years old, someone gave it a market/trendy name to attract the uninitiated. Read: - POSA (www.amazon.com/Pattern-Oriented-Software-Architecture-Concurrent-Networked/dp/0471606952/ref=sr_1_1?ie=UTF8&qid=1479060184&sr=8-1&keywords=Pattern-Oriented+Software+Architecture+volume+2) - www.cs.wustl.edu/~schmidt/PDF/proactor.pdf
How to understand the "nodejs programmer should understand denotation semantic, that's crazy, that should be done by the compiler."? Is there something relative with the Communicating Sequential Processes? (Async in es7 ?)
Ah, updated 300000 rows async but after 50 rows the connectionpool gives no new free connections anymore. Normaly the update shall return void, but gives a exception now. You tell me the connectionpool must be functional-reactive too?!
He nails the problem with NodeJS, without even mentioning npm and the problems it adds. I like Node, but the whole ecosystem is volatile and deeply insecure (lol, leftpad, lol)
I'm not sure Erik correctly described iteratees when he said they were in a sense both observables and enumerables. He said they can send values back to the 'collection' but from my understanding these values are limited to either Cont, Done or Error states, where Cont is a function that accepts the next value from the collection, computes a step, producing one of the above three states again. Amiright?