Show HN: Fresh – A new terminal editor built in Rust https://ift.tt/VNQEOUd

Show HN: Fresh – A new terminal editor built in Rust I built Fresh to challenge the status quo that terminal editing must require a steep learning curve or endless configuration. My goal was to create a fast, resource-efficient TUI editor with the usability and features of a modern GUI editor (like a command palette, mouse support, and LSP integration). Core Philosophy: - Ease-of-Use: Fundamentally non-modal. Prioritizes standard keybindings and a minimal learning curve. - Efficiency: Uses a lazy-loading piece tree to avoid loading huge files into RAM - reads only what's needed for user interactions. Coded in Rust. - Extensibility: Uses TypeScript (via Deno) for plugins, making it accessible to a large developer base. The Performance Challenge: I focused on resource consumption and speed with large file support as a core feature. I did a quick benchmark loading a 2GB log file with ANSI color codes. Here is the comparison against other popular editors: - Fresh: Load Time: *~600ms* | Memory: *~36 MB* - Neovim: Load Time: ~6.5 seconds | Memory: ~2 GB - Emacs: Load Time: ~10 seconds | Memory: ~2 GB - VS Code: Load Time: ~20 seconds | Memory: OOM Killed (~4.3 GB available) (Only Fresh rendered the ansi colors.) Development process: I embraced Claude Code and made an effort to get good mileage out of it. I gave it strong specific directions, especially in architecture / code structure / UX-sensitive areas. It required constant supervision and re-alignment, especially in the performance critical areas. Added very extensive tests (compared to my normal standards) to keep it aligned as the code grows. Especially, focused on end-to-end testing where I could easily enforce a specific behavior or user flow. Fresh is an open-source project (GPL-2) seeking early adopters. You're welcome to send feedback, feature requests, and bug reports. Website: https://sinelaw.github.io/fresh/ GitHub Repository: https://ift.tt/bPTOVDn https://sinelaw.github.io/fresh/ December 3, 2025 at 08:15PM

Show HN: Golang Client Library for Gradium.ai TTS/STT API https://ift.tt/1TUN8KV

Show HN: Golang Client Library for Gradium.ai TTS/STT API https://ift.tt/OqyYwPE December 3, 2025 at 01:22AM

Show HN: Meeting Detection – a small Rust engine that detects meetings on macOS https://ift.tt/fcPaqps

Show HN: Meeting Detection – a small Rust engine that detects meetings on macOS I built a small open-source meeting detection engine for macOS. The goal is to provide a simple and accurate way for apps to know when a user is in a Zoom/Meet/Teams/Webex meeting. A lot of meeting recorders, productivity tools, and focus apps try to detect meetings, but the results are often unreliable. Some apps pop up “You’re in a meeting” suggestions even when nothing is happening. I wanted something that works consistently and is easy for developers to integrate. The engine is written in Rust and exposed to Node/Electron via napi-rs. It runs a lightweight background loop and uses two tiers: 1. Native app detection (Zoom, Teams, Webex) • process detection • meeting-related network activity 2. Browser meeting detection (Google Meet, Teams Web, Zoom Web, Webex Web) • reads browser tabs via AppleScript • validates meeting URL patterns • supports Chrome, Safari, and Edge It exposes a very simple JS API: init(); onMeetingStart((_, d) => console.log("Meeting started:", d.appName)); onMeetingEnd(() => console.log("Meeting ended")); console.log(isMeetingActive()); Would love feedback, especially from anyone building recorders, focus apps, calendar tools, etc. Windows + Linux support coming next. https://ift.tt/pe6JEQH December 3, 2025 at 01:47AM

Show HN: SMART report viewer – Simple tool to analyze smartctl outputs https://ift.tt/8BE0wsa

Show HN: SMART report viewer – Simple tool to analyze smartctl outputs https://ift.tt/28hA1yo December 3, 2025 at 12:29AM

Show HN: Valknut – static analysis to tame agent tech debt https://ift.tt/Uqdw8MO

Show HN: Valknut – static analysis to tame agent tech debt Hi y'all, In my work to reduce the amount of time I spend in the agentic development loop, I observed that code structure was one of the biggest determinants in agent task success. Ironically, agents aren't good at structuring code for their own consumption, so left to their own devices purely vibe-coded projects will tend towards dumpster fire status. Agents aren't great at refactoring out of the box either, so rather than resign myself to babysitting refactors to maintain agent performance, I wrote a tool to put agents on rails while refactoring. Another big problem I encountered trying to remove myself from the loop was knowing where to spend my time efficiently when I did dive into the codebase. To combat this I implemented a html report that simplifies identifying high level problem. In many cases you can click from an issue in the report directly to the code via VS Code links. I hope you find this tool as useful as I have, I'm working on it actively so I'm happy to field feature requests. https://ift.tt/bEGIDXB December 2, 2025 at 11:14PM

Show HN: RFC Hub https://ift.tt/4eh1yAI

Show HN: RFC Hub I've worked at several companies during the past two decades and I kept encountering the same issues with internal technical proposals: - Authors would change a spec after I started writing code - It's hard to find what proposals would benefit from my review - It's hard to find the right person to review my proposals - It's not always obvious if a proposal has reached consensus (e.g. buried comments) - I'm not notified if a proposal I approved is now ready to be worked on And that's just scratching the surface. The most popular solutions (like Notion or Google Drive + Docs) mostly lack semantics. For example it's easy as a human to see a table in a document with rows representing reviewers and a checkbox representing review acceptance but it's hard to formally extract meaning and prevent a document from "being published" when criteria isn't met. RFC Hub aims to solve these issues by building an easy to use interface around all the metadata associated with technical proposals instead of containing it textually within the document itself. The project is still under heavy development as I work on it most nights and weekends. The next big feature I'm planning is proposal templates and the ability to refer to documents as something other than RFCs (Request for Comments). E.g. a company might have a UIRFC for GUI work (User Interface RFCs), a DBADR (Database Architecture Decision Record), etc. And while there's a built-in notification system I'm still working on a Slack integration. Auth works by sending tokens via email but of course RFC Hub needs Google auth. Please let me know what you think! https://rfchub.app/ December 1, 2025 at 10:34PM

Show HN: An AI zettelkasten that extracts ideas from articles, videos, and PDFs https://ift.tt/dW9lc6h

Show HN: An AI zettelkasten that extracts ideas from articles, videos, and PDFs Hey HN! Over the weekend (leaning heavily on Opus 4.5) I wrote Jargon - an AI-managed zettelkasten that reads articles, papers, and YouTube videos, extracts the key ideas, and automatically links related concepts together. Demo video: https://youtu.be/W7ejMqZ6EUQ Repo: https://ift.tt/EW1J4sj You can paste an article, PDF link, or YouTube video to parse, or ask questions directly and it'll find its own content. Sources get summarized, broken into insight cards, and embedded for semantic search. Similar ideas automatically cluster together. Each insight can spawn research threads - questions that trigger web searches to pull in related content, which flows through the same pipeline. You can explore the graph of linked ideas directly, or ask questions and it'll RAG over your whole library plus fresh web results. Jargon uses Rails + Hotwire with Falcon for async processing, pgvector for embeddings, Exa for neural web search, crawl4ai as a fallback scraper, and pdftotext for academic papers. https://ift.tt/EW1J4sj December 1, 2025 at 11:50PM