4 ms·

No thank you. I appreciate the power, speed, simplicity and flexibility of UNIX/GNU style text tools. I-Also-Don't-Want-To-Be-Locked-Into-This-Ridiculous-Syntax

• shortrounddev 4y ago
  It's funny to me that people hate how verbose posh is when bash syntax looks like my cat walked over my keyboard
  • password4321 4y ago
    Thank goodness for tab completion! I appreciate that it auto-corrects capitalization and slash direction.
  • stinos 4y ago
    When I read I-Also-Don't-Want-To-Be-Locked-Into-This-Ridiculous-Syntax-Nightmare, bash and sed and cut and the likes indeed are the first things which come to mind. I really feel kind of bad sometimes for once having spent time learning them, only to later find out there are many alternatives and nearly all of them have a shorter learning curve. Many of these tools also have zero discoverability as well, meaning you effectively get locked into learning their syntax. And then another one for the next tool. Whereas at least in PS you can try to use common words and tab completion and sometimes get there before having to reach to 'how do I x in y'.
  • chongli 4y ago
    It's a matter of recognizing your use case. If you're going to write a program that you expect to maintain for years, sure, go ahead and make it as verbose as possible. Unix tools support this with long-form flags (usually prefixed with -- rather than -). On the other hand, if you're doing exploration and iterating interactively on the fly (which bash is best at) then you want very terse syntax to keep lines short.
• gabrielsroka 4y ago
  Here it is with aliases. `?` Means where: ipcsv example.csv | ? color -eq red color shape flag index ----- ----- ---- ----- red square 1 15 red circle 1 16 red square 0 48 red square 0 7