Maybe ask a web dev community about this.
There could be something better written in Rust.
There could be something better NOT written in Rust.
They should know.

Good. But a lot of us do this already:

[target.x86_64-unknown-linux-gnu]
linker = "clang" # for mold
rustflags = ["-c", "link-arg=-fuse-ld=/usr/bin/mold"]

[target.x86_64-unknown-linux-musl]
rustflags = ["-Z", "gcc-ld=lld"]

I didn’t understand your sentence. But: Having concerns is valid.
Having them in the context of this story/ad is misplaced.

IBM invested 1B$ in Linux all the way back in year 2000 (imagine how much that is worth with tech inflation), and they did it again years later.

That 1M$ is nothing. It’s not nearly enough to control the Rust foundation for one year, let alone controlling the Rust project as a whole. Calling it a “Vote of Confidence in Rust’s Future” was probably a good-spirited joke from the author, at least I hope it was.

Note that IBM still doesn’t control Linux (even after acquiring RedHat), and we still have no problem calling them evil. Some of us still have no problem calling MS evil either, although many of the new crop of developers won’t, because for them the chance to have the financial privilege of working there someday outweighs any moral considerations. Incidentally, there is a good intersection between this group, and the group that takes moral posturing about whatever in-group approved cause of the month to the maximum. Ironic, isn’t it?

This is effective advertisement, not a donation. A real ad (with a campaign) would probably have cost much more, and wouldn’t continue to be propagated for free months after the ad campaign is over, like this peace of news.

This type of ad is also much harder to filter/block, since not only it appears to be site-native, but also topic-native.

Not based on, but built on top of Iced.

The fork wouldn’t be that different from whatever upstream Iced snapshot it last synced with. There are two major, if peripheral, changes still. A renderer for some Wayland special needs, and some integrated accessibility support. At least that was the case until a few weeks ago. I don’t think anything significant changed since.

So the Iced API itself is largely the same. However, since this is built on top of Iced. COSMIC apps are more inclined to use abstractions and tools from libcosmic wherever applicable instead of using Iced API directly. But you still see plenty of direct Iced API use.

Thunderbird is still going?

What’s next? Rust in Songbird?

You can easily guess who is behind such narratives and why.

You would think so. But anti-FSF sentiment comes in different forms nowadays.

My first (and only) visit to the Mastodon world was years ago. Top post (or whatever you call them) was from some micro-celeb (who probably didn’t even code) bitching about how Stallmann caused great damage, and how the FSF’s biggest achievement was giving decades of “our” free labor to corporations. The microblogtards replying agreed of course. Needless to say, that tab didn’t stay open for long.

Social war ultras (big intersection with microblogtards) also don’t like Stallman and the FSF.

So, new developers may have chosen non-FSF licenses not only because of copyleft implications. But also because it looks and goes along better with the posturing ethics of the times. The snowball has already gotten large of course, and next-gen devs may just be going along with the choices made by their predecessors or library dependencies without knowing much about the why.

Still, there should probably be more MPLv2 in the Rust ecosystem.

It’s a conspiracy too big that I don’t think anyone of us can really understand or grasp the scale of it all.

Thankfully, the EU was aware and prepared. And the EUPL is ready to usurp whatever project license, whenever needed.

Wasn’t Iced basically a one man show before system 76 started using it for their desktop environment and made huge contributions to it?

No. And what they contribute, they contribute to their own fork.

They do, however, help the ecosystem with crates like cosmic-text.

I think for now your best bet is probably…

Their best bet was to ask around (done) and filter out the waffle. They already got a good specific actionable answer out of it.

See! Unlike the post from last week, this post actually provides useful and actionable info.

Good luck to the Ferrocene team.

Yay. My first ad-masquerading-as-a-genuine-post experience on Lemmy!

Thus, we’ve developed a cargo extension that transparently queries the Phylum API for information about a package before it’s allowed to build.

Only our* malware-like behaviour is blessed. Because it’s a feature. And research-based. And security-oriented. And commercial! We told you about it beforehand and sold you the idea.

* Assuming the malware discovered is not theirs too.