Search

Items tagged with: Rust


I wanna do some #SQL in #Rust. Maybe use an #ORM, unless everyone thinks ORMs are dumb.

What crates should I use?

What would Ferris do?

#sql #rust #orm


:ferris: vs :julia:

My talk about "Rust vs Julia in scientific computing" is confirmed!

I am very excited about it :D
Only 7 minutes, but that is fine for the first public talk :)

The talk will be recorded and I will write a blog post about it. Stay tuned :D

You can still register to the free online conference "Scientific Computing in Rust":

scientificcomputing.rs/

#RustLang #Rust #JuliaLang #ScientificComputing


Really happy to see these results on the perception of googlers on quality of the #Rust development experience, an area I'm highly passionate about. I'd like to take this as an opportunity to encourage the 9% (and the other 91% as well) to file tickets when we don't meet the bar we've set for ourselves.
opensource.googleblog.com/2023…
#rust


I've decided to open source Ebou, the cross platform Mastodon Desktop Client.

You can find the repository here:

github.com/terhechte/Ebou

It also supports Windows, although this is beta and Windows binaries are not included yet (you'll have to compile it yourself). Attached is a Windows screenshot. Linux should be easy to support, too.

I'm open sourcing it because I think there's great value in a high quality cross platform Mastodon desktop client and I can't pull this off alone.

#rust

#rust



I love it when I get #Rust errors that I worked on and forgot about
#rust



fwiw i highly recommend that, if you're interested in the future of #rust, you join the Rust Zulip chat [1]. even if you have nothing to say and just want to lurk.

it's a productive and friendly space for the most part, and a super good way to stay informed on what's happening.

1: rust-lang.zulipchat.com

#rust


Exciting times are ahead! We're starting to see new programming languages evolve the ideas popularized by #Rust. Children of Rust, if you will.

inko-lang.org/

Inko seems to trade off a little performance to get a compiler that accepts more code as valid, but still keeping strong safety guarantees. An easier-to-write language than Rust perhaps.

I'm looking forward to seeing more languages that make coding easier while not compromising on safety and reliability. :blobcatthumbsup:

#rust



One thing I particularly like about Rust — which I’m very new to — is how thoughtfully the compiler errors and warnings have been designed. It not only diagnoses and explains the problem: it provides a possible solution. Genius.

This is the essence of good design: it’s compassionate, anticipating the needs and wants of another person. I can’t think of another language that does anything like this. Certainly not Swift, not that I’m bitter.

#rust #swift


Microsoft is rewriting parts of GDI in Rust, as evidenced by a new file called "win32kbase_rs.sys" which contains a complete reimplementation of the REGION type in rust, and a vive ID called "Rust_GDI_REGION".

#rust #rustlang #microsoft #windows


This is an actual case where a rewrite in #rust would be appropriate.
#rust


🦀 "Why the Rust Community Should Be Worried About the New Carbon Language"

👉 should we?

👉 If we some language can do what Rust can do but more simpler, we should be happy to switch but is that the case here?

Article:
towardsdev.com/why-the-rust-co…

#rustlang #rust #cpp #carbon




Exciting news about #AccessKit: Talon (talonvoice.com/) is one of the first real applications to use AccessKit. In the current beta build (for Patreon supporters), the Talon app core has been ported from Qt to #Rust using the #egui toolkit, and it's now accessible with AccessKit on Windows and macOS (Linux AccessKit support is close, but waiting on a bug fix). #accessibility




Is there a high-level, statically typed language in the #GTK ecosystem?

#Rust, while better than C is overly obsessed with memory to use it daily.

Looking at bindings
gtk.org/docs/language-bindings…

things like #JVM and #.NET are missing, leaving the choice of unhelpful type systems, or caring about unneeded details, or both... Not a good outlook for quickly building apps.

#gtk #rust #jvm



As part of the optimizations, there are a lot fewer temporary allocations now, e.g. for NUL-terminated strings.

Also, in addition to better performance, the code generation improvements also reduce the binary size considerably.

Some GStreamer plugins saw reductions of 15-20% 🥳

#GStreamer #Rust #RustLang


First steps with #Rust, great initiation!
#rust


For me this is the last nail in the coffin for #Go.

I've never bought much into the language. I've been impressed by its constructs to natively manage and synchronize asynchronous operations, but its rigidity when it comes to programming paradigms (no proper object-oriented and functional constructs in the 21st century, seriously?) means that I see it as a language that seriously limits expressivity, and doomed to generate a lot of boilerplate. It's a language very good at solving the types of problem that are usually solved at Google (build and scale large services that process a lot of stuff in a way that the code looks the same for all the employees), and little more than that.

After #Rust really took off, I didn't see a single reason why someone would pick Go.

And now here we go with the last straw: Google has proposed to embed telemetry collection *into the language toolchain itself*. And, according to Google, it should be enabled by default (opt-out rather than opt-in), because, of course, if they make it an opt-in then not many people will explicitly enable a toggle that shares their source code and their usage of the compiler with one of today's biggest stalkers. If they make it an opt-out, well, many people won't even notice, and you can grab more data points from people, whether they know/like it or not.

If you build open-source projects in Go, it's time to drop it and start considering alternatives. The market for modern compiled language is much more competitive now than it was a decade ago. We knew already that we couldn't trust a programming language developed by the largest surveillance company on the planet.

theregister.com/2023/02/10/goo…

#rust #go





let floor = Floor::default();<br>let mut bowl = Bowl::new();<br>let mut cat = Cat::mew();<br><br>bowl.place_on(&floor);<br>cat.sit_on(&bowl);<br><br>let floor: &mut Floor = unsafe {<br>    &mut *(&floor as *const Floor as *mut Floor)<br>};<br><br>floor.lower_by(50 * CM);<br>

Levitation needs some unsafe code, but not around the cat, cats don't take fall damage.

Original post by @Kyu : meow.social/@Kyu/1095710305682…

#RustCataStructures #rust #RustLang #cat #CatsOfMastodon


Not all cats have the gift of levitation.
Those that do, however, do like to flaunt it.


#rust


Spent my lunch break quickly writing up the fun and games of converting an svg to a pdf in #rust with out messing up the text.

Unfortunately I didn't save screenshots of all the weird errors I got along the way they would have been good to illustrate the post with.

parsecsreach.org/post/rust_svg…

#rust


The Rust base64 crate got a new release the other day, which removed (or rather deprecated for now) the simple encoding/decoding API and requires quite a bit boilerplate for such a simple task.

The maintainer does not see the point in providing a simpler API for the common cases because if the API is too difficult to use then Rust is just the wrong language for you 🙄

Too bad the crate has such a prominent name on crates.io and is used so widely. I hope that doesn't turn away too many beginners because something as simple as base64 handling is so complicated.

The data-encoding crate looks like a good alternative for the same tasks. It provides the same amount of flexibility while still providing a simple API for the common tasks.

lib.rs/crates/data-encoding

#rust #RustLang


In exciting async news: the stabilization of `std::pin::pin!` has been accepted, and will be coming to stable on #Rust on 1.68.0!

This will enable "stack pinning" entirely from safe Rust, replacing many of the uses for `Box::pin`, the unsafe `Pin::new_unchecked`, and external crates such as `pin-utils`!

github.com/rust-lang/rust/pull…

#rust


Oh! I made a PR to crates.io less than 3 hours ago, and it's already merged and deployed! 😯

Crates.io now shows little `cargo add` snippets, that you can also copy to the clipboard with a single click.

#rust

#rust


The experimental Rust PR to add a more expressive "interop" ABI on top of the C ABI is IMHO the most exciting new effort that happened in Rust in the last few years.

Thanks to @josh and others for starting this very important work 🥳​

github.com/rust-lang/rust/pull…

Also @Mara's reply seems to indicate that some serious thought is now also put into other related areas, especially for handling Rust dynamic libraries.

github.com/rust-lang/rust/pull…

Very exciting stuff for making Rust a better choice in various areas where exactly these topics were slowing down or hindering adoption.

#Rust #RustLang


Talk on Zero-cost deserialization in #Rust, by @manishearth

> ICU4X has [gone] all-in on zero-copy deserialization, a technique that ensures that data loading involves fast validation as opposed to slow allocation. To help with this, we have built a suite of crates (yoke, zerovec, zerofrom, and databake) that make zero-copy deserialization easier to work with and more broadly applicable.

youtube.com/watch?v=DM2DI3ZI_B…


🦀​ Rust 🦀​ people, is there a way to use conditional compilation in the match parts of a declarative macro? Other than duplicating the whole macro definition.

Basically something like

macro_rules! foo(<br>    ($x:expr) => { {<br>        println!("{}", $x);<br>    }};<br>    #[cfg(target_os = "linux")]<br>    ($x:expr, $y:expr) => { {<br>        println!("{} {}", $x, $y);<br>    }};<br>);<br>

This currently fails compiling: play.rust-lang.org/?version=st…

#Rust #RustLang