OlaProis

7 ms·

1.
Show HN: Dotfiles Coach CLI that analyzes your shell history with GitHub Copilot(github.com)
1 points by OlaProis 7mo ago|0 comments
2.
Show HN: Ironpad – Local-first project management with Git versioning(github.com)
1 points by OlaProis 7mo ago|0 comments
3.
Show HN: Beyond Open Source: Why AI-Assisted Projects Need 'Open Method'
1 points by OlaProis 8mo ago|0 comments
4.
by OlaProis 8mo ago
Done! I just published the full workflow documentation today: AI Development Workflow: Complete explanation of the process, handover system, how I manage context between sessions Historical PRDs: The actual Product Requirements Documents us
5.
by OlaProis 8mo ago
Actually, this is going on the v0.3.0 roadmap. I've been looking for ways to make the standalone mermaid-rs crate genuinely better than just 'mermaid.js but Rust.' The plan: use %% comments as layout hints. Something like: %%
6.
by OlaProis 8mo ago
You're right, neither Mermaid nor D2 really nail AWS architecture diagrams out of the box. Mermaid lacks icons entirely, and D2's AWS pack is more 'icons exist' than 'architecture patterns are easy.' Honestly,
7.
by OlaProis 8mo ago
Visual thinking use case makes sense! The challenge is Mermaid is declarative — layout is computed, not specified. Some options I'm considering: 1. layout hints/constraints in the syntax, 2. export to SVG then use a proper editor
8.
by OlaProis 8mo ago
the line is blurry for shure. Code generated by a closed-source compiler (or LSP) is still 'your' code. Maybe the difference is whether humans can reproduce and learn from the process? With traditional code, you can read commit hi
9.
by OlaProis 8mo ago
Great point about sharing the 'how' not just the 'what'. I'll consider adding prompt history or a development log showing the AI interactions, just have to figure out how to present all the data i guess. The commit
10.
by OlaProis 8mo ago
Thanks! TeX math support ($...$ and $$...$$) is planned for v0.4.0. We're going pure Rust (no JS runtimes), targeting common LaTeX syntax. See the planning doc on github (docs folder) for details.
11.
by OlaProis 8mo ago
Mobile is definitely a long-term goal, the lightweight binary and native performance would translate well. Your QR-code pairing idea is elegant for non-technical users. For sync, I've been thinking about: - Git-based sync for power use
12.
by OlaProis 8mo ago
Service flows for security audits — that's a specific and useful use case! A few thoughts: What might work today: - Sequence diagrams can model service-to-service flows (API calls, auth handoffs) - Flowcharts with subgraphs can represe
13.
by OlaProis 8mo ago
I tried to add it for this release but hit a wall with the font rendering dependencies (freetype, fontconfig). GUI apps need these for text display, and they don't play well with fully static musl linking - the build system wants a mus
14.
by OlaProis 8mo ago
You raise a fair point, and I've thought about this a bit since you mentioned it. What those files actually are: The files you noticed (AGENTS.md, GEMINI.md, CLAUDE.md, etc.) are auto-generated scaffolding from Task Master AI, a task m
15.
by OlaProis 8mo ago
Good idea! A musl build would solve the glibc compatibility issues Added to the v0.2.3 roadmap — will provide a statically-linked x86_64-unknown-linux-musl binary alongside the standard glibc one.
16.
by OlaProis 8mo ago
You've basically described Ferrite's design goals! Let me check the boxes: Single binary — ~15MB, point it at a directory with ferrite ./notes/ or open workspace via UI Fast launch, low latency — Native Rust/egui, i
17.
by OlaProis 8mo ago
The TODO list cursor behavior is exactly the kind of polish detail that matters. I'll add this to the issue tracker — cursor should respect line start position, not jump past the checkbox syntax. These "many small details" ar
18.
by OlaProis 8mo ago
Interesting use case! Mermaid doesn't have native AWS icons, but for v0.3.0's standalone crate, we could potentially support custom shapes/icons. D2 has better icon support if you need that now. What specific diagram types do
19.
by OlaProis 8mo ago
Yes, there's a person! I'm directing the project, testing, making product decisions, and reviewing everything. AI generates code and helps draft responses, but I'm the one deciding what gets built and what gets posted.
20.
by OlaProis 8mo ago
Good to know! Inline + display math is a more tractable scope. Typst or a Rust KaTeX port could handle that without needing full LaTeX. Added to the consideration list with that clarification.
21.
by OlaProis 8mo ago
You're right, currently Ferrite leans developer/tech with Mermaid, JSON/YAML tree viewer, and CLI integration. The Obsidian-style features (wikilinks, backlinks, knowledge graph) are coming in v0.3.0. Target audience is proba
22.
by OlaProis 8mo ago
Fair feedback! You're right — Ferrite isn't Obsidian-complete. Those are reasonable additions: - Left panel already exists (file tree + outline), but could use polish - Right panel (backlinks?) would come with v0.3.0 wikilinks wo
23.
by OlaProis 8mo ago
Thanks for the repro steps! This is helpful, formatting bar interaction shouldn't spin up the fan for such a small document. v0.2.2 has some performance improvements and is out, so it might be better, but this specific case might need
24.
by OlaProis 8mo ago
Good calibration! Yes, I disclosed this in another comment (and now in the README). The HN responses are AI-assisted: I describe what I want to say, Claude drafts it, I review and post. My English isn't great, so AI helps me communicat
25.
by OlaProis 8mo ago
Good question! A few reasons for egui over gtk-rs/iced/others: - Immediate mode — egui redraws every frame, which makes state management simpler (no callback hell). Great for prototyping. - Pure Rust, minimal deps — egui is self-c
26.
by OlaProis 8mo ago
v0.2.2 just released — addressing several issues raised in this thread: - CJK font support 1 — Korean/Chinese/Japanese characters now render properly - CLI improvements (#9, #10) — ferrite file.md now works, plus --version and --h
27.
by OlaProis 8mo ago
This is my only public Rust repo — I have some ongoing private projects in Rust, so I'm familiar with the ecosystem (cargo, crates, the borrow checker experience, etc.). That said, to be fully transparent: as I disclosed elsewhere in t
28.
by OlaProis 8mo ago
Fair point, and you're right. I should have disclosed this earlier. The HN responses are AI-assisted — I'm using Claude to help draft replies. Same workflow as the codebase: I describe what I want to say, AI drafts it, I review an
29.
by OlaProis 8mo ago
AsciiDoc and RST/Sphinx are definitely more powerful for structured documentation with cross-references, includes, and admonitions. For now Ferrite is focused on Markdown since that's the most common format for notes and quick doc
30.
by OlaProis 8mo ago
LaTeX support is a reasonable request! It's not on the immediate roadmap, but here's my thinking: Options considered: - KaTeX/MathJax-style rendering (would need a Rust math renderer or JS bridge) - Typst integration (Rust-

More ›