home.social

Search

1000 results for “cli_ar”

  1. OpenAI's Codex CLI architecture revealed: How the agent loop orchestrates autonomous software engineering through Responses API, prompt caching & stateless requests. Enterprise teams at Cisco & JetBrains now deploy this infrastructure. Analysis by #Adwait #OpenAI #Codex #AIEngineering #DeveloperTools #Tech #News #AI

    adwaitx.com/openai-codex-agent

  2. OpenAI's Codex CLI architecture revealed: How the agent loop orchestrates autonomous software engineering through Responses API, prompt caching & stateless requests. Enterprise teams at Cisco & JetBrains now deploy this infrastructure. Analysis by #Adwait #OpenAI #Codex #AIEngineering #DeveloperTools #Tech #News #AI

    adwaitx.com/openai-codex-agent

  3. OpenAI's Codex CLI architecture revealed: How the agent loop orchestrates autonomous software engineering through Responses API, prompt caching & stateless requests. Enterprise teams at Cisco & JetBrains now deploy this infrastructure. Analysis by #Adwait #OpenAI #Codex #AIEngineering #DeveloperTools #Tech #News #AI

    adwaitx.com/openai-codex-agent

  4. OpenAI's Codex CLI architecture revealed: How the agent loop orchestrates autonomous software engineering through Responses API, prompt caching & stateless requests. Enterprise teams at Cisco & JetBrains now deploy this infrastructure. Analysis by #Adwait #OpenAI #Codex #AIEngineering #DeveloperTools #Tech #News #AI

    adwaitx.com/openai-codex-agent

  5. OpenAI's Codex CLI architecture revealed: How the agent loop orchestrates autonomous software engineering through Responses API, prompt caching & stateless requests. Enterprise teams at Cisco & JetBrains now deploy this infrastructure. Analysis by #Adwait #OpenAI #Codex #AIEngineering #DeveloperTools #Tech #News #AI

    adwaitx.com/openai-codex-agent

  6. Recently @Schneems wrote a PR for a CLI argument to get machine-readable output from `bundle list`.

    github.com/rubygems/rubygems/p

    I liked it as an idea, and then about a day later I coincidentally had a use case where it'd come in handy. I hope it gets attention quickly - and merged, of course 😀

    #ruby #bundler

  7. I've tried multiple crates for parsing cli arguments, and I find them all very hard to use. More than once I've just done my own, missing all the features I wanted to get by using an available crate. Some things clearly does not work all that well for me when it comes to code reuse.

    #Programming #RustLang #Rust #CodeReuse #CliArgumentsParsing

  8. I've tried multiple crates for parsing cli arguments, and I find them all very hard to use. More than once I've just done my own, missing all the features I wanted to get by using an available crate. Some things clearly does not work all that well for me when it comes to code reuse.

    #Programming #RustLang #Rust #CodeReuse #CliArgumentsParsing

  9. 🎨 Old news: I added colour to argparse CLI help in last month's Python 3.14.

    ⭐ New news: I just added colour to ruff and ty's help so they can catch up (uv already had colour).

    #Python #CLI #argparse #ruff #ty #uv #colour

  10. 🎨 Old news: I added colour to argparse CLI help in last month's Python 3.14.

    ⭐ New news: I just added colour to ruff and ty's help so they can catch up (uv already had colour).

    #Python #CLI #argparse #ruff #ty #uv #colour

  11. 🎨 Old news: I added colour to argparse CLI help in last month's Python 3.14.

    ⭐ New news: I just added colour to ruff and ty's help so they can catch up (uv already had colour).

    #Python #CLI #argparse #ruff #ty #uv #colour

  12. 🎨 Old news: I added colour to argparse CLI help in last month's Python 3.14.

    ⭐ New news: I just added colour to ruff and ty's help so they can catch up (uv already had colour).

    #Python #CLI #argparse #ruff #ty #uv #colour

  13. 🎨 Old news: I added colour to argparse CLI help in last month's Python 3.14.

    ⭐ New news: I just added colour to ruff and ty's help so they can catch up (uv already had colour).

    #Python #CLI #argparse #ruff #ty #uv #colour

  14. Bash csh zsh ksh tksh fish are powerful CLI tools

    Entire networks can be controlled and build with them.

    Let's take for example command line tools to control media output

    For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to _fetch data that I never asked for$ and thus burn bandwidth

    The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.

    The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer

    Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
    We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm & twm and few others.
    The alsa audio interface was also just born.

    It is within this context that Andy envisioned alsaplayer. It should be modular just like Delitracker Amiga, it should be lightweight Delitracker runs on an Amiga A500 with just half A megabyte of chip ram
    That should still be memory left to do other the things so straight calls were made to widget libraries which explains the simplicity yet great usability of the UI. For as far as I remember Andy has also written an API for Alsaplayer

    Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.

    Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written

    One of the main reasons is that it has been coded by a command line programmer

    Alsaplayer has been ported to many different Operating System Architectures including freeBSD

    For me working on the command line has always been logical, graphic user interfaces were only used when absolutely necessary think about GEOS on the C64

    I started coding on the Casio FX 700p programmable calculator. I went so far to make program code that was in the book more efficient by crunching all the commands with two letter abbreviations.

    The power of the Command Line something the Young Ones should Learn

    Alsaplayer manpage

    https://man.freebsd.org/cgi/man.cgi?query=alsaplayer&sektion=1&apropos=0&manpath=FreeBSD+6.0-RELEASE+and+Ports

    #programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries #Amiga #RetroComputing

  15. If you’re using #Python’s #argparse module to parse CLI arguments and want to have `--foo` and `--no-foo` flags, check out `action=argparse.BooleanOptionalAction`, which automatically creates `--no-foo` for you: docs.python.org/3/library/argp

    parser.add_argument('--foo', action=argparse.BooleanOptionalAction)

    Requires 3.9 though. Simple solution for 3.8:

    parser.add_argument('--foo', action='store_true')
    parser.add_argument('--no-foo', dest='foo', action='store_false')
    parser.set_defaults(foo=True)

  16. Is there anything better than "Free Download Manager" these days (kinda dislike their GUI since they changed it from the v3.9.7 one)
    to get downloads from the browser automatically pushed into another tool that can do resumption and all (esp. when downloading multiple >20gb files/images).

    On the CLI aria2 + yt-dlp kinda works, but I haven't seen a browser plugin that would automatically intercept and forward downloads (esp. the javascript triggered ones).

    #aria2 #jdownloader #download #ytdlp

  17. Day 37 of learning Rust as a C# dev:
    Parsing CLI arguments with clap is clean, fast, and surprisingly fun.
    Add a little match, sprinkle in some ?, and boom, real logic.

    Here’s what I built:
    woodruff.dev/parsing-arguments

    #RustLang #CSharp #DotNet #LearnRust #RustForCSharpDevs

  18. Day 37 of learning Rust as a C# dev:
    Parsing CLI arguments with clap is clean, fast, and surprisingly fun.
    Add a little match, sprinkle in some ?, and boom, real logic.

    Here’s what I built:
    woodruff.dev/parsing-arguments

    #RustLang #CSharp #DotNet #LearnRust #RustForCSharpDevs

  19. Day 37 of learning Rust as a C# dev:
    Parsing CLI arguments with clap is clean, fast, and surprisingly fun.
    Add a little match, sprinkle in some ?, and boom, real logic.

    Here’s what I built:
    woodruff.dev/parsing-arguments

    #RustLang #CSharp #DotNet #LearnRust #RustForCSharpDevs

  20. Day 37 of learning Rust as a C# dev:
    Parsing CLI arguments with clap is clean, fast, and surprisingly fun.
    Add a little match, sprinkle in some ?, and boom, real logic.

    Here’s what I built:
    woodruff.dev/parsing-arguments

    #RustLang #CSharp #DotNet #LearnRust #RustForCSharpDevs

  21. Day 37 of learning Rust as a C# dev:
    Parsing CLI arguments with clap is clean, fast, and surprisingly fun.
    Add a little match, sprinkle in some ?, and boom, real logic.

    Here’s what I built:
    woodruff.dev/parsing-arguments

    #RustLang #CSharp #DotNet #LearnRust #RustForCSharpDevs

  22. There was a lack of a decent web based leaderboard so I wrote one in python and got up to speed on publishing to pypi properly. It's a nice minimal example of publishing a single python file to an installable command.

    github.com/westonal/archive-wa

    #archiveteam #archiveteamwarrior

  23. Topiary; Channel Your Inner Tweag

    Mixing it up a bit due to the chaos that is my new “normal”. Along with a mission (at the end), you also get a new resource to play with!

    Time to dig into today’s assignment.

    Type your email…

    Subscribe

    Topiary

    Photo by Yelena Odintsova on Pexels.com

    Topiary is a Rust-based universal source formatter that is a member of the Tree-sitter ecosystem and aims to be a uniform formatter for simple languages. It’s named after the art of shaping plants into pleasing forms, and just like its namesake (i.e., Topiary shapes your code into a more readable and aesthetically pleasing form).

    By leveraging Tree-sitter, Topiary can format code by understanding its syntax tree. This means it’s not just blindly applying text transformations; it deliberately reshapes code based on syntactic structure.

    You don’t even have to install it to use it! Try the online playground before polluting your pristine system with yet-another binary.

    Channeling Your Inner Tweag

    Photo by MART PRODUCTION on Pexels.com

    Back in Q3 of 2023, Tweag blogged about their revamping of the UX of the Topiary CLI. Yes, CLI tools 100% have UX concerns, and Topiary’s UX was as mundane and sub-par as many tools you likely use on the regular.

    In the article, they discuss the challenges and improvements. Some core issues prior to the revamp include:

    • Simplicity: Common tasks were difficult to perform due to the combinatorial explosion of flags, options, and modifiers.
    • Memorability: It was difficult to remember all the different options.
    • Discoverability: The CLI did not effectively guide users towards the full range of possible actions.
    • Familiarity: Users had to resort to guessing due to the lack of common idioms.
    • Clarity: The output was not always clear, making it difficult to understand the results.

    To address these issues, the following improvements were made:

    • Make illegal states un-representable: Using Rust’s type system and the clap library, the CLI was redesigned to forbid invalid input.
    • Separate modes of operation: Formatting and visualization were separated into distinct sub-commands, making the CLI more intuitive.
    • Make use of familiar idioms: The CLI was updated to follow common behaviors and idioms found in other CLI tools.
    • Make common tasks easy and unsurprising: The CLI was designed to make common tasks simple and predictable, while still allowing for customization.
    • Don’t paint yourself into a corner: The CLI was designed to be flexible and not limit future development or user expectations.

    These changes were implemented in Topiary v0.3.

    Please digest the linked article as they explain things quite well, especially when emphasizing the “why”.

    Your Mission

    Photo by Monstera Production on Pexels.com

    We’ve asked you to make some CLIs over these ~400 Drops, and you likely have your own, personal tools you maintain.

    Use the principles provided by Tweag — and many of the articles we’ve read on command-line completion, CLI argument parsing, and manual page building — to level-up at least one CLI tool of yours over the weekend. Your future self will look back fondly on this time well spent.

    Type your email…

    Subscribe

    FIN

    Remember, you can follow and interact with the full text of The Daily Drop’s free posts on Mastodon via @[email protected] ☮️

    https://dailydrop.hrbrmstr.dev/2024/01/12/drop-404-2024-01-12-weekend-project-edition/

    #cli #rust #topiary #tweag #ux

  24. Bash csh zsh ksh tksh fish are powerful

    Entire networks can be controlled and build with them.

    Let's take for example command line tools to control media output

    For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to fetch data that I never asked for and thus burn bandwidth

    The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.

    The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer

    Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
    We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm twm and few others.
    The alsa audio interface was also just Born.

    It is within this context that Andy envisioned alsaplayer. It should be modular just like delitracker Amiga, it should be lightweight daily tracker runs on an Amiga 500 with just half A megabyte of chip ram
    That should still be memory left to do other the things so straight calls were made to widget libraries.

    Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.

    Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written, one of the main reasons is that it has been coded by a command line programmer

    #programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries

  25. Bash csh zsh ksh tksh fish are powerful

    Entire networks can be controlled and build with them.

    Let's take for example command line tools to control media output

    For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to fetch data that I never asked for and thus burn bandwidth

    The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.

    The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer

    Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
    We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm twm and few others.
    The alsa audio interface was also just Born.

    It is within this context that Andy envisioned alsaplayer. It should be modular just like delitracker Amiga, it should be lightweight daily tracker runs on an Amiga 500 with just half A megabyte of chip ram
    That should still be memory left to do other the things so straight calls were made to widget libraries.

    Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.

    Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written, one of the main reasons is that it has been coded by a command line programmer

    #programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries