this post was submitted on 05 Jul 2023
2 points (75.0% liked)
Embedded
264 readers
1 users here now
We talk and share about anything Embedded, including;
- PCB Design.
- Hardware architecture.
- Embedded platforms and chipsets.
- Protocols.
- Embedded programming.
- Digital Logic.
- FPGA.
- VHDL, System Verilog...etc.
- Intel Quartus, AMD Xilinx...etc.
- DIP, DSP.
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I must admit that I'm disappointed with this article. It' fairly standard "why isn't X used in a field A" and the answer is: we've always used Y, so all libraries and tooling assume Y, and things are slow to change around here anyway. There is nothing specific to Rust, and the only semi-specific thing to embedded programing is noting the reliance on vendor provided libraries. I wouldn't be surprised if it was generated by ChatGPT.
gotta agree with that, all the points in the article are pretty standard and could be made for any "tool adoption" in any setting
ChatGTP won't make claims such as "Rust is an exciting language, and I expect it to gain market share slowly. However, I expect more teams to adopt C++ than Rust over the next half-decade." but will use a lot more weasel words haha.
As for the argument being "it's not standard", it's dull but quite true