Aria2 definitely needs a UI, and the one presented in the video checks the box of every feature I wish aria natively had, including activity tabs, easy addition/removal, and expandable status.
It's small, plain, and simple, and fits in very nicely with the idea of efficient minimalism that Aria exhudes.
I just wish it wasn't behind a webserver (a TUI would have been just as good), and the docker image seems like overkill for such a small app.
I appreciate the premise, aria is a powerful tool.
However I immediately have two concerns:
1. Why would the author use a screenshot obviously downloading copyrighted material instead of linux ISOs? It's either on purpose, which I support, or lack of foresight.
2. As much as I love the JVM, it feels like the wrong platform for this UI. It's a bit of command routing and server side simple html rendering. Go or something would do just fine. The name says tiny, but it ships a UI in a 100M+ docker container, for aria, a 5M cli tool.
If I was building it for myself, I would have no issue with the larger overhead, because I'm comfortable with the ecosystem, but for other people to run it's not a great trade off.
Edit: Sorry, I think this reads pretty one-sided in retrospect, feel free to disregard. I'm trying to be less negative.
Comments
I like it and hate it at the same time.
Aria2 definitely needs a UI, and the one presented in the video checks the box of every feature I wish aria natively had, including activity tabs, easy addition/removal, and expandable status.
It's small, plain, and simple, and fits in very nicely with the idea of efficient minimalism that Aria exhudes.
I just wish it wasn't behind a webserver (a TUI would have been just as good), and the docker image seems like overkill for such a small app.
Again, love it and hate it.
I appreciate the premise, aria is a powerful tool.
However I immediately have two concerns:
1. Why would the author use a screenshot obviously downloading copyrighted material instead of linux ISOs? It's either on purpose, which I support, or lack of foresight.
2. As much as I love the JVM, it feels like the wrong platform for this UI. It's a bit of command routing and server side simple html rendering. Go or something would do just fine. The name says tiny, but it ships a UI in a 100M+ docker container, for aria, a 5M cli tool.
If I was building it for myself, I would have no issue with the larger overhead, because I'm comfortable with the ecosystem, but for other people to run it's not a great trade off.
Edit: Sorry, I think this reads pretty one-sided in retrospect, feel free to disregard. I'm trying to be less negative.