Lunch will be provided! The goal of this meeting is to gather together and build a better, clearer definition of what error handling in Node entails and work toward a shared definition of what that should be for 1.0.
Omni San Francisco Hotel
500 California St
San Francisco, CA 94104
Russian Hill meeting room
- Dan Shaw (@dshaw)
- Rod Vagg (@rvagg)
- TJ Fontaine (@tjfontaine)
- Trevor Norris (@trevnorris)
- Forrest Norvell (@othiym23)
- Erik Toth (@totherik)
- Current state of Error Handling in Node
- Error-first callbacks
- EventEmitter errors
- Throw
- Handling errors
- in callbacks
- error listeners
- try/catch
- uncaughtException
- domains
- The future
- AsyncListener
- What do we do with domains?
- What else do we need for 1.0?
- Not included in this list, but probably should be
- Promises
- Have a good time and learn a lot.
- Have a better understanding of what the challenges users are facing and where we are falling short.
- Improved documentation about best practices.
- Improved training guidelines for Node and a consistent error handling story.
- Avoid creating another Domains.
- Make node v1.0.0 awesome!