@pro Heh. Python is probably Java's equal as well, as long as you properly test your code. They're even similar in execution speed these days. You can add datatype enforcement with python.
I'd say the main reason for going to Rust rather than Java or Python is if you want your executables to be a file, rather than a folder full of garbage with a script to launch it, and you want a bit more speed and low level access. For the embedded low level development I do, the single executable, speed, and low level access is a benefit. I'm often running my code on single core 500mhz systems, shared with a half dozen other apps, and being able to just stop the service, scp a single file in, and start it is often a very nice thing compared to shoving a tarball through and extracting it.
(Though, you can make Python be a single file if you use the system environment rather than a bespoke python environment just for the application.)
I'd say the main reason for going to Rust rather than Java or Python is if you want your executables to be a file, rather than a folder full of garbage with a script to launch it, and you want a bit more speed and low level access. For the embedded low level development I do, the single executable, speed, and low level access is a benefit. I'm often running my code on single core 500mhz systems, shared with a half dozen other apps, and being able to just stop the service, scp a single file in, and start it is often a very nice thing compared to shoving a tarball through and extracting it.
(Though, you can make Python be a single file if you use the system environment rather than a bespoke python environment just for the application.)
- replies
- 1
- announces
- 0
- likes
- 0
@kazriko You know how they do single file executable these days?
~/bin/PrusaSlicer-2.7.4+linux-x64-GTK3-202404050928.AppImage
I'm not even joking, it works and apparently was the way to go for years. Even works on Fedora despite it notionally leading the Flatpak camp.
I didn't know you were doing embedded. I used to go around saying that I'd only do embedded again if my family were danger of starvation.
~/bin/PrusaSlicer-2.7.4+linux-x64-GTK3-202404050928.AppImage
I'm not even joking, it works and apparently was the way to go for years. Even works on Fedora despite it notionally leading the Flatpak camp.
I didn't know you were doing embedded. I used to go around saying that I'd only do embedded again if my family were danger of starvation.
@pro Haha. AppImage is the ultimate to me of how computing has alternated between Statically linking to avoid DLL Hell, and Dynamically linking to save storage space. It's kind of the worst of both worlds, but I like them a lot better than Flatpak at least. It's taking a dynamically linked application and packaging every one of its dependencies with it.
Yeah, though I alternate between Embedded, HMI, and Industrial programming, Rust and C, J/Python, or IEC61131-3/Ladder Logic.
Yeah, though I alternate between Embedded, HMI, and Industrial programming, Rust and C, J/Python, or IEC61131-3/Ladder Logic.