Lessons learned from building an asynchronous filesystem component

Good talk! That's some difficult material you brought :D

The talk itself was good, could clearly understand and hear you and the pace was good.

I think the talk itself would benefit even more if you gave even more examples of what you were trying to show us. It would make the whole a lot clearer I believe.

The one thing I think I'd want to see from this talk is more! I think you could easily make this a much longer talk by diving deeper into the subject, giving more examples, etc. So definitely try to put more content in :)

Hope to see you speak again soon! :)

Interesting subject. I liked the talk but wanted to see more depth. You covered the problems, but didn't say as much as i would have liked about the solutions. A small nitpick: some of the text was hard to read due to the background images. Aside from that, please grow this talk and keep bringing it.

The talk itself was good. You gave some good examples and I really liked the pace and the confident style of presenting.

However, the talk was a bit on the short side. Right after the part about inodes I though "ok, now it's getting started, let's go", but then the talk was over. I understand with these kinds of talks it's hard to strike the balance between holding the hand of the audience and diving (too) deep. However itt's probably safe to eg. explain os x's flags (that you mentioned a bit more), or tell what makes a filesystem like zhs special, etc.

I'd love to see this at another user group (or conference) as a 50 minute talk, because you obviously know your stuff very well.

Your entire talk was a great introduction. Just when I thought you would get started, you ended. A WTF moment ;-)

A complete mismatch with what I expected. Was really hoping to learn more about ReactPHP/Filesystem and other related projects.

If you manage to do that and trim down the unix filesystem intro stuff, you got yourself a killer talk.