The name puts me off though. Why learn something called "rust"? How about "dirt" or "shit" or "pee"?

If there is a programming language called "juicy mango" or "steak with butter and french fries", learn that instead.

People getting stuck on python is a testament to how useful it is :)

Notable exception (from what I've heard): VSCode.

(Although, in this case, it helps that the intended audience of that app is the same profession that the creators of that app belong to.)

Godot does too much for my needs, basically. It's also rather opinionated, in its object-orientedness (and OOP doesn't fit how my brain thinks), and somewhat insular (no easy way to call C from GDScript, for example).

Main issue with Rust is that it's cumbersome to work with dynamic data (like what you'd read from JSON, for example).

There is a Godot extension that allows for Rust to be used with Godot. Haven't tried it, but it a apparently works.

Incidentally, the game isn't going to be pure Rust; I've used the mlua crate to embed a Lua (actually luau, the dialect that Roblox uses) interpreter into my project.

There's two complexities here:
* Strings are UTF-8. This means that each character can be a different number of bytes, and that you can't treat arbitrary sequences of bytes as strings. (Well, you *can* if you use unsafe code, but putting non-UTF-8 data into a string will result in undefined behavior.)
* The whole String versus &str case. Strings are an owned type, while &str is a borrowed type. Learning the difference is one of the important aspects of learning Rust. (If you're familiar with C++, String is like the STL string class, and &str is like char *.)

Python does have its disadvantages, however. Some people find that dynamic typing leads to issues (particularly since they are only found when you try to use the value, not at compile-time), and performance is poor compared to other languages. Rust does not have these issues.

On the other hand, Rust has its flaws, and they tend to be things that Python is actually good at.

Thanks for the tips. Yes, I don't use C++.
About "Python being everywhere": Yeah... That's why the joke on the op. :P

- - - -

A Web-Based wouldn't work for me. Dart apparently is based on this. Plus I personally dislike the idea of making everything Material UI (it seems to be the selling point of Flutter? Sorry if its not.) and bloated because of "multiplatform".

One thing that works everywhere, in my experience, is not optimized anywhere, except when is really possible to optimze anywhere with some ease, or the language itself is well optimized already...

Look at Unity and Unreal engines. This "we work everywhere", at one time in the future, end up costing us all time, money and development progress in my humble opinion.

Well, truth is, I really want performance above all else.
If you can optimize it to everywhere specifically, then its ok.

But then there's this data about Dart x Rust through some benchmarks:

https://github.com/jinyus/related_post_gen

https://medium.com/@tommyyy/the-dart-speed-035272e9d46d

https://programming-language-benchmarks.vercel.app/dart-vs-rust

Since I want performance for my use case, people's comments comparing Tauri vs Flutter on some sites is also a big no-no for me.

https://www.reddit.com/r/rust/comments/uqr1nq/tauri_or_flutter_for_rustdesk_desktop/

- - - -

I understand. You have a point for your case. I just want to challenge myself and learn more instead of procrastinating on a language that I got curious about.

On Python:
Though I don't disdain Python, I dislike the mentality which is a cause of what you described on how Python spread itself.

One example of this is how JavaScript is all over the internet making it excessively bloated with scripts for UX/UI, and thus, prone to bad performance and abuse.

Python shines in DataScience by what I've seen.
But some are saying https://docs.pola.rs/ is going to grow more soon and is better and faster.. because it was written in Rust? I've never used it though.

https://www.statology.org/pandas-vs-polars-performance-benchmarks-for-common-data-operations/

https://www.datacamp.com/blog/an-introduction-to-polars-python-s-tool-for-large-scale-data-analysis

https://www.reddit.com/r/datascience/comments/16eiddh/comment/jzviilj/

- - - -

Just noticed how big this post became.
Sorry for that.

I use VSCodium:

https://github.com/VSCodium/vscodium

It has some hiccups, but this is certainly on my CPU. They did a good job with it, indeed.

- -

Are you sharing your development anywhere? I really got curious to see how your game is going now. I wish you good luck!

- -

I did watch some videos on ownership, borrowship, Strings in UTF-8 and .unsafe.
Also about the ".clone" which, according to the video, is an easy but costly escape from ownership "problems".

It does make a lot of sense for safety.
It 'clicks' when you understand where they came from to do this with Rust.

Thanks for explaining!

* Electron, Tauri, and similar solutions are also web based.
* I think the performance issues aren't from it working everywhere, but rather because the tools used are high-level and not purpose-built to the specific task. For games with simple 2D graphics, for example, a purpose built game engine will far outperform one built with a general-purpose 3D game engine, whether Unity, Unreal, or Godot. (Case in point; Godot has to load and show a splash screen, while my game, at least in its current state, starts instantly once compilation is finished.)

Not at this time.

I still haven't implemented characters, stats, or combat. All there is, at the moment, is some (limited) overworld exploration and a basic event system.

I'm planning on writing the first draft of the battle system next week.

Thanks for correcting me and explaining.
Slint, Iced and Egui aren't web based though. (But then they're not similar right?)

There are types that are reference counted, and all cloning them does is increment a reference count and copy a pointer. Rc and Arc are examples of this, and they do solve ownership problems if you don't need mutation. (If you *do* need mutation, you can get it via interior mutability, via Cell, RefCell, Mutex, or RwLock. Or UnsafeCell, if you really know what you're doing and are comfortable with unsafe code.)

I'm not sure about porting rust applications to mobile. (Especially not Apple), but for many other applications, sure. Remember, Apple makes you pay though the nose for every last bloody step of developing for them.

ICED might be your best bet for getting things done in terms of GUI, it's what COSMIC is building their desktop on.

That is indeed the most important question to ask.

No harm, and possible great benefit though, from learning another language anyway.

If I was younger, I'd maybe learn a few other languages. As I'm not, and are happy using AutoIt 99% of the time, I will just continue to do that.

If I was younger, I would probably focus on creating Android Apps.

Thanks! Will write this down for future reference.

Im not familiar with developing for iOS at all.
Can't we develop custom "apks", like on Android, for personal use and distribution for close people only that use iPhone?

The app I intend to do is for a group of musicians I play with, so its nothing "commercial". Just a little tool that matches our use case.
I know I can do something like this quite easily for Android, but one of the musicians uses an iPhone, so I'd need to develop for them too.
By what I know, anyway, the only thing you need is a digital signature or something, but the app can be fully open sourced and even uploaded to F-Droid, following certain guidelines, right?

Also, about Iced, people all over the internet praise it, but it feels a bit complicated to understand.
Slint is easier for someone learning Rust, but I will still decide what to do when the time comes.

Thanks for the tips too.

Yup.

Thank you very much for the valuable insights.
As explained above when quoting Darvond, nope, iOS is not a major focus, as most friends that would use it are Android users.

Will still decide what to do.

Rust documentation is amazing.
One of the best documentations I've ever seen.
Looks like it was made for someone first learning to program.
Not kidding. Really helpful.
Maybe that's a good reason for its fast growth last years.

Tried to use Iced documentation... theres almost nothing there.
Really hard to learn as someone starting on it.
Devs said they will be working on it on time by a random post somewhere I read.
It does indeed look good for GUI development... but geez... Help. :p

Slint documentation is ok, really simple to navigate and understand too, like Rust's.
Unfortunately It lacks some more precise details for beginners on it like me.
Still could manage to create a working UI easily with buttons, colors, etc easily.

Anyway, thanks everyone for the recommendations and tips for specific hardware and situations/use cases.
Specially on mobile GUI and Rust logic so will have to look at each calmly later.

Thanks again.

Just commented this... and, surprise, they updated their documentation today.
This is incredible.

https://docs.slint.dev/latest/docs/slint/

Maybe we have some Slint devs around here? :P