News for hackers. Stuff that matters.
Re:Dioxus Labs and "High-Level Rust" by dash2 on Sunday June 23, 2024 @09:01AM (#40767172)
The "Capture" trait looks very like the following proposal for a "Claim" trait, motivated by very similar pain points:

https://smallcultfollowing.com/babysteps/blog/2024/06/21/cla...

Re:Dioxus Labs and "High-Level Rust" by aib on Sunday June 23, 2024 @03:48PM (#40770072)
A pain point, for me, is having to explicitly type private functions.

I like refactoring independent blocks out into functions, to separate the scopes and have readable summaries a la self-documenting code. Having to fish out and then explicitly enter some library's useful but complex type makes it unpleasant.

I'm starting to see a pattern here... Hmm, maybe private functions should be treated differently?

Re:Dioxus Labs and "High-Level Rust" by sam_bristow on Monday June 24, 2024 @03:44AM (#40773443)
For those who missed the earlier article this is refering to, I think it's this one:

https://loglog.games/blog/leaving-rust-gamedev/

Re:Dioxus Labs and "High-Level Rust" by poulpy123 on Monday June 24, 2024 @07:05AM (#40774560)
> I argue that Rust’s success is social in nature. My hot take: Rust’s popularity does not come from its technical merits.

This is very true: Rust has found success because it arrived at the good time, in the good niche and pushed by the good people. Obviously it has technical merits because else it would not have succeeded, but its success compared to other languages that have also technical merits is based on other reasons

Re:Dioxus Labs and "High-Level Rust" by aredox on Monday June 24, 2024 @03:17PM (#40779632)
It is almost always the case. IT in general is far less driven by objective technological progress than we ourselves tend to think.
Re:Dioxus Labs and "High-Level Rust" by tracker1 on Monday June 24, 2024 @03:13PM (#40779595)
I am not a deep, low-level developer... I've only tinkered with some direct hardware access over the years. I will say, that I've toyed with Rust (Axum and others) for mid-tier API usage and found the results to be more than effective.

I didn't find working with Axum to be much more difficult than say Koa with Node or C# since .Net Core. It took a bit of structure to get things going, but in general it was relatively straight forward.

The couple things I've done on the UI side, mostly around Yew, has been much more difficult for me to wrap my mind around however. I think there's room for improvement, and I do think there's room for a better templating structure. There's definitely not a white box solution for getting things done like some other platforms and languages. You have to put a bit more of it together. It's the difference between Lego Mindstorm and Duplo.

Re:Dioxus Labs and "High-Level Rust" by jmartin2683 on Monday June 24, 2024 @06:10PM (#40781529)
We use rust for all sorts of stuff at work and definitely don’t find progress on anything to be slow. If anything, we ship much faster and with a lot more confidence than most (all?) of the other teams in our org that don’t use rust.
Re:Dioxus Labs and "High-Level Rust" by tw061023 on Tuesday June 25, 2024 @01:20AM (#40784762)
Could you please tell what languages and technologies other teams use?

Comparison statements are meaningless if there's nothing to compare to.

Re:Dioxus Labs and "High-Level Rust" by rjmccall on Wednesday June 26, 2024 @01:35PM (#40802388)
This is an interesting article, but as a Swift language designer, I'd really appreciate it if people didn't randomly throw out wildly inaccurate information like "Basically everything in swift is an Arc<Mutex<T>>".