kas VS rust

Qt classic/widgets? I'm developing Kas to offer vaguely similar features (e.g. data models, theme abstraction, custom widgets with complex event handling), though said event handling and data models are quite different. It's still got a long way to go (so API is not stable), but in case you are interested, I should be dropping a new release tomorrow.

KAS GUI

kas-wgpu looks hopeful, but there's very little information about it and I'm not even sure it works on Android.

Changelog

The next release will support dynamic linking which approx. halves the recompile time in my quick tests. This is based on Bevy which also recommends using LLD (see here); I didn't have much success with this yet however.

If you want a "native-like" toolkit like Qt but Rust-native, then Druid, KAS and Iced are the most advanced in my opinion (though all are incomplete).

Yes. It was actually a mistake (using a nightly compiler and not realising the lock-in). But in this case (with KAS still in "earlyish development" and the workaround being less concise), I decided to leave it.

This is a little library I've been using recently (original version here).

Hello, I am github.com/dhardy, maintainer of rand, former dev of OpenMalaria epidemiology simulator, author of KAS GUI and Rust enthusiast since 2013. I may be interested in positions within Europe.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.