Rust

8182 readers

11 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

torcherist@programming.dev

New to Dioxus and Rust. Any tips about getting started? (programming.dev)

submitted 3 days ago by xoron@programming.dev to c/rust@programming.dev

6 comments fedilink hide all child comments

Hey, I'm a webdev. I previously approached the project with JavaScript. I'm familiar with the js ecosystem.

I put a fair bit of consideration and in contrast to my JavaScript-approach, I'd like to investigate Dioxus.

I'm not completely new. I've dabbled in rust before. I have read a lot of the docs and I'm sure there is much more to learn amd practice. I also don't want to downplay that I'm ai-slop-maxxing at scale.

What advice would you give to getting started with the rust ecosystem approach?

Similar to a lot of languages there are considerations for things like tests. So it would be useful to see the options there. As well as any other best-practices and nuances.

In relation to my project, I'm particularly interested in the tooling available in rust for formal verification.

Just to be clear, im not here to waste your time on my slop, but if you want to see what I've got so far (practically nothing):

you are viewing a single comment's thread
view the rest of the comments

[–] ExperimentalGuy@programming.dev 1 points 1 day ago (1 children)

What's your goal with switching languages? You need to figure out what business requirements are fulfilled more effectively given that technical change before making that change. I mostly say this because I don't hear a clear reason for the switch in your post.

For the rust ecosystem in general, reading through the cargo help output to see what tooling is there is a great start. You can see what functionality is already baked into the native language tooling, which should guide you on the right path. Off the top of my head, theres ways to test and lint your code already built in. Best practices are usually crate dependent, especially when working with something (I think) is macro heavy like dioxus(I don't do a lot of UI in rust). Make sure to go through the provided dioxus code examples because those will probably cover most use cases you'll be going for.

[–] xoron@programming.dev 1 points 1 day ago (1 children)

im switching to the rust stack mainly because i think it has better tooling formal-verification. formal verification is particuarly important in my project because it relates to cryptography.

i assume i can get something comparable to what i already did with JS... but with rust, i may be able to break out of the browser environment.

i not only want to be able to offer a native gui version, but with rust i think im on track for also being able to create a cli tool too.

[–] busyvar@piaille.fr 1 points 17 hours ago* (last edited 17 hours ago)

@xoron @ExperimentalGuy if you need server side processing, fullstack mode have a nice macro to generate API calls.

In case you need a js lib (ex. Codemirror editor) wasm binding allow to define extern interface.

For any technical issue feel free to post on their Discord forum.