areweguiyet VS rfcs

The organization behind QT (QT Group) has pretty onerous licensing terms.

My understanding is that it's $3,950 per year just to develop using their libraries on your own computer if you ever in the future intend to commercialize a product using QT. Transitioning from the open source license to the commercial license is something you can do but it's not the happy path and their FAQ seems to indicate that it comes with some sort of penalty.

https://www.qt.io/pricing

Something like Slint (Rust based but includes CPP and JS bindings) is not as comprehensive (yet) but it's more modern and the licensing terms are significantly more in line with software industry norms.

GPUI from Zed is also something to monitor: https://www.gpui.rs/

Also, in general you can find an extensive list of Rust-based native UI libraries here: https://areweguiyet.com/

I would suggest that nearly every person on this website is a developer. Both C and C++ let you shoot yourself in the foot quite easily, but at least C++ has RAII.

If you're referring to Rust, it's just not there yet for anything serious: https://areweguiyet.com/

I normally use python to do some quick data analysis, with pandas/polars/pyspark/...

But I've started to use rust more and more in the last few weeks and really start to like it.

Does anyone have experience doing data analysis with rust, and would you recommend it over python?

And are there any resources like https://areweguiyet.com/ but for data analysis?

You still haven't said anything about why those existing frameworks don't count. Again, they are used in production and do exactly what a gui framework is supposed to do. Sure they may not have all the features of the frameworks that have existed a decade before rust even existed but the issue is time not rust itself. They very clearly can be used to build complex UI without inheritance. Since you mentioned it, you should probably actually look at it https://areweguiyet.com/ the page clearly says that GUI frameworks do exist in rust.

The web site https://areweguiyet.com/ has a list of GUI libraries for Rust.

I haven’t tried any yet as I lack the time, but it can be a good starting point.

Iced and Slint where interesting when I looked at that, and Slint may be done by former Qt developers.

I also hope that it is consistent with the goals mentioned at https://areweguiyet.com/

RFC: Add large language models to Rust

https://github.com/rust-lang/rfcs/pull/3603

Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582

Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.

Literally has nothing to do with memory management.

Congrats!

> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.

Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".

Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.

> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)

> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.

This is great to see though!

I can understand it being a flag on these lower level, directly invoked dependency resolution operations.

While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537

How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.

In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:

https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...

I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:

https://github.com/rust-lang/rfcs/pull/899

Still, no real discussion of why unbuffered stderr.

Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].

Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)

You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].

[1]: https://doc.rust-lang.org/std/arch/index.html

[2]: https://doc.rust-lang.org/std/simd/index.html

[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...

[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...

[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...

[6]: https://github.com/rust-lang/rfcs/pull/3469