You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There will be no Q/A (a.k.a: please hang out with the attendees at our awesome bar and hack with them on any questions that might come up)
You must use our presenters computer
There will be a presenter remote
Your slides must be 1440x1080px
I know that not using your own computer can be painful but I will go length to install everything under the sun to make you feel as comfortable on that machine as possible.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Simple streams are a modification to [min-streams][] that aren't quite as minimal, but should be much easier to use with only a slight change in definition. After using min-streams for a while, the biggest issue is the confusion between the data channel and the close channel. Also there is no structural type to tell consumers this is a stream. It's just a function with little introspection.
A simple-stream is defined as an object with .read(callback) and .stop(err, callback) functions. These are functions, not methods. This means that you don't have to worry about binding them to the stream object before calling them or using them as callbacks to other functions.
A nice side effect of this new design is that the read function is a continuable already. Libraries that consume generators like [gen-run][] can yield on read directly for easy stream consumption.
What does the ultimate database look like? Maybe the ultimate database of the future going to be a many-headed hydra that will attempt to solve all problems? Maybe marketing teams are going to be at the heart of its success? Perhaps it will grow tentacles and become violent toward its creator?
What does your current database do?
Unless you're a contributor to the software, your probably limited to understanding the value propositions and a subset of features. Maybe your an expert. Probably not. This corner is usually dark. A database has historically been a black box. You pick one that seems like the best fit and trust it.
Maybe the database of the future should just be a library, more like BerkeleyDB, I really don't want an entire server. Someone could just add a server on top of it if they really wanted one. It would also be nice if understanding it (in its entirety) wouldn't represent a big investment.
Object.getPropertyDescriptor and Object.getPropertyNames
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Node embracing async from the get-go means that servers are low-resource, high-concurrency by default.
Async + JavaScript = Perfect fit for an event loop.
When it comes to threads vs event-loop, there are times when either are advantageous.
But there are things very hard or impossible to do with threads.
WebSockets are difficult to do properly with threads. That's one example where non-blocking IO (async) has a major advantage.
RAM usage is another factor, especially when we're talking about the physical hardware required to run your application, which translates to real dollars.