Skip to content

poorly maintained code,  #573

@JuanVargas

Description

@JuanVargas

I am struggling to understand the point of offering something so poorly maintained as MLJ.
I will try to be positive and offer constructive criticism.

There are so many issues that it has hard to figure where to start. But I will try:

  1. Documentation is missing, incorrect, outdated. There are several cases of links to non existing pages, such as https://alan-turing-institute.github.io/MLJ.jl/dev/loading_model_code/#Loading-Model-Code

  2. Code shown in the model browser pages often fails. For example, the package BetaML, which is shown in one of the tutorials, does not work.

  3. I use Go quite extensively, so I was hoping that Julia, also a modern language, would compare well to GO. Unfortunately that is not the case. When I compare the practice of development and testing in Go versus Julia, it is clear that testing in MLJ is not a primary consideration. There is "test" subdirectory under the MLJ, but the code is so incomplete....

  4. And then, there is the issue of debugging, which is not specific to MLJ, but, debugging in Julia is so slow that it is simply useless.

  5. I really was hoping to like Julia and use it for serious data science work. Unfortunately working in Julia is more of a pain than a joy, to the extent that I could not use it for the reasons already expressed, and I will recommend my colleagues to stay away.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions