- Capture some of the benefit of NodeConf, JSConf or RealTimeConf on a sustainable, regular basis.
- Get enough of a quorum of Bay Area Node.js leadership involved to appeal to other people to attend and get involved themselves. This includes not just visible leadership, but valuable less-visible contributors like jlord, Dave Pacheco, Emily Tanaka-Delgado, and Daniel Erickson.
- Provide an in-person forum to work through Node issues and improve and broaden the community.
- Foster broader leadership by getting more people more involved.
- Spread the organizational load among a wider crew of people so no one individual gets burnt out, more people get experience with running events, and we all are able to have fun.
- If there is to be a bias when making speaker selections, have it be towards bringing in new speakers and creating a safe space for speakers to present new material.
- Keep it fast-moving, entertaining, and concise -- have 2-hour (tops) meetups and then allow people to do social s
| # npm publish with goodies | |
| # prerequisite: `npm install -g trash` | |
| # `np` with an optional argument `patch`/`minor`/`major`/`<version>` | |
| # defaults to `patch` | |
| np() { | |
| trash node_modules &>/dev/null; | |
| git pull --rebase && | |
| npm install && | |
| npm test && | |
| npm version ${1:-patch} && |
| # Elixir has pipes `|>`. Let's try to implement those in Ruby. | |
| # | |
| # I want to write this: | |
| # | |
| # email.body | RemoveSignature | HighlightMentions | :html_safe | |
| # | |
| # instead of: | |
| # | |
| # HighlightMentions.call(RemoveSignature.call(email.body)).html_safe | |
| # |
- end-of-stream - specify a callback to be called when a stream ends (which is surpsingly hard to get right)
- duplexify - compose a Duplex stream from a Readable and a Writable stream
- pump - pipe streams together and close all of them if one of them closes
- pumpify - combine an array of streams into a single duplex stream using pump and duplexify
- through2 - tools for making Transform streams
- from2 - tools for making Readable streams
@mafintosh asks: "Does anyone have a good code example of when to use setImmediate instead of nextTick?"
https://twitter.com/mafintosh/status/624590818125352960
The answer is "generally anywhere outside of core".
process.nextTick is barely asynchronous. Flow-wise it is asynchronous, but it will trigger before any other asynchronous events can (timers, io, etc.) and thus can starve the event loop.
In this script I show a starved event loop where I just synchronously block, use nextTick and setImmediate
[ Update 2025-03-24: Commenting is disabled permanently. Previous comments are archived at web.archive.org. ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
(This isn't specific to Wireshark)
sudo vi /etc/pam.d/sudo
Add to the end BEGINNING of the file:
auth sufficient pam_tid.so
Test with a trivial sudo command, and you should get a TouchID prompt:
| light: | |
| - platform: esp32_rmt_led_strip | |
| name: Status LED | |
| pin: GPIO8 | |
| rgb_order: RGB | |
| num_leds: 1 | |
| rmt_channel: 0 | |
| chipset: ws2812 | |
| entity_category: config |