Did you first try searching for Cordura to figure out what is? Typing that single word into any search engine should point you to Wikipedia within the first few results.
Seems like you’re imposing requirements fora solution without understanding the problem space.
Your approach is like choosing a specific microcontroller you want to use before understanding embedded systems fundamentals. Or choosing a JS framework and being upset an “intro to frontend” tutorial isn’t centered around that specific tool.
I read the Wikipedia page for Cordura before, and re-reading it now I still find it opaque and not helping me understand what it actually is, or how it differs from non-Cordura. Whereas the page I linked above definitely helps me more.
Notably, I can totally understand a person that knows absolutely nothing about programming could come to me with a question of: "How do I create a website from scratch that would use React?" I would not start by answering them with: "Did you even try googling up what React is?", because I'm quite sure they wouldn't understand the explanation as presented on the internet. I would love to instead explain why they don't need to worry about React yet, and to show them a quick outline of a progression to get there, respecting that the decision to chose React or not is theirs in the end. And also tell them of some alternatives that they might want to explore instead of React at some point, and why.
Seems like you’re imposing requirements fora solution without understanding the problem space.
Your approach is like choosing a specific microcontroller you want to use before understanding embedded systems fundamentals. Or choosing a JS framework and being upset an “intro to frontend” tutorial isn’t centered around that specific tool.