-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add quicli post #14
Add quicli post #14
Conversation
Thanks so much for offering to review this, @jamesmunns! :) |
@mgattozzi pong! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
A few grammar/spelling comments, but other than that thanks for sharing!
_posts/2018-01-30-quicli.md
Outdated
[#19]: https://github.com/killercup/quicli/issues/19 | ||
|
||
That sounded pretty awesome and made me really proud: | ||
Did me library |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Did me/Did my
_posts/2018-01-30-quicli.md
Outdated
|
||
But, before blindly agreeing to this, | ||
I needed to take a step back | ||
and evaluate what I want quicli to be. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
want => wanted (consistent past tense)
_posts/2018-01-30-quicli.md
Outdated
I just wanted a small framework-like thing | ||
that made writing CLI apps less of a pain. | ||
But how exactly do I want to to this? | ||
Thanks to Garretts' questions and comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Garrett's
_posts/2018-01-30-quicli.md
Outdated
|
||
In its implementation, | ||
you get what I'd call | ||
"a small framework around you main function": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
your main
_posts/2018-01-30-quicli.md
Outdated
In its implementation, | ||
you get what I'd call | ||
"a small framework around you main function": | ||
quicly's `main!` macro set up some basic things, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quicli
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is embarrassing
_posts/2018-01-30-quicli.md
Outdated
Sadly, for newcomers/forgetful people/drunk programmers/etc. | ||
they are also _wonderfully complex._ | ||
|
||
So, instead of offering the user "everything," |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"everything",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I went with the American style here, as I'm also using American spelling everywhere (I think)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are. What @jamesmunns put is how I always spell everything. I really don't see it split up often but both are valid!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You know what: You're both right and I actually like the ",
version more because it makes way more sense when parsing a sentence. It's just that I really like typography and the hanging quotes look so pretty. Oh well, I'm rendering everything in shitty monospace markdown style anyway :)
_posts/2018-01-30-quicli.md
Outdated
So, instead of offering the user "everything," | ||
I want to introduce some abstractions that are simple to use, | ||
and have simple but useful examples. | ||
Not not get stuck, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"not to get stuck"
_posts/2018-01-30-quicli.md
Outdated
Since then, I've written two more guides, | ||
and for both I added features to the framework, | ||
exposed new functionality, | ||
and thought more about how I want quicly-based code to feel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quicly => quicli
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is sooo embarrassing
_posts/2018-01-30-quicli.md
Outdated
and for both I added features to the framework, | ||
exposed new functionality, | ||
and thought more about how I want quicly-based code to feel. | ||
(More on the aspect of hosting and testing these docs in a future post!) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
post)!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole sentence is in parentheses
_posts/2018-01-30-quicli.md
Outdated
It gives you a way of quickly writing CLI programs in Rust. | ||
(Hence the name.) | ||
In this post, | ||
I want to present the ideas and underlaying philosophies of this project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
underlying
found by @jamesmunns --Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much! Pushed an update that addressed everything I didn't explicitly comment on :)
_posts/2018-01-30-quicli.md
Outdated
In its implementation, | ||
you get what I'd call | ||
"a small framework around you main function": | ||
quicly's `main!` macro set up some basic things, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is embarrassing
(as well as my ergonomic requirements). | ||
|
||
What I want you to end up with is code that is | ||
concise, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well-structured and boilerplate-free and part of the same point! See below
_posts/2018-01-30-quicli.md
Outdated
Sadly, for newcomers/forgetful people/drunk programmers/etc. | ||
they are also _wonderfully complex._ | ||
|
||
So, instead of offering the user "everything," |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I went with the American style here, as I'm also using American spelling everywhere (I think)
_posts/2018-01-30-quicli.md
Outdated
Since then, I've written two more guides, | ||
and for both I added features to the framework, | ||
exposed new functionality, | ||
and thought more about how I want quicly-based code to feel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is sooo embarrassing
_posts/2018-01-30-quicli.md
Outdated
and for both I added features to the framework, | ||
exposed new functionality, | ||
and thought more about how I want quicly-based code to feel. | ||
(More on the aspect of hosting and testing these docs in a future post!) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole sentence is in parentheses
@skade pong! :) |
@killercup ping! :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not bad! Mostly some grammatical, formatting, and spelling nit picks :D
_posts/2018-01-30-quicli.md
Outdated
|
||
I've been writing CLI tools in Rust for a while now. | ||
It really surprised me how this language | ||
that works really well for system programming |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
system -> systems
_posts/2018-01-30-quicli.md
Outdated
["5 Tips for Writing Small CLI Tools in Rust"][cli-tips] | ||
at the end of August 2017 | ||
that you may have read, | ||
where I describes some of my take-aways from that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
describes -> describe
_posts/2018-01-30-quicli.md
Outdated
that you may have read, | ||
where I describes some of my take-aways from that | ||
in the form of short tips. | ||
I've got some great feedback to that post, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got -> I've gotten
to -> from
I didn't have the time or concentration | ||
to sit down and really do this. | ||
And here's the good news: | ||
For some reason[^9e-talk], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this link render funny?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes: It renders a footnote :)
_posts/2018-01-30-quicli.md
Outdated
|
||
[cli-tips]: {% post_url 2017-08-31-rust-cli-tips %} | ||
|
||
[^9e-talk]: Okay, I admit, I promised to give a talk about Rust, and I wanted to present some nice, clean example code. (Of course, in the end I didn't show quicli in the talk.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you've made these two separate sentences rather than an aside you can remove the ( and )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, the create-react-app setup tools famously has this feature
_posts/2018-01-30-quicli.md
Outdated
So, instead of offering the user "everything," | ||
I want to introduce some abstractions that are simple to use, | ||
and have simple but useful examples. | ||
Not to get stuck, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were you intending this to be part of the previous sentence? Otherwise I have no idea what you were trying to convey here with this sentence or what you mean by Not to get stuck
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Messed up the fix, should've been "To not get stuck"
Indeed, instead of adding any feature flags to this crate | ||
(that enable additional components to be loaded/exposed), | ||
I want to have a clear line | ||
where a user is supposed to stop relying on quicli. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeeeeah
(that enable additional components to be loaded/exposed), | ||
I want to have a clear line | ||
where a user is supposed to stop relying on quicli. | ||
I'd rather have an "eject" option |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
react-cli (I think) does this and it's nice.
but another important aspect to me is to prove that it is useful | ||
for writing small tools | ||
-- even if you've only just started with Rust. | ||
This is why I initially wrote the Readme file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Readme -> README
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but but… my file is Readme.md
:O
_posts/2018-01-30-quicli.md
Outdated
for writing small tools | ||
-- even if you've only just started with Rust. | ||
This is why I initially wrote the Readme file | ||
in form of a How To: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in -> in the
I say a few but there were like 34 there lol woops |
There is no such thing as too many nits! Thanks a lot, @mgattozzi, will
edit this tonight!
Michael Gattozzi <notifications@github.com> schrieb am Di. 30. Jan. 2018 um
02:55:
… I say a few but there were like 34 there lol woops
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOX3MrRd0N9O2JKzN1qHW_Z3OkpX51ks5tPnaBgaJpZM4RxRlg>
.
|
I like it. I'd reread the introduction and see if you could make it a little shorter. I haven't quite gotten out of it if you will merge stdcli and quicli now? |
As suggested by @mgattozzi --Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed a bunch of comments :)
_posts/2018-01-30-quicli.md
Outdated
Sadly, for newcomers/forgetful people/drunk programmers/etc. | ||
they are also _wonderfully complex._ | ||
|
||
So, instead of offering the user "everything," |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You know what: You're both right and I actually like the ",
version more because it makes way more sense when parsing a sentence. It's just that I really like typography and the hanging quotes look so pretty. Oh well, I'm rendering everything in shitty monospace markdown style anyway :)
I didn't have the time or concentration | ||
to sit down and really do this. | ||
And here's the good news: | ||
For some reason[^9e-talk], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes: It renders a footnote :)
_posts/2018-01-30-quicli.md
Outdated
it is very concise. | ||
|
||
Another aspect of conciseness: | ||
Instead of using `.unwrap` to deal with errors, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I actually added the dot to note that it is a method and not a free function. But you're right, they're all the same :)
_posts/2018-01-30-quicli.md
Outdated
and good error messages. | ||
Similarly, you get logging for free, | ||
and if you add two more lines, | ||
you also get a `--verbose`/`-v` CLI argument to control the log level |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I <3 consistency and will go with 'flag'
_posts/2018-01-30-quicli.md
Outdated
So, instead of offering the user "everything," | ||
I want to introduce some abstractions that are simple to use, | ||
and have simple but useful examples. | ||
Not to get stuck, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Messed up the fix, should've been "To not get stuck"
_posts/2018-01-30-quicli.md
Outdated
|
||
[cli-tips]: {% post_url 2017-08-31-rust-cli-tips %} | ||
|
||
[^9e-talk]: Okay, I admit, I promised to give a talk about Rust, and I wanted to present some nice, clean example code. (Of course, in the end I didn't show quicli in the talk.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, the create-react-app setup tools famously has this feature
but another important aspect to me is to prove that it is useful | ||
for writing small tools | ||
-- even if you've only just started with Rust. | ||
This is why I initially wrote the Readme file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but but… my file is Readme.md
:O
Thank you three! The post is now live at https://deterministic.space/quicli.html :) |
No description provided.