> > > > > > In sum, it's not that NuttX is hard. It's that *NuttX IS MADE HARD, > > PROBABLY ON PURPOSE* >
I told myself to let NuttX go silently (I did unsub), but this overall story matches several I've seen. The core architecture is just weird in ways that don't encourage fresh blood. Whitespace and comment standards seems minor but it not being automatically generated by any existing editor doesn't add value; it adds cognitive overhead for anyone that isn't exclusive with this code. In researching code, I found several majorish contributions in GitHub that silently coasted to a halt after several rounds of hoop jumping. The large PRs have just idled because the devs have gotten frustrated and left. (My various feedback may have been perceived as rude, but at least I told you why I left in the hope you can make it better for the next dev. In zero cases did I feel that feedback was welcome.) In all the cases I noticed, those were the last PRs in this project opened by those devs, so it's a lost talent opportunity. So I'm not sure it's on purpose, but there's a visible brain drain in the thousands (!) of open PRs on the project. Maybe NuttX has reached stasis and the existing team can keep it maintained. It's a cool project and a welcome entry in the space between, say, Free RTOS and a full million line Linux kernel + glibc, so I genuinely do wish the project success whether that's a static core or a growing team. Good luck!
