On 2025-01-28 11:23:26, Sebastien Lorquet wrote: > my trust in nuttx is now hard to maintain. > > Every day a DELUGE of commits (from xiaomi, this is a fact) is added to the > repository. > > I am struggling to understand what happens in this project. > > so many fixes are pushed, how is that even possible? this is a quicksand > project! Project gets more popular. This is both good and bad. More commits/fixes are good, but it also increases chances of something bad slipping thru. Especially that Nuttx does not have that many core developers that can really sit and review the code. And reviews take tons of time and requires lot of knowledge. > > > Also, how are such commits (not from xiaomi!) allowed? No description except > "uf2" ? Where is the adult in charge? > > https://github.com/apache/nuttx/commit/dac3f315a11cead82a5f630d4ae1c3eb45a80377 Commit is awful, true. But then again, you cherry picked commit that supports your thesis.
> I am announcing that after that many years my company has started to develop > a minimal rtos to replace our usage of nuttx, because it is just not stable > enough to be usable for stable long term projects. > > There are too many changes, we are loosing money every time we need an > update. there is no way to maintain the use of a nuttx custom board and > project over several years. What changes are you talking about? Nuttx is Posix, so no "userspace" app should get broken by any change - if it does, then there a problem in Nuttx that should be reported and fixed. Merge conflicts in kernel? Push your improvements to mainline, problem will solve itself for the most part. > Having control of our code will be a better investment. That will obviously > be closed source. Which is, after all, a better way of control on our > products. Good luck with that. Every custom RTOS I worked with was an attrocious. FreeRTOS + Vendor HAL is not good pair. You will be in world of pain. I'd rather use Zephyr than making own semi baked RTOS. Let's not even start on topic when you are going to change MCU vendor (like stm to microchip). Seriously buddy, if not Nuttx, then save yourself some pain and go with Zephyr. > No amount of my involvement in the github triage is going to help, the case > is desperate. I just have no time, no energy, no motivation, no spoons left > to deal with this. it's a deluge of commits, let it be, but without me. > > the warning from the apache foundation that you use too many ci credits > should have been a warning to slow down and reflect on the project > direction. nothing has happened except making it even faster. > > I will also discourage people to use this project, I cannot in good > conscience recommend it to anyone, it would be a trap. Being salty hepls noone. Point out what bothers you. If commits are constantly messing up with your projects it's either your problem or Nuttx problem. These things should be reported so they can be acted upon. Either Nuttx will be fixed or you will be told how to properly maintain your code within Nuttx. It's true that Nuttx does no quite know where it wants to go and be right now. Introducing CMake without removing Makefiles where very bad decision - as you have to maintain two build systems now - which takes time from other more important things. Introducing Zig and Rust feels also like a fashion move. Rust feels like it's being shoved down everyone's throat. And Nuttx has more cleaning up to do before adding even more gimmicky stuff. It really does feel like Nuttx wants to do much more then it was intended to do. Also there is simply not enough manpower to maintain so many things. Less is more, more is less. -- .-----------------.-------------------.----------------------.-----------------. | Michal Lyszczek | Embedded C, Linux | Company Address | .-. opensource | | +48 727 564 419 | Software Engineer | Akacjowa 10a; 55-330 | oo| supporter | | https://bofc.pl `----.--------------: Brzezinka Sredzka PL | /`'\ & | | GPG FF1EBFE7E3A974B1 | Bits of Code | NIP: 813 349 58 78 |(\_;/) programer | `----------------------^--------------^----------------------^-----------------'
signature.asc
Description: PGP signature
