Well i still pay for it for two reasons- no ads and music. I use YouTube music as the music service since it has more artista from my country as for example spotify. And ads free since I and my family love watching each specific videos and are subscribed to different creators. I could switch to Spotify for music but then getting all devices, mostly our tv with chrome cast a solid app that somehow blocks ads without any issues… I would do that. And what about the iOS devices? I don’t want alternative stores on my iOS infected devices just to get an alternative app running. Then again, I don’t want to have pihole being my single point of failure on the complete home network. But the pi hole thing is completely different story (and out if scope).

The double commander is gui only, right? Thanks for the info. 👍🏻

Thank you for your question. The first thing you will notice is the ui, which Rodeo, uses the two-pane l, where as Yazi is a directory/preview and file browsing popup. Yazi also uses most of external tools (zoxide, jq, fd etc) where as Rodeo uses a-lot of Rust crates to achieve the similar result. Rodeo doesn’t have that much external dependencies. At the end, it’s personal preference. I like the mc/nc setup more, that was the sole reason to develop it too. I hope I answered your question 👍🏻

Keep up the good work and thank you for contributing to FOSS!

I don’t really understand how your comment has anything to do with the application I’m writing. I appreciate any constructive criticism to the application - The issue you and chrash0 are describing is usually solved with proper linting and formatting tools included to any IDE of your choice. Thank you anyways for sharing your PoV on YAML :)

Thank you for your feedback.

The good old X vs Y. I think its a matter of use-case and personal preference. The decision to pick yaml is solely because readability, which is, above what toml has to offer with its single-dimension. On the other side, yes, yaml has its own quirks such as primitive boolean (yes, true, on) and whitespace sensitivity;

still, yaml is still preferred type when we’re talking devops.

I’ll put this on a nice to have list- I’m quite sure the toml OR yaml for that matter, has an option to convert one way or another :)

Update: I’ve added the issue to the project.

:D Not really, but the thing with stockholm syndrom maybe describes me quite well :D. However, if I’d have to decide to do a config file, I would always rather take yaml than json.