May 6th, 2024, GOSIM 2024 Europe hosted by the organization of Global Open-Source Innovation Meetup (GOSIM) will be officially held in Delft, Netherlands, Europe. This grand event has provided a…
Missed Office Hours last week? No problem: the full recording is ready to watch on YouTube and @tilvids.
The 3 developers behind the effort to bring native Microsoft Exchange support to Thunderbird discuss their adventures in Rust, and explain the long-term benefits and steep challenges associated with this project.
The three developers behind the effort to bring native Microsoft Exchange support to Thunderbird join us to discuss their adventures in Rust, and explain the long-term benefits and steep challenges associated with this project.
Rust's unexpected super-power is just how flexible it is. It allows you to write very high level looking code on a low level language. That caused people to use it beyond its intended niche. But it is fundamentally a low level programming language. It will continue becoming easier to use (that's my personal goal!) but there are "obvious" changes that would make things easier at the cost of speed or correctness that #Rust cannot take. #RustLang
This is a great insightful post about #GameDev in #Rust, worth reading even if you’re not not into either of those but are interested in programming languages and computer engineering. — “I'd argue as far as maintainability being the wrong value for indie games, as what we should strive for is iteration speed. Other languages allow much easier workarounds for immediate problems without necessarily sacrificing code quality.” https://loglog.games/blog/leaving-rust-gamedev/
Im currently writing code for my #rust implementation of an external #http Server for #xmpp file uploads. I have recently started migrating from hyper to tiny_http and would like to publish a new version and am currently testing it. But it would be great if other people could also test (or would like to review rust code) the functionality :)
Our Rust and Exchange Community Office Hours start in one hour, at 16:00 UTC! Find out how to join us on Big Blue Button in our blog post. Hope to see you there! 🦀
In case you're not following our blog (gasp!), our Rust developers have the technical details on how we're using the language to bring in native Exchange support in the latest post.
So if you're a fan of all things Rust and email protocols, and you want to know what we've done so far and what's coming next, give it a read - and come to our office hours all about Rust and Exchange tomorrow at 16:00 UTC!
Thunderbird will support Microsoft Exchange Web Services (EWS) natively, all written in Rust! Read about our Rusty adventures, the technical nature of the EWS
If you're eagerly anticipating Rust and native Exchange support in Thunderbird, have questions, or want to know what this is all about, you'll want to tune into our next Community Office Hours on April 23 at 16:00 UTC. 🦀
I think it is worth for #hyper and the #rust ecosystem to work as #curl backend but not other way around. The only reason for curl to support hyper is to validate that the backend api is flexible enough and to have another "validator" for such interface. But probably it is one of those piece of code that maintainers are happy to push to third parties 😅
We've got a new Developer Digest, and this one is full of updates on Rust and Exchange support, a better mailing list subscription experience, and a successful ESMification! 🎉
So when is native Exchange Support coming to Thunderbird - and what role does Rust play? Get the answer in this clip from our most recent office hours! 📼 🦀
Also, this video and ALL our videos going forward will have German subtitles. Ausgezeichnet! 🇩🇪
Is support for Microsoft's Exchange protocol coming to the desktop version of Thunderbird? What about K-9 Mail and Thunderbird for Android? What's the timeline? Here's your answer in a short video clip from our recent Community Office Hours session.
With the upcoming stabilization of the diagnostic namespace, I want to take stock of the compile time error messages generated by diesel and see what messages can be improved.
Diesel is known for sometimes generating sub-optimal compile time error messages. With the upcoming stabilization of the #[diagnostic] attribute namespace and the #[diagnostic::on_unimplemented] at...
This project needs more/new maintainers. I took over maintainership in 2019 (IIRC) during a project at my employer back then, because I needed fixes/changes in this crate to fulfill my task at work...
Of the 15 top Hubris and Oxide firmware contributors by commit count, it looks like 8 had no prior embedded experience.
Let that sink in.
What we're doing here is not easy, but we've built an environment that lets more people contribute. Rust means big-computer skills translate, and better tooling makes us all better devs.
This feels like a vindication of both Hubris's design goals, and the use of Rust in firmware more generally.
A few weeks ago, I introduced and fixed a bug where I accidentally checked if a string literal, instead of a vector, was empty, jokingly saying that I blamed Clippy for not having a lint against it. Following a suggestion from @zeenix, I created a feature request, and it's now actually implemented. This means that Clippy will now warn you if you try to call `is_empty` on a string. https://rust-lang.github.io/rust-clippy/master/index.html#/const_is_empty
Does anybody have a good idea how one can verify that your rust compiler and the FFI code you interact with use the same libc?
Some of our rust code inside mesa will allocate/deallocate code indirectly via `malloc`/`free` and I don't think we really want to mix and match across different libc impls here.
So we want to figure out at configure or compiler time that everything uses the same libc.
The new GStreamer 1.24 release is also the first that has a Rust component as part of core, in addition to all the plugins that were already part of previous releases.
Ok does anyone have a rec on #Rust learning materials for the incorrigibly object oriented? Like how those concepts map or do not map onto Rust before I spent all my lifetime failing to learn this language lol
Over the last months the Rust/cargo support in meson improved a lot.
It's now ready to build and install a GTK4 Rust application with around 70 dependencies without having to write almost any custom build glue for the dependencies.
The application in question is just a small experiment of mine for rayon and GTK4 input handling / rendering. The more or less same should work for other GTK4 applications at this point.
All this still depends on two unmerged meson PRs, but it's a huge step forward from the situation just a few months ago.
I hope in the future this will allow GNOME applications written in Rust to have a less strange and fragile build setup than what they have right now with mixing cargo and meson.
Learn and prototype with GNOME technologies – Workbench lets you experiment with GNOME technologies, no matter if tinkering for the first time or building and testing a GTK user interface. Among other things, Workbench comes with Live GTK/CSS pre...
Been seeing that repo with claims that the memory safety guarantees in #rust can be easily circumvented without using unsafe, but I lack the time/energy to look into it in detail. Any rust user has a comment on it?
Relatedly, I also released rpgpie 🦀️🔐🥧 v0.0.1 (https://crates.io/crates/rpgpie), an experimental high level OpenPGP API based on rpgp (rsop is built on top of rpgpie).
News from the machine room: the pure #rust end-to-end encryption engine, "rpgp", saw quite some work and a new release in recent weeks and now @hko released a higher level "rpgpie" interface for application developers ( see https://fosstodon.org/@hko/111997998005869515 ) which also powers running the IETF #OpenPGP #interoperability test suite quite successfully .... Delta Chat's security-audited encryption engine is in fact used from several other projects and in other contexts these days and we are happy about it!
Relatedly, I also released rpgpie 🦀️🔐🥧 v0.0.1 (https://crates.io/crates/rpgpie), an experimental high level OpenPGP API based on rpgp (rsop is built on top of rpgpie).
Hm...I'm getting the impression that #Rust is increasingly met with a refusal by some people (it's an almost _hateful_ attitude sometimes).
I wonder why. Of course there are a lot of layers to it, but one is definitely that Rust has gotten a lot more exposure to people and so there are just a lot more potential `match`es that lead to Err(()) and that's Ok(()) (sorry, pun intended).
But I wonder, if there's more to it than what meets the eye (feeling excluded/alienated/left behind?).
🦀 Thunderbird Making Progress With Adopting Rust Code — Phoronix
"Thunderbird developers have been using Rust for overhauling the mail client's Microsoft Exchange support. Rust is proving useful for replacing a lot of old, unmaintained code within Thunderbird. The hope is that with the Rust transition they'll be replacing a lot of old and delicate code paths and improving the overall architecture."
Earlier this month at FOSDEM in Brussels was a presentation by developers Brendan Abolivier, Ikey Doherty, and Sean Burke on the Thunderbird mail client beginning to make use of the Rust programming language within its codebase.
What it does This lint would warn against using try_into from the TryInto or TryFrom trait when there is an available Into or From implementation. Advantage Remove the need for handling an error ca...
❤️ 
🦀 
