is this stuff not pretty easy to do with python? ``` python -c "import base64; print(base64.b64encode('$INPUT_STRING'.encode('utf-8')).decode('utf-8'))" ```
Show HN: ut – Rust based CLI utilities for devs and IT
31–40 of 66 posts
Re: Show HN: ut – Rust based CLI utilities for devs and IT
#32Earlier quoted context omitted.
Amusingly, if you look historically, it's also a traditional approach to reduce total binary size - a bunch of small utilities were all Sim links to a single binary, which conditioned on argv[0] to figure out what to do.
In The Old Days, it was hard links, no symlinks.
Re: Show HN: ut – Rust based CLI utilities for devs and IT
#33I can understand why people would find `ut` convenient. That said, I would caution against trying to include too much functionality. What is too much? I don't have a clear idea on this yet. But I would probably argue that including HTTP functionality is going too far. Why? Because there are already amazing tools dedicated to this already. On the client side, see `xh` [1]. On the server side, see `miniserve` [2]. Both…
You can serve a folder of static assets like this:
http-nu :3021 '{|req| .static "www" $req.path}'
Re: Show HN: ut – Rust based CLI utilities for devs and IT
#34Re: Show HN: ut – Rust based CLI utilities for devs and IT
#35Re: Show HN: ut – Rust based CLI utilities for devs and IT
#36Very neat. Although philosophically I prefer the unix approach of "do one thing and do it well", I really admire this tool. I think it might be the fact that the one thing this does well is curating a set of functions for a particular profile of developer. My story is someone doing web focused full stack development? It might be worth doing a survey of your users to see what they use ut for and what areas you should…
I think for packaging it's okay to "have" lots of things that individually "do" one thing. The important part is that the user controls the entry points. It's more Unixy to allow someone to decode audio from one pipe to another than to only allow them to play a file to a speaker. Consider that Debian "does" lots of things because it has a kernel, hardware abstractions, a userland, a package manager, and often a GUI a…
Re: Show HN: ut – Rust based CLI utilities for devs and IT
#37Re: Show HN: ut – Rust based CLI utilities for devs and IT
#38Re: Show HN: ut – Rust based CLI utilities for devs and IT
#39I can understand why people would find `ut` convenient. That said, I would caution against trying to include too much functionality. What is too much? I don't have a clear idea on this yet. But I would probably argue that including HTTP functionality is going too far. Why? Because there are already amazing tools dedicated to this already. On the client side, see `xh` [1]. On the server side, see `miniserve` [2]. Both…
Re: Show HN: ut – Rust based CLI utilities for devs and IT
#401. Input must be valid UTF-8. 2. stdin is read to EOF instead of being read incrementally
Neither are ideal and can make ut unfit for a fair few use cases.