3

People always complain about node_modules, at least it works most of the time, unlike god-damn python AI packages. I can't install https://github.com/shashikg/... because for some inane reason it requires a LLVM wrapper that in turn wants to compile LLVM manually. Not just manually YOU, the filthy dev that wants to use this holy library, must go and compile it yourself. And don't you forget to apply the holy patches.

God the code in AI projects always sucks - last time I looked at voice gen it required me to figure out what the fuck it was doing and go hunt down the libraries manually and still have to vendor in half the library because they used a library that had a minor migration but was 2 major versions behind or similar issue.

Why do science bros write such shit code that always wants to reach into things completely unnecessarily. Just write your shit properly.

Is this why they always have docker image...

Comments
  • 1
    Huh... Last time I used Python packages it would download compilers and do the compile for me. It wasn't an AI package though.
  • 1
    @Demolishun It's probably because they tend to be not as popular as the mainline packages, since it's not text nor image gen. In this case, it's some transient library causing a fuck-up. Also, libraries assuming you're using conda

    For a while, most AI libraries were stuck on old versions of python as well because of the way they bound the C functions to python
  • 1
    "Why do science bros write such shit code" - because their expertiese is "doing science", not "writing code". else they would be code bros.
  • 0
    @tosensei Sure, but then they modify things like LLVM. If it was just shit python code, I could deal with it.
  • 1
    @BordedDev

    "libraries assuming you're using conda"

    This is nightmare shit right there.
Add Comment