It's already being mixed, albeit not very competently.

stop lying.

You are absolutely fucking full of shit.

I chose to "go into war zones" many times and none of it was to "enjoy killing people".

Not sure what military is being discussed. In the US military, you do not choose to go into combat zones. You receive orders to deploy you to a combat zone.

Sure you do, I did.

True, not everyone has such a choice, but I volunteered for the organization I wanted to work for and then I volunteered for multiple deployments I didn't have to go on. Many of us have that choice and make that choice.

Then you aren't one of the dozens he has seen?

So, did you? Look what they made you do, right?

C isn't the problem here. one might argue that the combination of micro python and C and the person writing it having no understanding of how either one works is the problem.

Also running python on a microcontroller to do cryptography is fucking insane.

> Also running python on a microcontroller to do cryptography is fucking insane.

I feel like I should confess to snubbing this (and some other) hardware wallet projects for the fact it used micropython. I think it's hard to draw the line between systems programmer snobbery and good advice... and I feel a little like a cop guilty of stop-and-frisk on the basis of skin color.

Because in general the ideas necessary to produce reliable software aren't well understood or agreed on there is a risk of letting style preferences which are only correlated with good engineering but aren't causative of good engineering get mistaken-- and this can cause errors in both directions, both mistaking stuff as good because it uses the "right" tools, or mistaking something as bad because it doesn't.

I've used open code extensively -- it's not bad, but it's not anywhere near the level of the codex application.