>> Good software doesn’t force users to learn how it works. It hides the inner workings under the interface, so that people never even have to worry about it at all.
I agree - AND the fact is that the amount of effort involved in expressing (In a really well-made UI) every possible permutation of every command line option of a really complex tool like SOLR is tremendously high and unlikely to ever get done unless sponsored by a corporation. While it's true that the ideal would be UI that makes it all easier (and such UI is theoretically possible) it rarely gets built because of the cost involved. There can be tremendous complexity in expressing that many moving parts successfully... My .02 worth anyway... On Sat, Sep 17, 2016 at 1:52 PM, Bram Van Dam <bram.van...@intix.eu> wrote: > > I would like to see a future where the admin UI is more than just an > > addon ... but even then, I think the HTTP API will *still* be the most > > important piece of the system. > > In 4 years of heavily using (many instances and many versions of) Solr, > the only times when I've used the admin UI has been as a > debugging/diagnostics tool. For instance to quickly check memory usage > or to verify data has been loaded. > > My (and by extension my employer's and our customers') Solr usage > probably isn't typical, but I can't imagine anyone relying on the admin > UI for day-to-day Solr operations. > > >> Good software doesn’t force users to learn how it works. It hides the > inner workings under the interface, so that people never even have to > worry about it at all. > > Administering a system you know nothing about is a recipe for disaster. > This is just as true for WordPress, MySQL or Oracle as it is for Solr. > I'm not saying things can't/shouldn't be as easy and clear as possible. > But some effort to understand the system should be expected by the > sysadmin/operator. > > - Bram > >
