Thanks for all of the feedback, everyone. I wanted to offer a few brief comments related to some of the things said in this thread so far.
I use the web console in addition to Stardog Studio because I enjoy navigating the entities though the links, which is a functionality not available in Studio.
I'm happy to say, in response to this, that Stardog Studio will be getting search functionality very soon. The initial release of the functionality will include the ability to search a specified database (as in the web console), view results in a table, and visualize sub-graphs for entities in the results. The visualization will show connections to nearby nodes and also associated data properties. This isn't quite the same "browser" experience as that in the web console, but it provides much of the same information. Adding additional browsability is something that's in the Studio pipeline.
I use the web console because not all database creation properties are reflected in Stardog Studio. For instance, I just came across this when working with it tonight: SameAs reasoning settings are not available in Stardog Studio when creating a database using Stardog Studio.
This should be resolved in our next Studio release!
Being a Government department we are required to have all software "whitelisted" and "packaged" (ie made installable and useable in our environment) before it can be used and managed by our Software Management tools. We cannot install software ourselves.
This process can take up to 6 weeks depending on the complexity of the software.
Stardog Studio consists of a large number of DLLs each of which will require individual whitelisting.
#1 Studio doesn't work on Centos 7.
We intend to address each of these concerns by providing Studio as a dockerized web application in the near future. Providing Studio in a docker container means that it will run on CentOS 7 (and other currently unsupported OSes) and also that it won't require installation on individual machines. Since the dockerized version of Studio will be a web application, it can also be run either on the local machine (without installation on the local system) or on a different machine that is accessible from elsewhere via the browser. This should, we hope, address the remaining concerns in this thread. We'd love to hear any feedback from you all concerning this.
Thanks again for all of the feedback! We take it seriously and we aim to use it to make Studio a joy to work with for all users.