3 ms·
Sounds like Meson isn't a very good match for your use case. That's too bad. Good thing there are other tools like CMake which are a better fit for you. It seem
by sfpotter 4y ago
Sounds like Meson isn't a very good match for your use case. That's too bad. Good thing there are other tools like CMake which are a better fit for you. It seems like you have also lost some time attempting to port your build over to Meson and failed, which was probably really frustrating. As a result, you really dislike Meson, going so far as to call it "unfit for human consumption".
Many other people like Meson, and many large projects have gone so far as to switch to using Meson. It's great that it worked for them, and it's OK that it didn't work for you.
- oldgradstudent 4y ago> Sounds like Meson isn't a very good match for your use case. That's exactly what I've been saying. > As a result, you really dislike Meson, going so far as to call it "unfit for human consumption". Meson got so many things right, but this one point makes it unusable for many projects, and prevents it from being industry standard. Let me say it again, a programming language for writing large scale programs (11,000 lines is a large scale program) without functions/subroutines is unfit for human consumption. It is made worse by giving a blatantly wrong rationale for not having user-defined function. The only reason I even bothered spending so much time in responding is the hope that they will reverse this idiotic position.
- sfpotter 4y agoI guess it wouldn’t help for me to recapitulate all of the arguments made by bonzini, who actually was involved in the 11,000 lines (down from 15,000 thanks to switching to Meson). He made his arguments very cogently and you apparently either don’t understand them or don’t care to listen. Clearly there are people who think the position isn’t idiotic, and there are large projects which decided that Meson was a great choice and chose to migrate to it. This means that Meson is fit for human consumption.