On Wed, Jan 8, 2014 at 11:34 AM, <
hehehaha...@gmail.com> wrote:
> You can try downloading the driver yourself and following the instructions
> for building it. You will see that it fails to build. If you hack it so
> that it compiles, then you can't connect to the database because you get a
> run-time error that the command doesn't exist or the module can't be found
> or blah-blah. Then if you deal with that issue... (on and on...).
>
> Now I look and see that many people who are trying to fork or fix the code
> on github have issued pull requests and left comments that this needs to be
> fixed or that needs to be fixed (and some comments say the code no longer
> compiles) but the comments are months to years old and have still gone
> unresponded to.
>
> I guess I'm not surprised. This is what always happens to me when I work in
> Erlang. Erlang itself is great, considered in a vacuum. But once you leave
> the solace of anything that was shipped with it, it turns into a ghetto.
> Even products WRITTEN in Erlang will support every language on the planet
> BUT Erlang.
>
> I guess I would ask how ChicagoBoss is solving the issue... but I'm not sure
> I want to even try anymore. I don't think I want to rest a project's fate
> on a joke unmaintained driver.
>
> Thanks.
>
Sorry for my limited response. I should have specified from my end