Ok, I know maybe it's too early in this projects lifecycle, but when I read the page this was my initial reaction. As an embedded engineer I found the github p

Ok, I know maybe it's too early in this projects lifecycle, but when I read the page this was my initial reaction. As an embedded engineer I found the github page incredibly frustration, and it's tempting to just write it off. If the original author, or anyone else putting a putting together a language page, here's question I shouldn't have to dig for: 1. Where's an example this has been used professionally? (or out side an academic setting) I'm pretty risk adverse since FW/embedded systems are harder to OTA, and changes once we've approved the HW design blows up projects. If it hasn't been, be upfront about it. 2. What's the plan for the project? Is the language stable? Is a standard library next? I use a vendors language/BSP to avoid writing everything little thing from scratch, like printf() 3. Give me a comparison to other languages, why should I use T1 over any other embedded solution. Include size, and maybe the performance hit. 4. Show me some code. If I'm picking this for a project I need to think of everyone else I need to teach the language too, and how they'll accept it. It really helps for a quick glimpse at the syntax to see how foreign it is. Even if it's just Hello World. 5. How do I access peripherals/HW? For example if I need flash/nvram persistent storage, access to the serial port am I back to C to write driver or interface to the BSP? If so I now need good C skills, T1 skills and good binding skills. Thanks for everyone for the slides, reading the hacker comments pretty much answered 1-5: https://t1lang.github.io/NorthSec-20190516.pdf https://t1lang.github.io/NorthSec-20190516.pdf https://bearssl.org/gitweb/?p=BearSSL;a=blob;f=src/x509/asn1.t0;hb=HEAD https://bearssl.org/gitweb/?p=BearSSL;a=blob;f=src/x509/asn1...