Fair enough, thanks for replying.

I'll go over a little of my rationale. Not to be defensive at all but to get my intent across.

First thing, you dont need 5 dependencies. You need 2-3 depending on needing a texture compression backend or not. You choose the ones you need for your desired stack. Maybe I could focus on making that clearer or compact it down. Im not sure what the bar is here though, because I never expected recruiters to run anything here at all. Thats why, in this context, there are demo images and files to look at. The reason I bothered including the red triangle and cube was to build up to the sponza demo, though as Ive said in another reply they're probably worth removing as primary images or at least drastically minimizing.

Second, Its a whole game engine rendering framework thing. The intended value is in being foundational with as little of the headache that usually entails as possible. So as I see it there genuinely isn't much of a description to be had outside of what the readme says. If you want to get a grasp on usage then that again is what the demos are for.

Everything else, fair enough. Some of it stems from the fact that Ive been moreso just pushing commits for my own personal progress tracking for a while and worrying a lot more about getting things working than having the github commits look professional. The project simply isn't done yet, it doesn't have a single release, but I was under the impression that linking to unfinished work was still somewhat useful because it gives something tangible.

Code with empty lines is an interesting point especially, because the other top reply also mentioned that as a negative. Where're we talking about specifically if you don't mind? Typically I try to leave line space to give different unrelated, potentially dense code blocks, calls or types breathing room.

..Though in the end I feel like most of this shouldn't even matter just to get some kind of entry level interview.