Replies: 4 comments 7 replies
-
|
In this discussion, I would make a distinction between Installer can stay in Python as performance isn't important and python give us pluggability and ease of development. For Ash itself, I'd like to envision AshOS in C, and that's proper C not OOP C++. |
Beta Was this translation helpful? Give feedback.
-
|
I would suggest Go, because it is (like)C but convenient. And it doesn't have the dependency nightmare of C, and it can be easily compiled as a static binary too, and there is also the fact that one can compile it using LLVM/GCC if using CGO, also Go is very readable, unlike C++. |
Beta Was this translation helpful? Give feedback.
-
|
@ochibani In your experience, what has been the pain point(s) with converting ashos to Rust so far? |
Beta Was this translation helpful? Give feedback.
-
|
It was replacing 'python-anytree' and I didn't fix this, as the code still depends on this Python library.😅 |
Beta Was this translation helpful? Give feedback.
-
|
I can see this, but one aspect that I'd like to be considered: Does rust run on all the OSes and architectures that Python supports? |
Beta Was this translation helpful? Give feedback.
-
|
Why not? |
Beta Was this translation helpful? Give feedback.
-
|
Another cons against Rust would be that it is quite contrary to this:
|
Beta Was this translation helpful? Give feedback.
-
Is there a serious problem with this? Statically compiling Rust is not a big problem, however, Rust binaries that are compiled this way are usually bigger than other language's because they bundle everything, not just the necessary symbols. C, C++, Go, Zig, etc, simply bundle the symbols needed, not everything. |
Beta Was this translation helpful? Give feedback.
-
Changes in Rust-Related PRHi everyone, I’d like to discuss the changes introduced in this Rust-related PR. Key Changes:
Final Thoughts:If there were a programming language with the simplicity of Bash or Python but better error handling, it might be a better fit for this project. Honestly, I'm not entirely happy with my Rust code—it feels more like a Bash script written in Rust 😅. The good news is that the code is functional and ready for testing. |
Beta Was this translation helpful? Give feedback.
-
|
Great work @ochibani. I have been following your work since inception and will look closer at the topics you brought up above. For the time being, one quick thing that comes to my mind regarding "Ash ISO (planned for the future)": And regarding bash-infected Rust code, as mentioned in the readme, same issue exists with the python version! |
Beta Was this translation helpful? Give feedback.
-
|
The answer is very simple, I would suggest creating a custom GUI installer (probably Calamares-based). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
With AshOS further maturing I think it's a good time to reconsider our language choice.
When the project originally started I chose Python as the implementation language - simply because it's good for quick prototypes and has a lot of features built-in. But now the scope of the project is much bigger than first expected, so it's a good time to ask if Python is the right language for this project.
One of the disadvantages of Python is it's reliance on a language runtime - if the Python installation is somehow messed up, the entire system falls apart. For that reason a compiled language might be better suited.
Here's a small list of the pros and cons of different approaches:
Approach one - compiled language (C, C++ or similar)
Cons
Pros
Approach two - shell scripts
Cons
Pros
Approach three - keep using python
Cons
Pros
I'd like to discuss the merits of these approaches, and choose whichever one works best for the project. Personally I think approaches 1 and 3 are the more interesting ones.
I'll be waiting for any input from our community!
Beta Was this translation helpful? Give feedback.
All reactions