I thought Mark was a good speaker and very comfortable in front of an audience. However, this talk was not about what I thought it was going to be about... it was a "pet project" talk, which I usually avoid. I also came out of it having very little idea how his database really works or what it's good for or bad for... seems like the main idea is that data is stored in JSON files which are downloaded to the client's machine, and then "queries" are written in JS... but this seems like it would be terrible for a lot of things.
I just felt disappointed, the first half of the presentation was promising a magical solution to all the typical DB pain points, but the solution didn't sound like anything I could use.
The first half was great, about what sets functional programming apart, good explanations and engaging. It felt like when it switched over to mapping (ha!) functional concepts to their counterparts in non-functional languages, the speaker lost his mojo. The [a] -> [b] whatever notation was not explained, and the examples were light.
Clever show. Great format and excellent points.
Great presentation. Helped filled in a lot of gaps that were missing in my understanding of node.
Great talk. Really helped my understanding of Node's event loop specifically, and did a great job addressing questions from the audience during the talk.
Would have been better if I could have seen the screen/examples. Was trying to follow along with the test instance, but I was quickly out paced and could never get caught back up.
Good examination of where OpenStack and particularly SUSE are going, but hardly a "dive" into it.
Good examination of the problem and solution to managing persistent data and why MongoDB was a good choice. Also an interesting application of Data::Dive, which was very cool. would have liked more depth.
I wanted to enjoy this talk, but it seemed to be more of an introduction to why we needed yet another BSD. The deep dive into sysctl was less a deep dive and more a walk through. I did not hear a compelling argument for hardenedbsd, but I will probably take a look at it.