Hacker News Reader

This looks great, but I am a bit dismayed by one "will not tackle" feature: qmake support.

Why make this call? Most qt projects default to qmake by default. Making this a will not tackle acts as a big barrier to anyone looking to port their projects over to LeanCreator.

View on HN

I still use Qt Creator for my qmake projects until everything is migrated. It doesn't make sense to add qmake support to LeanCreator because Qt Creator is still available on all platforms and continues to support qmake (at least I have no other information). If people port their projects, they actually don't port to LeanCreator, but to the BUSY build system, which in turn can generate qmake projects in case you want/have to use Qt Creator for some tasks.

> It doesn't make sense to add qmake support to LeanCreator because Qt Creator is still available on all platforms and continues to support qmake (at least I have no other information).

This take sounds ridiculous. It's ok if you want to use the project to try to drive up the adoption of a build system, but it's absurd to argue against the adoption of a widely established build system by stating that people should instead use other IDEs.

Could it be that you have not understood the argument?

Reply on news.ycombinator.com