Yep, exactly. You can actually look at their source code, it should be very good for learning.

Basic human decency, hopefully.

Presumably such behavior could get you into moderation trouble, just guessing.

What's to stop someone from getting AI to do it, or just replying "LGTM"?

Very nice read, the code examples were very clear :)

Pretty elite flex, ngl

Wow that's pretty crazy. I guess this bug was only in nightly?

Also I want to know more about this guy's crazy build system.

Almost certainly prevents some inlining or loop unrolling or something like that.

Weird. I threw it in compiler explorer and the assembly got longer (as expected).

Slint is pretty much the spiritual successor to QtQuick. I think it's written by people that used to work for Qt, it has a similar design (GUI focused DSL with automatic reactivity), and they are even using the same business model - basically free except for embedded use (cars, petrol pumps, PoS etc.). But without the decades of baggage Qt has and with support for Rust from day one.

It can even use Qt as a backend somehow.

I had a go with Slint because it does look impressive but tbh the amount of setup you have to do is just a bit too much compared to something like gpui-component. Probably worth it for a bit project I guess.

Ahh too bad, thanks for the answer though :)

Not really in practice. In older versions I have done it, but they really don't want you to. The binaries are only distributed as shared libraries, so you at least need to build Qt from source. And also whenever I build recent Qt apps even with QtWidgets it has a load of plugin files and other nonsense that it needs.

I'm sure it's possible with enough work but it's not simple like with fltk or egui or gpui.

Yeah that part from them was very disappointing. I was really hoping for the qt style integration to be maintained. I really want to do something that integrates well in our plasma/kde environments but don't want to touch those weird languages to do it.

Hoping this new approach from qt is successful. They tried to maintain others like qt jambi but that is kinda of abandoned or wtv.

Well yeah, but I would want to use Qt/QML to have native integration with something like KDE Plasma.

Unfortunately Slint just recently announced that they will be slowly deprecating the native styles except Fluent, which is Windows's useless and unused style: https://slint.dev/blog/default-native-style-change

So it is quite good to have this Qt Bridge for Rust.

Being rust native with a ui language like qml and showing all their things working with 3 or 4 languages every release.

Couldn't find any info, so maybe someone here knows: Is QT statically linkable, in particular when used from Rust? That's something that I really value in fltk.

Maybe they were scared of the work Slint is doing.

What work?

Freaking about time they did something like that. Everyone looking for GUI alternative frameworks to run away from eletron and people find qt only to realize that it's impossible to use because you'd have to use that weird cpp language or use python for the only reasonable alternative they support.

Maybe they were scared of the work Slint is doing.

Seems I'm not the only one who was impressed by the response time opening an issue on the Rust repo. The bug I opened wasn't even critical. It's amazing how fast they fix them, honestly.

Faster build speed? Yes please!

Congrats.

Perhaps no project is more deserving.

Here's a blog post about the miscompilation bug: https://parsa.wtf/cast/

Riiiiight. You might want to look up what Hitler actually did. It was just a little worse than anything these companies have done. Just a smidge.

This sorts of formalizes something that always existed ("communicating with rust users in production", "experience reports", ...etc). And it could be argued that centralizing and publicly documenting these activities is a positive move.

But this argument runs hollow in the presence of this potential start to a bureaucratic behemoth pushing towards a committee-centric model.

Best case scenario: this is just a (side-)gig bureaucratic job for the boys, which will largely be irrelevant as far the Rust project itself goes.

Thankfully, that scenario is not implausible.

Not sure what some of these clueless comments in this thread are about. Maybe stop treating every new news item as a connected next episode in a telenovela of grand conspiracies and big betrayal.

For one, linuxiac is a decent news outlet for open source and linux news

For 2, wdym "reposting spammer", 2-year-old-account with-a whopping-13-posts lolol feel free to contribute more of your preferred sources to the threadiverse