One of these is an organization the other is a project. Still the name clash is not ideal. Honestly, we’ve tried forever to come up with a different name for JuliaDB, but nothing else has stuck, so in the interest of getting it out there, we decided to just go with the working name that we’ve been using internally. There are three options:
- Both the org and the project can use the name “JuliaDB” and they can be disambiguated contextually.
- The org could be renamed to “JuliaDatabases”, which is arguably a more apt name.
- The project could be renamed to something else – we’re open to suggestions.
An aspect of understanding JuliaDB is that, compared to traditional SQL databases, which are all about transactional storage, JuliaDB is more about persistent computation and bringing code to data efficiently and seamlessly – including being able to store any kind of Julia data without fuss. So the “Julia” part in the name can be thought of as putting a strong emphasis on code.