Also, this tool exists to fix card errors at field and reduce support costs, not to advocate their superior jutsu of formatting. The latter is not the point.
The fundamental problem, I think, is that FOSS didn't really take off in Japan the way it did in US/EU, for some reason. There are tons of code-literate engineers but way less who would be sympathetic with developer community building, code sharing, licensing discussions, etc., that are more common in communities from US/EU.
I find these cultural differences very interesting. I wonder why it’s that way. I noticed some lower willingness to share work (and any form of bad news) in more competitive societies, but I’m unsure this would be the case.
Culture eats strategy for breakfast
Software developers are also not seen as "real" engineers there. They're just typing words into a computer, right?
You can of course "just program" the same way you can "just build" a car out of plywood and some electric motors, however the presence of an engineering mindset (and tools/resources) is what separates a fire hazard from a Ferrari.
On the one hand, I get that and I get that you might not want to take criticism etc on a small utility that you create...
However, on the other hand, if this such a pervasive issue as to merit an official "correct" implementation, then I would think you would want more implementations working correctly, so that your brand behaves more consistently, correctly, across impls.
I could've done it without AI (I've done it before) but it would've taken me 20x longer.
Are you a communist? /s
Jokes aside. I'd love to see this standardized and widely available with a document why SD cards needs to be formatted this way, but I think everyone is afraid that someone's patent or secret or something will be revealed, and its library form is probably, really a revenue stream for them.
Shortsighted, I may say.