Johnny.Decimal is a system for organizing digital files and folders using a hierarchical decimal system. It encourages users to define ten top-level areas of responsibility, each numbered 00-09, and then subdivide each area into ten more specific categories (00.00-00.09, 01.00-01.09, etc.), and so on, creating a logical and easily navigable structure. This system aims to combat "digital sprawl" by providing a clear framework for storing and retrieving files, ultimately improving focus and productivity. By assigning a decimal number to every project and area of responsibility, Johnny.Decimal makes it easier to find anything quickly and maintain a consistent organizational structure.
File Pilot is a new file manager focused on speed and a modern user experience. It boasts instant startup and file browsing, a dual-pane interface for efficient file operations, and extensive customization options like themes and keyboard shortcuts. Built with a robust architecture using Rust and Qt, File Pilot aims to provide a reliable and performant alternative to existing file explorers on Windows, macOS, and Linux. Key features include tabbed browsing, a built-in terminal, seamless file previews, and advanced filtering capabilities. File Pilot is currently available as a free technical preview.
HN commenters generally praised File Pilot's speed and clean interface, with several noting its responsiveness felt superior even to native file managers. Some appreciated specific features like the tabbed interface, customizable keyboard shortcuts, and the dual-pane view. A few users requested features like the ability to edit text files directly within the application and improved search functionality. Concerns were raised about the developer's choice to use Electron, citing potential performance overhead and resource consumption. There was also discussion around the lack of a Linux version and the developer's plans for future development and monetization. Some commenters expressed skepticism about the long-term viability of the project given its reliance on a single developer.
This blog post details how to automatically remove macOS-specific files (.DS_Store and ._*) from external drives upon ejection. The author uses a combination of AppleScript and a LaunchAgent to trigger a cleanup script whenever a volume is ejected. The script leverages dot_clean to efficiently delete these often-annoying hidden files, preventing their proliferation on non-macOS systems. This automated approach replaces the need for manual cleanup and ensures a cleaner experience when sharing drives between different operating systems.
Commenters on Hacker News largely appreciated the simplicity and directness of the provided AppleScript solution for removing macOS-specific files from external drives upon ejection. Some highlighted the potential for data loss if used carelessly, especially with networked drives or if the script were modified to delete different files. Others offered alternative solutions, including using dot_clean, incorporating the script into a Hazel rule, or employing a shell script with find. The discussion also touched upon the annoyance factor of these files on other operating systems and the historical reasons for their existence, with some suggesting that their prevalence has diminished. A few commenters mentioned more robust solutions for syncing and backing up, which would obviate the need for such a script altogether.
The blog post argues against using generic, top-level directories like .cache, .local, and .config for application caching and configuration in Unix-like systems. These directories quickly become cluttered, making it difficult to manage disk space, identify relevant files, and troubleshoot application issues. The author advocates for application developers to use XDG Base Directory Specification compliant paths within $HOME/.cache, $HOME/.local/share, and $HOME/.config, respectively, creating distinct subdirectories for each application. This structured approach improves organization, simplifies cleanup by application or user, and prevents naming conflicts. The lack of enforcement mechanisms for this specification and inconsistent adoption by applications are acknowledged as obstacles.
HN commenters largely agree that standardized cache directories are a good idea in principle but messy in practice. Several point out inconsistencies in how applications actually use $XDG_CACHE_HOME, leading to wasted space and difficulty managing caches. Some suggest tools like bcache could help, while others advocate for more granular control, like per-application cache directories or explicit opt-in/opt-out mechanisms. The lack of clear guidelines on cache eviction policies and the potential for sensitive data leakage are also highlighted as concerns. A few commenters mention that directories starting with a dot (.) are annoying for interactive shell users.
Helix editor's pull request #11285 integrates a file explorer directly into the editor. This new feature allows users to browse and open files within their project workspace without needing external tools. The implementation provides basic file management operations like creating, deleting, renaming, and opening files and directories, enhancing the editor's self-sufficiency and streamlining the editing workflow. It leverages the existing tree-sitter infrastructure for efficient parsing and rendering of the file tree.
Hacker News users generally expressed excitement about the merged file explorer in Helix, praising its speed and integration with the editor's core functionalities. Several commenters appreciated the thoughtful design, particularly the ability to open multiple files simultaneously and the minimalist, non-distracting implementation. Some users compared it favorably to other editors' file explorers, noting its superior performance and smoother workflow. A few commenters discussed potential improvements, like the ability to rename files directly within the explorer and support for fuzzy finding. Overall, the reception was positive, with many looking forward to using the new feature.
TMSU is a command-line tool that lets you tag files and directories, creating a virtual filesystem based on those tags. Instead of relying on a file's physical location, you can organize and access files through a flexible tag-based system. TMSU supports various commands for tagging, untagging, listing files by tag, and navigating the virtual filesystem. It offers features like autocompletion, regular expression matching for tags, and integration with find. This allows for powerful and dynamic file management based on user-defined criteria, bypassing the limitations of traditional directory structures.
Hacker News users generally praised TMSU for its speed, simplicity, and effectiveness, especially compared to more complex solutions. One commenter highlighted its efficiency for managing a large photo collection, appreciating the ability to tag files based on date and other criteria. Others found its clear documentation and intuitive use of find commands beneficial. Some expressed interest in similar terminal-based tagging solutions, mentioning TagSpaces as a cross-platform alternative and bemoaning the lack of a modern GUI for TMSU. A few users questioned the longevity of the project, given the last commit being two years prior, while others pointed out the stability of the software and the infrequency of needed updates for such a tool.
Summary of Comments ( 116 )
https://news.ycombinator.com/item?id=43128093
Hacker News users discussed Johnny.Decimal's potential benefits and drawbacks. Several praised its simplicity and effectiveness for personal file management, noting its improvement over purely chronological or alphabetical systems. Some found the 10-area/100-file limit too restrictive, preferring more granular or flexible approaches like tagging. Others questioned the system's long-term maintainability and scalability, especially for collaborative projects. The decimal system itself was both lauded for its logical structure and criticized for its perceived rigidity. A few commenters mentioned alternative organizational systems they found more effective, such as PARA and a Zettelkasten approach. Overall, the comments suggest Johnny.Decimal is a viable option for personal file organization but may not suit everyone's needs or work style.
The Hacker News post discussing Johnny.Decimal, a system for organizing digital files, has generated a substantial number of comments. Many users share their experiences with similar systems, offer alternative approaches, or discuss specific aspects of the Johnny.Decimal system.
Several commenters express appreciation for the system's simplicity and flexibility. One user highlights the benefit of assigning a decimal number to each area of responsibility, making it easy to locate files related to a specific project or task. Another commenter praises the system's focus on areas of responsibility rather than strict categorization, allowing for a more natural and personalized organization structure. The ability to adapt the system to individual needs is a recurring theme, with users describing how they've modified the system to fit their specific workflows.
A common point of discussion revolves around the granularity of the system. Some users find the 10-10-10 structure (10 areas, 10 categories within each area, and 10 files within each category) too restrictive, while others appreciate its enforced structure. Suggestions for alternative structures emerge, including using more or fewer levels or adapting the numbering system for larger projects. The use of symbolic links and tagging systems is also mentioned as a way to enhance the system's flexibility.
The discussion also touches on the challenges of maintaining such a system. Some commenters express concern about the overhead of assigning and remembering the decimal codes. Others highlight the importance of consistent use and periodic review to prevent the system from becoming unwieldy. The integration of the system with existing tools and workflows is also a topic of interest, with users sharing their experiences using Johnny.Decimal with various file managers and cloud storage services.
Several alternative systems are mentioned, including PARA (Projects, Areas, Resources, Archives), a similar system that focuses on different categories of information. The benefits and drawbacks of each system are discussed, with some users preferring the simplicity of Johnny.Decimal and others finding the PARA system more suited to their needs. The conversation also extends to the use of dedicated note-taking applications and the role of search functionality in managing digital files.
Overall, the comments reflect a general interest in personal organization systems and a willingness to experiment with different approaches. While many users express enthusiasm for Johnny.Decimal, the discussion also highlights the importance of finding a system that fits individual needs and workflows. The comments offer a valuable perspective on the practical considerations of implementing and maintaining such a system in a real-world setting.