# Impromptu discussion 2025-07-30

* rustconf
* want to give a few insights
* plans for next few weeks

## Pete's takeaways:

### Coding output that's useful is the following:

* Primer to the space (e.g. safety-critical) as a section
* If there are specific enablers, can raise them as examples, one section per each
* if there are regulatory requirements, raise those
* e.g. MC/DC is required for regulatory reasons
* Tag these by e.g. Rust (the language) and/or Rust (the ecosystem) to clarify ownership

### Todo

Will get a draft out this week to Niko and Jack to make sure headed in the right direction
* HackMD probably easiest
* Should I put this in the Rust Vision Doc "folder" on HackMD?

# Interview list ("the Jack list")

## Jack

### Scheduled

- erik karulf (Amazon store)
- On vacation in August, scheduled for Sept. 9th

### Emailed (no response yet)

- [e-mail] - "Currently I work on web applications written in Java/Spring so I haven't yet felt a need to pick up Rust."
- [e-mail] - "Haha it's been about a week."
- [e-mail] - "but compared to FastAPI in Pythonland it's not even close to as pleasant a developer experience."
- [e-mail] - "The first steps of Rust, getting the language setup and running hello world were painless, starting to write my own code was trickier and felt like I was back in the first days of learning to code. "
- [e-mail] - "I find the language as an interesting path for me to try out low-level coding. A web server would be more within my domain, but I think Rust could be a fantastic choice for writing desktop native applications and games."
- [e-mail] - "A pet project of mine switched from Python to Rust for performance boost. That's how I became curious of Rust"

### Emailed (response, not scheduled yet)

- [e-mail] - "I haven't had a project that it seemed like it would be the best fit for, so I haven't tried it, but I am worried that it will be too steep of a learning curve for someone who has mainly programmed in high level scripting languages."

## Pete

- [e-mail] - "As the head of an engineering department producing HW IPs and SW, some of the engineers started to use Rust to develop infrastructure tools."
- ST Microelectronics, very interesting
- Sent email
- [e-mail] - "We do not use Rust as we feel the language is too volatile due to a lack of standardization."
- "expert in the development and manufacturing of cutting-edge electronic products for use in explosion-hazardous environments in the process, petrochemical, and tank storage industries for almost 20 years."
- Sent email
- Woven folks:
- Adam Panzica (architect for in-vehicle/safety-critical/embedded software; bullish on C++, bearish on Rust)
- David Hooks (team lead for in-vehicle/safety-critical/embedded software; also bearish on Rust, but maybe a bit warmer)
- Sent Slack message to these two
- Amazon folks:
- noah lichtenstein, eric jones (safety-critical/embedded)
- Sent email
- joemag,
- Sent email

## Niko

* **John Robbins ([e-mail])** Comfort Level 2, -- Experienced C/C++ developer transitioning to Rust after years in traditional systems programming. Represents experienced systems programmers making the transition - can speak to both the challenges and the "why" behind the difficulty.