[dathinab]

Is anyone besides embedded doing _any_ 32-bit dev outside of maintaining legacy code?

I mean 64-bit PowerPc is by now around 17 Years old and even 15 years ago some of the most widespread users of PowerPc (Xbox) switched to using 64 bit PowerPc architecture...

[monocasa]

Xbox 360 still ran in 32bit mode with the exception of the hypervisor. No use of 64bit pointers on a system with a max of 1GB of RAM other than just wasting cache space, and there's no real other benefit tacked on like you see in other 64-bit archs.

[dathinab]

Thanks I didn't know this. I just looked up since when PowerPc 64-bit is a think.

[monocasa]

Ah. In that case the PowerPC 620 was a 64 bit design from the late nineties.

[ridiculous_fish]

Depends what you mean by "embedded," but almost every set-top box and TV has a 32 bit ARM SOC. These run software under active development: web browsers, Netflix, etc.

[dathinab]

Yup, I included set-top into embedded, too.

Also just to be clear I don't say that rust isn't for embedding, just currently development is focused around server (and kinda desktop) usage with some focus on some of the most wide spread embedding targets.

I hope in the future rust will be the go-to alternative for C/C++ in any use-case (at least any which llvm supports). But we are not there yet. But we are slowly getting there step by step.

[saagarjha]

Embedded sounds like a great domain for Rust that it sadly often cannot really be used in.

[jacobush]

Rust is promoted all the time as the sensible choice for embedded work instead of C or C++.

[steveklabnik]

The thing is “embedded” is an extremely broad space. There’s a bunch of Rust stuff going on in some corners, and absolutely none in others.

[jacobush]

Yeah, to clarify, it’s often touted as great for embedded but wholly impractical, it turns out, for some things. Which can be alarming and unexpected