- (00:00:00) Part 1:
- (00:34:27) Part 2:
- (00:59:14) Part 3: 👩🏼💻 Netlify Dev
- (01:21:29) Part 4:
- (01:52:33) Part 5:
- (02:31:19) Part 6:
- Event name: Svelte Society First Meetup
- Description: The first Svelte meetup in NYC
- Start date: Oct 1
- End date: Oct 1
- Start time: 6.30pm
- End time: 9pm
- Organizer name: Shawn Wang & Rich Harris
- Estimated number of attendees: 30
- Event URL (if one exists): https://www.meetup.com/Svelte-Society/events/zwkkjryznbcb/
- Registration URL (if one exists): https://www.meetup.com/Svelte-Society/events/zwkkjryznbcb/
- decent representaiton here across paypal, twilio, apollo, stripe, intuit, adobe/cordova, and thats just the people ive met so far. and ofcourse salesforce, heroku, and netlify
- jeff dickey (oclif creator) leaving heroku. not sure what hes doing next
- salesforce cli has 16k total unique users, ~2k daily active. 90 community plugins
- twilio is launching a big oclif initiative at Signal Conf in a few weeks
- paypal working on something big too, a few devs here
- salesforce/heroku have 10 people fulltime and 70ish domain expert contributors on CLI. a lot more community plugin contributors
an adaptive, intent based CLI "state machine"
one realization from working on Netlify's CLI is that the CLI framework we used, oclif, didn't provide a great user experience out of the box.
Emphasis on great: it does a lot of nice things, like offering flag and argument parsing, help documentation, and pluggability. That's good for the CLI developer. But what about the CLI user?
- Idiomatic oclif code often checks for required preconditions, and if it doesn't exist, it prints a warning and then
- Decent code prints a helpful warning telling the user what they got wrong. It is informative.
- Better code offers a prompt, creates a file, or something similar to solve the precondition before proceeding. (possibly recursively). It is intent-based.
- Great code remembers past inputs to prompts and uses that to offer useful defaults. It is adaptive.