I wouldn't call my criticism to the 'suckless' philosophy baseless. I think my comments below provides some reasons why I'm criticizing. This[0] might be called baseless criticism though.

> trying to rewrite complex projects into simpler ones without careful planning of how the new projects will handle complexity makes more inconsistent, divisioned ecosystems.

> Trying to cater to a large group of people will always be complex. And trying to cater to a large group of people is NOT the definition of ‘bloated’.

[0] https://news.ycombinator.com/item?id=14553552

It was baseless. You had no evidence CJK will not be supported. It was just a baseless condemnation of the project because the readme referenced suckless.

I'm keep saying this (and it's mentioned in the original comment) - it's not criticism to the project, it's criticism to the 'suckless' philosophy. I have total respect to the project, and I believe that if this project can succeed in having comparable features with less complexity with FreeType, it will be great.

Also, the mention of CJK support is based on my personal experience. (I've mentioned it here[0], previously.) Much bigger open source projects like whole linux distributions or even proprietary software companies don't do CJK (or at least Hangul) properly. I'm pretty sure, from my experience that a small library fails to do it properly. If it does (as I've mentioned above), it would be great.

[0]: https://news.ycombinator.com/item?id=22933613

You have to keep saying it because you haven’t explained why referencing suckless has any bearing on whether the project will support CJK. In particular you have no basis for this statement:

“Ok, this is a bit of a offtopic rant, but this project seems to be aiming ‘suckless’[0].

For me and a lot of users, that means that this project probably won’t be useful for a lot of non-ASCII users, especially for CJK users like me.”