3 ms·
> Just add a section at the top with basic examples and you halve my effort to start using them. That makes them better. Why is moving examples from the bottom
by hobarrera 11y ago
> Just add a section at the top with basic examples and you halve my effort to start using them. That makes them better.
Why is moving examples from the bottom to the top better?
> There's a huge class of people in the world who will never, ever touch a command line tool
So that's your argument in defence of a new command line tool? Oh, the irony.
Also, how many of those non-cli users actually know enough programming so as to write raw JavaScript on the cli?
- ajkjk 11y agoExamples at the top is better because experienced users who already know what the tool can do will find what they need regardless of where it's placed, but beginners need to have the barrier to entry lowered. It's not uncommon to open the document, not see what you need, and close it and go looking elsewhere. It's the same reason you put a useful description of your product on its landing page instead of nestled inside subdirectories. I guess I shouldn't have mentioned the people who never touch command-line tools. It's the people who almost-never do who are more convertible. Anyway, there's a marked difference between an easy way to run code on the command line, and a special-purpose tool with special-purpose syntax. Those non-advanced users are the ones who would benefit from having something with easily composable parts. (this is the same argument for building lots of small CLI tools and then composing them together, taken further?) I wager lots of amateur web developers can manage their way around basic JavaScript. It used to be people started coding with shell hacking so they were forced to learn the bizarre tool suite. Now they probably start with web development [citation needed].