LLVM sucks
Having recently spent some time trying to get lljvm working again, I can only echo the general sentiment. LLVM sucks. Every point release of the code introduces numerous incompatible API changes, and some APIs are withdrawn with no equivalent replacement being provided. llvm is clearly an immature project thrown together by people who have no clue about software engineering or design. For it to still be so immature after so many years is pretty conclusive proof of that.
(My lljvm tree, for reference https://github.com/hyc/lljvm/tree/llvm3.3)
Having spent a few days beating this into submission for llvm 3.3, still with missing functionality, I just don't have the will to update it again for llvm 3.4. Now I understand why the original lljvm author abandoned the project. Nobody in their right mind would use this piece of garbage.
Having recently spent some time trying to get lljvm working again, I can only echo the general sentiment. LLVM sucks. Every point release of the code introduces numerous incompatible API changes, and some APIs are withdrawn with no equivalent replacement being provided. llvm is clearly an immature project thrown together by people who have no clue about software engineering or design. For it to still be so immature after so many years is pretty conclusive proof of that.
(My lljvm tree, for reference https://github.com/hyc/lljvm/tree/llvm3.3)
Having spent a few days beating this into submission for llvm 3.3, still with missing functionality, I just don't have the will to update it again for llvm 3.4. Now I understand why the original lljvm author abandoned the project. Nobody in their right mind would use this piece of garbage.
Comment