Jiri Stribny has released a free, online, and modern command-line handbook aimed at both beginners and experienced users. The handbook covers a wide range of topics from basic navigation and file manipulation to more advanced concepts like shell scripting, process management, and using the command line effectively with cloud services like AWS. It focuses on practical examples and aims to be a comprehensive resource, updated for the current computing landscape, including discussions of newer tools and best practices. The handbook encourages interactive learning through built-in exercises and code examples that readers can experiment with directly in their terminal.
The blog post laments the absence of a simple, built-in command-line tool in common Unix systems for sorting IPv6 addresses correctly. Standard sorting tools like sort treat IPv6 addresses as strings, leading to incorrect ordering. The author explores several workarounds, including converting addresses to a sortable format using expansion and zero-padding, leveraging specialized tools like ip6calc, or scripting solutions. Ultimately, the post highlights the surprising complexity of this seemingly straightforward task and calls for a more elegant, standardized solution within core Unix utilities.
HN commenters generally agree that sorting IPv6 addresses from the command line is tricky. Several suggest using sort -k, potentially with some preprocessing via awk or sed to isolate the relevant parts of the address for numerical sorting. Some note the complications introduced by mixed representations (e.g., compressed vs. expanded addresses) and the need to handle various formats like CIDR notation. One commenter highlights the difficulty of sorting IPv6 addresses lexicographically as opposed to numerically. Another commenter suggests a Python solution using the ipaddress module. Several commenters point out that the sort -V (version sort) option likely won't work correctly for IPv6 addresses, reinforcing the original poster's frustration.
Frustrated with the complexity and performance overhead of dynamic CMS platforms like WordPress, the author developed BSSG, a static site generator written entirely in Bash. Driven by a desire for simplicity, speed, and portability, they transitioned their website from WordPress to this custom solution. BSSG utilizes Pandoc for Markdown conversion and a templating system based on heredocs, offering a lightweight and efficient approach to website generation. The author emphasizes the benefits of this minimalist setup, highlighting improved site speed, reduced attack surface, and easier maintenance. While acknowledging potential limitations in features compared to full-fledged CMS platforms, they champion BSSG as a viable alternative for those prioritizing speed and simplicity.
HN commenters generally praised the author's simple, pragmatic approach to static site generation, finding it refreshing compared to more complex solutions. Several appreciated the focus on Bash scripting for its accessibility and ease of understanding. Some questioned the long-term maintainability and scalability of a Bash-based generator, suggesting alternatives like Python or Go for more complex sites. Others offered specific improvements, such as using rsync for deployment and incorporating a templating engine. A few pointed out potential vulnerabilities in the provided code examples, particularly regarding HTML escaping. The overall sentiment leaned towards appreciation for the author's ingenuity and the project's minimalist philosophy.
Pipelining, the ability to chain operations together sequentially, is lauded as an incredibly powerful and expressive programming feature. It simplifies complex transformations by breaking them down into smaller, manageable steps, improving readability and reducing the need for intermediate variables. The author emphasizes how pipelines, particularly when combined with functional programming concepts like pure functions and immutable data, lead to cleaner, more maintainable code. They highlight the efficiency gains, not just in writing but also in comprehension and debugging, as the flow of data becomes explicit and easy to follow. This clarity is especially beneficial when dealing with transformations involving asynchronous operations or error handling.
Hacker News users generally agree with the author's appreciation for pipelining, finding it elegant and efficient. Several commenters highlight its power for simplifying complex data transformations and improving code readability. Some discuss the benefits of using specific pipeline implementations like Clojure's threading macros or shell pipes. A few point out potential downsides, such as debugging complexity with deeply nested pipelines, and suggest moderation in their use. The merits of different pipeline styles (e.g., F#'s backwards pipe vs. Elixir's forward pipe) are also debated. Overall, the comments reinforce the idea that pipelining, when used judiciously, is a valuable tool for writing cleaner and more maintainable code.
This presentation provides a deep dive into advanced Bash scripting techniques. It covers crucial topics like regular expressions for pattern matching, utilizing built-in commands for string manipulation and file processing, and leveraging external utilities like sed and awk for more complex operations. The guide emphasizes practical scripting skills, demonstrating how to control program flow with loops and conditional statements, handle signals and traps for robust script behavior, and effectively manage variables and functions for modular and reusable code. It also delves into input/output redirection, process management, and here documents, equipping users to write powerful and efficient shell scripts for automating various system administration tasks.
HN commenters generally praise the linked Bash scripting guide for its clarity and comprehensiveness, especially regarding lesser-known features and best practices. Several highlight the sections on quoting and variable expansion as particularly valuable for avoiding common pitfalls. Some suggest the guide, while older, remains relevant for intermediate/advanced users looking to solidify their understanding. A few users mention alternative resources or offer minor critiques, such as the guide's lack of coverage on newer Bash features or the density of information, but the overall sentiment is positive, viewing the PDF as a valuable resource for improving Bash scripting skills. The mention of set -u (nounset) to catch undefined variables is brought up multiple times as a crucial takeaway.
Xan is a command-line tool designed for efficient manipulation of CSV and tabular data. It focuses on speed and simplicity, leveraging Rust's performance for tasks like searching, filtering, transforming, and aggregating. Xan aims to be a modern alternative to traditional tools like awk and sed, offering a more intuitive syntax specifically geared toward working with structured data in a terminal environment. Its features include column selection, filtering based on various criteria, data type conversion, statistical computations, and outputting in various formats, including JSON.
Hacker News users discuss XAN's potential, particularly its speed and ease of use for data manipulation tasks compared to traditional tools like awk and sed. Some express excitement about its CSV parsing capabilities and the ability to leverage Python's power. Concerns are raised regarding the dependency on Python, potential performance bottlenecks, and the limited feature set compared to more established data wrangling tools like Pandas. The discussion also touches upon the project's early stage of development, with some users interested in contributing and others suggesting potential improvements like better documentation and integration with other command-line tools. Several comments compare XAN favorably to other similar tools like jq and miller, emphasizing its niche in CSV manipulation.
This blog post demonstrates how to efficiently integrate Large Language Models (LLMs) into bash scripts for automating text-based tasks. It leverages the curl command to send prompts to LLMs via API, specifically using OpenAI's API as an example. The author provides practical examples of formatting prompts with variables and processing the JSON responses to extract desired text output. This allows for dynamic prompt generation and seamless integration of LLM-generated content into existing shell workflows, opening possibilities for tasks like code generation, text summarization, and automated report creation directly within a familiar scripting environment.
Hacker News users generally found the concept of using LLMs in bash scripts intriguing but impractical. Several commenters highlighted potential issues like rate limiting, cost, and the inherent unreliability of LLMs for tasks that demand precision. One compelling argument was that relying on an LLM for simple string manipulation or data extraction in bash is overkill when more robust and predictable tools like sed, awk, or jq already exist. The discussion also touched upon the security implications of sending potentially sensitive data to an external LLM API and the lack of reproducibility in scripts relying on probabilistic outputs. Some suggested alternative uses for LLMs within scripting, such as generating boilerplate code or documentation.
Christian Tietze reflects on the "software rake," a metaphor for accumulating small, seemingly insignificant tasks that eventually hinder progress on larger, more important work. He breaks down the rake's "prongs" into categories like maintenance, distractions, context switching, and unexpected issues. These prongs snatch time and attention, creating a sense of being busy but unproductive. Tietze advocates for consciously identifying and addressing these prongs through techniques like timeboxing, focused work sessions, and ruthless prioritization to clear the way for meaningful progress on significant projects.
Hacker News users discussed the various "prongs" of the Rake, agreeing with the author's general premise about complexity in software. Several commenters shared their own experiences wrestling with similar issues, particularly around build systems and dependency management. One pointed out the irony of Rake itself being a complex build system, while another suggested that embracing complexity is sometimes unavoidable, especially as projects mature. The impact of "worse is better" philosophy was debated, with some arguing it contributes to the problem and others suggesting it's a pragmatic necessity. A few users highlighted specific prongs they found particularly relevant, including the struggle to maintain compatibility and the pressure to adopt new technologies. Some offered alternative solutions, like focusing on smaller, composable tools and simpler languages, while others emphasized the importance of careful planning and design upfront to mitigate future complexity. There was also discussion about the role of organizational structure and communication in exacerbating these issues.
Paul Samuels advocates for using simple, project-specific shell scripts instead of complex build systems or task runners for small to medium-sized projects. He argues that shell scripts offer better transparency, debuggability, and control, while reducing cognitive overhead. They facilitate easier understanding of project dependencies and build processes, which ultimately contributes to better maintainability, especially for solo developers or small teams. By leveraging the shell's built-in features and readily available Unix tools, project scripts provide a lightweight yet powerful approach to managing common development tasks.
Hacker News users generally praised the simplicity and practicality of "Project Scripts." Several commenters appreciated the lightweight nature of the approach compared to more complex build systems or dedicated project management tools, highlighting the benefit of reduced cognitive overhead. Some suggested potential improvements like incorporating direnv or using a Makefile for more complex projects. A few users expressed skepticism, arguing that the proposed "Project Scripts" offered little beyond basic shell scripting and questioned the need for a dedicated term. Others found the idea valuable for its focus on explicitness and ease of sharing project setup within a team. The discussion also touched on related tools like Taskfile and justfile, comparing their features and complexity to the author's approach.
"Do-nothing scripting" advocates for a gradual approach to automation. Instead of immediately trying to fully automate a complex task, you start by writing a script that simply performs the steps manually, echoing each command to the screen. This allows you to document the process precisely and identify potential issues without the risk of automated errors. As you gain confidence, you incrementally replace the manual execution of each command within the script with its automated equivalent. This iterative process minimizes disruption, allows for easy rollback, and makes the transition to full automation smoother and more manageable.
Hacker News users generally praised the "do-nothing scripting" approach as a valuable tool for understanding existing processes before automating them. Several commenters highlighted the benefit of using this technique to gain stakeholder buy-in and build trust, particularly when dealing with complex or mission-critical systems. Some shared similar experiences or suggested alternative methods like using strace or dtrace. One commenter suggested incorporating progressive logging to further refine the script's insights over time, while another cautioned against over-reliance on this approach, advocating for a move towards true automation once sufficient understanding is gained. Some skepticism was expressed regarding the practicality for highly interactive processes. Overall, the commentary reflects strong support for the core idea as a practical step toward thoughtful and effective automation.
The GNU Make Standard Library (GMSL) offers a collection of reusable Makefile functions designed to simplify common build tasks and promote best practices in GNU Make projects. It provides functions for tasks like finding files, managing dependencies, working with directories, handling shell commands, and more. By incorporating GMSL, Makefiles can become more concise, readable, and maintainable, reducing boilerplate and improving consistency across projects. The library is designed to be modular, allowing users to include only the functions they need.
Hacker News users discussed the GNU Make Standard Library (GMSL), mostly focusing on its potential usefulness and questioning its necessity. Some commenters appreciated the idea of standardized functions for common Make tasks, finding it could improve readability and reduce boilerplate. Others argued that existing solutions like shell scripts or including Makefiles suffice, viewing GMSL as adding unnecessary complexity. The discussion also touched upon the discoverability of such a library and whether the chosen license (GPLv3) would limit its adoption. Some expressed concern about the potential for GPLv3 to "infect" projects using the library. Finally, a few users pointed out alternatives like using a higher-level build system or other scripting languages to replace Make entirely.
Werk is a new build tool designed for simplicity and speed, focusing on task automation and project management. Written in Rust, it uses a declarative TOML configuration file to define commands and dependencies, offering a straightforward alternative to more complex tools like Make, Ninja, or just shell scripts. Werk aims for minimal overhead and predictable behavior, featuring parallel execution, a human-readable configuration format, and built-in dependency management to ensure efficient builds. It's intended to be a versatile tool suitable for various tasks from simple build processes to more complex workflows.
HN users generally praised Werk's simplicity and speed, particularly for smaller projects. Several compared it favorably to tools like Taskfile, Just, and Make, highlighting its cleaner syntax and faster execution. Some expressed concerns about its reliance on Deno and potential lack of Windows support, though the creator clarified that Windows compatibility is planned. Others questioned the long-term viability of Deno itself. Despite some skepticism, the overall reception was positive, with many appreciating the "fresh take" on build tools and its potential as a lightweight alternative to more complex systems. A few users also offered suggestions for improvements, including better error handling and more comprehensive documentation.
Summary of Comments ( 16 )
https://news.ycombinator.com/item?id=44126612
HN commenters largely praised the Command Line Handbook for its modern approach, covering newer tools and techniques omitted from older resources. Several appreciated the inclusion of practical examples and the focus on interactive use. Some suggested additions, including coverage of specific tools like
jq,fzf, andripgrep, more detail on shell scripting, and explanations of underlying concepts like the filesystem hierarchy. A few pointed out minor typos or formatting inconsistencies. The overall sentiment was highly positive, with many expressing their intent to use the handbook themselves or recommend it to others.The Hacker News post "Show HN: I wrote a modern Command Line Handbook" at https://news.ycombinator.com/item?id=44126612 generated a moderate amount of discussion, with several commenters expressing appreciation for the resource and offering suggestions for improvement.
One of the most compelling comments highlighted the importance of focusing on the conceptual underpinnings of the command line, rather than just presenting a collection of commands. This commenter advocated for explaining concepts like standard input/output/error, pipes, and redirection early on, emphasizing that understanding these fundamental concepts is crucial for effectively utilizing the command line. They argued that mastering these principles allows users to extrapolate and combine commands creatively, rather than just memorizing individual commands.
Another user suggested incorporating information about shell scripting, particularly using Bash or Zsh. They believed that introducing basic scripting could significantly enhance the handbook's value by empowering users to automate tasks and create more powerful workflows.
Several commenters praised the handbook's clear and concise writing style, finding it accessible and easy to understand. The modern focus, including coverage of tools like
fd,ripgrep, andfzf, was also well-received.Some suggestions for improvement included adding more interactive elements, such as exercises or quizzes, to reinforce learning. Another commenter requested a section on common command-line utilities for tasks like managing archives, working with images, and performing system administration tasks.
One user expressed a desire for more platform-specific information, particularly for Windows users, recognizing that many command-line tools behave differently across operating systems. They pointed out the growing popularity of Windows Subsystem for Linux (WSL) and suggested including guidance on using it effectively.
Finally, a few comments pointed out minor typos and formatting issues, demonstrating the community's engagement with the project and their willingness to contribute to its improvement. Overall, the comments reflect a positive reception to the handbook and provide valuable feedback for its continued development.