A thread. The best thread.https://twitter.com/pczarkowski/status/986275843671457792 …
-
-
Replying to @southpolesteve
This is exactly why I live in imperative CLI land with serverless. Fast, simple. Root cause analysis is trivial.
1 reply 0 retweets 1 like -
Replying to @JoeEmison
I have so many unfinished ideas in this space. My ideal tool is able to execute a series of CLI commands. Or print them out so you can run them yourself...
1 reply 0 retweets 0 likes -
Replying to @southpolesteve
So I do exactly this using Perl instead of bash. Super easy to flip between execute mode and print mode, and (I know this is not often said) Perl is much more readable, especially when done properly. (This is really why Perl was made, to be a better scripting language)
2 replies 0 retweets 1 like -
Replying to @JoeEmison
Neat. Makes sense and matches what I know of perl. If I ever finish this tool it will be in JS. Perl is before my time (but I should prob learn)
1 reply 0 retweets 0 likes -
Replying to @southpolesteve
The challenge with JS is that it sucks for sequential CLI calls and processing output that might be formatted text (instead of JSON). Perl is quite similar to lots of languages...you may already know one of those?
1 reply 0 retweets 0 likes
All true. Heavy execSync usage and some text processing libs :) I still think bets on JS are still good ones even if not the right tool. The dev community is so massive.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.