Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
72% Positive
Analyzed from 1076 words in the discussion.
Trending Topics
#file#vibe#manager#commander#don#coded#command#midnight#point#coding
Discussion Sentiment
Analyzed from 1076 words in the discussion.
Trending Topics
Discussion (36 Comments)Read Original on HackerNews
If you're shopping for a file manager, I recommend avoiding any project that incorporates a significant amount of LLM-generated code. Maybe in theory it could be reviewed as thoroughly as handwritten code; in practice that never happens.
I recently found that writing personal software through a coding agent is a fairly interesting endeavour. It's like I'm paying to get the software I need in the form of tokens.
> it's critical to know whether it's vibe coded
Strictly speaking, the only way to be sure that something is not vibe-coded is to either have a proof that the code were published before vibe-coding tools were available or to hand code it yourself.
Also, if you think that knowing if something is vibe-coded is so important, it is unwise to attack people who honestly tell you that something is vibe-coded.
The only problem for me is that it's not how I use a file manager. I learned to have two parallel windows when moving files, even before I learned how to use a terminal. That's why Midnight Commander was feeling so great. Until the day that I wanted to eliminate my usage of function keys and was tired of maintaining a config file. Some may say I "overkilled" it just to get rid of a config file..
Maybe it's a good file manager but, imo, authors completely failed to advertise it right.
Some aspects are still not completely ironed out, though. For example, today I discovered that there's no reliable exit hook and plugins have to override hotkeys and resort to various hacks. I had to patch a session saving extension so it kills mpv-based music preview plugin after yazi quits with "q". Kinda rough experience, but at least manageable with plugins in Lua.
Norton Commander.
Know and respect your elders.
Beyond the cost of tokens, I found it's very good at doing more with a limited context window before OpenCode hits context compaction.
Vibe coded or not, that's what puts me off from most nc/dn/mc reimplementations.
If you can't reach the command line by just typing the command, what's the point?
At least on this one you don't have to mouse click somewhere...
Command entering is just one if the "modes", and not necessarily the default one.
If shortcuts are limited to special keys and combos, this frees plane input for commands, but I personally prefer list filtering by default.
No TUI/GUI can do everything a unix command prompt can do, can they?
I don't know what your usage pattern is, but I keep mc open in a few terminals all the time, and just run commands in mc's shell when I need them. I suppose that if you only run the file manager when you need to manage files, your point of view makes sense.
I rarely do anything besides the basics (F5/F6) when managing files in MC, and for advanced stuff, like using rsync/rclone for moving files, I mostly use the usermenu.
I also hate to use function keys and having a menu bar in the TUI app. Therefore, I chose this design.
With OpenCode, I can finally make my own terminal file manager. I borrowed the main design concepts from Midnight Commander and some behavior from NVim-Tree file explorer.
I hope you would like it, at least I do. Since this project is entirely vibe-coded, so I'm not going to accept PR from the community, but feel free to open issues and fork it.