Rust
-
Rustls Outperforms OpenSSL and BoringSSL - Prossimo
www.memorysafety.org Rustls Outperforms OpenSSL and BoringSSLISRG has been investing heavily in the Rustls TLS library over the past few years. Our goal is to create a library that is both memory safe and a leader in performance. Back in January of this year we published a post about the start of our performance journey. We've come a long way since then and w...
-
Bash Script to compile a single rust script, execute the binary and delete the binary
I would like to share a bash script I made for when you want to simply run a rust script once and delete it. Instead of having compile the script with
rustc
, running the binary and then deleting the binary, you can achive all of this with this bash script below.The first argument will be the rust script file name. The
.rs
file extension is optional. The rest of the arguments are passed into the executed binary.Simply name the bash script to something like
rust-run.sh
.``` #!/bin/bash
#Get file path from first parameter path=$(dirname "$1")
#Get file name from first parameter fileName=$(basename "$1") fileName="${fileName%'.rs'}"
#Compile executable and save it in the same directory as the rust script rustc "${path}/${fileName}.rs" -o "${path}/${fileName}"
#If rustc commands retuned any errors, unable to compile the rust script if [ $? -ne 0 ]; then return fi
#Execute compilled executable and pass the rest of the parameters into the executable "${path}/${fileName}" ${*:2}
#Delete compillled executable rm "${path}/${fileName}" ```
If someone wants to rewrite this in rust or add these features into the
rustc
, feel free to do so. -
Help please. Vscode and breakpoints with Yew + Tauri
Hi all,
I'm going through and giving a bunch if different GUI frameworks a go and have tried iced, egui and Slint. Iced was by far the easiest to get started and just seemed fairly logical for layouts, Slint was pretty cool - VSCode actually has like a wysiwyg-editor that allows you to drag components around etc.
Unfortunately I'm having issues getting breakpoints to work when using VSCode, Tauri, plus a Rust frontend (yew, dioxus, etc). I think its because what is compiled isn't where my actual code exists? If I use a JavaScript frontend it hits breakpoints fine, but that's not what I'm wanting to use at the moment.
launch.json { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "lldb", "request": "launch", "name": "Tauri Development Debug", "cargo": { "args": [ "build", "--manifest-path=./src-tauri/Cargo.toml", "--no-default-features" ] }, "env": { "WEBKIT_DISABLE_COMPOSITING_MODE": "1" }, // task for the `beforeDevCommand` if used, must be configured in `.vscode/tasks.json` "preLaunchTask": "ui:dev" }, { "type": "lldb", "request": "launch", "name": "Tauri Production Debug", "cargo": { "args": ["build", "--release", "--manifest-path=./src-tauri/Cargo.toml"] }, // task for the `beforeBuildCommand` if used, must be configured in `.vscode/tasks.json` "preLaunchTask": "ui:build" } ] }
tasks.json { "version": "2.0.0", "tasks": [ { "label": "ui:dev", "type": "shell", "isBackground": true, // change this to your `beforeDevCommand`: "command": "trunk", "args": ["serve"] } ] }
-
What are you working on this week? (Okt. 20, 2024)
Hi rustaceans! What are you working on this week? Did you discover something new, you want to share?
-
Blocking code is a leaky abstraction – notgull
notgull.net Blocking code is a leaky abstractionAsynchronous code does not require the rest of your code to be asynchronous. I can’t say the same for blocking code.
-
Typst 0.12 released
typst.app Typst 0.12 is just ... better – Typst BlogBetter layout, better PDFs, better performance, better internals. Typst 0.12 is the result of over six months of hard work by us and many open-source contributors. ...
>Typst is a new markup-based typesetting system that is designed to be as powerful as LaTeX while being much easier to learn and use
Typst is awesome, in particular if you want to generate documents programmatically.
- blog.rust-lang.org Announcing Rust 1.82.0 | Rust Blog
Empowering everyone to build reliable and efficient software.
-
Does crates.io have a backup plan?
It's possible that the .io cctld is going to go away [0]. Does crates.io have a backup plan at all? Does anyone know what problems it would end up causing?
I imagine the package registry having to move domains is going to cause a ton of problems.
Frankly, it's concerning to me that so much of the Rust ecosystem has chosen to standardize on shaky ccTLDs. The Indian Ocean Territory (.io) is a small island territory whose only inhabitants are a single military base, it is crazy to use that domain for something important. Serbia (.rs) is more stable, but they could still cut off access for non-Serbians if they wanted to.
[0] - https://en.wikipedia.org/wiki/.io#Phasing_Out
-
What are some mind blowing Rust tricks?
If we were to create a Rust version of this page for Haskell, what cool programming techniques would you add to it?
-
rsky: AT Protocol implementation in Rust – a Blacksky project
github.com GitHub - blacksky-algorithms/rsky: An AT Protocol Implementation built in Rust.An AT Protocol Implementation built in Rust. Contribute to blacksky-algorithms/rsky development by creating an account on GitHub.
Links:
- https://atproto.com - https://atproto.com/articles/atproto-for-distsys-engineers
- https://www.blackskyweb.xyz - https://bsky.app/profile/rudyfraser.com/post/3l6d7mmzhik2r
> For a lot of us, atproto projects are some of the biggest (most users, most publicized, most code written, etc.) projects we’ve ever done. For me, it’s also my first time working in open source (ironically, someone asked me to be more open about that) > > If you can help, pls check out open issues.
I know not everyone thinks highly of atproto around these parts, but please don’t let that get in the way of welcoming a fellow rustacean into the open source world 🦀
-
Bacon v3 released
Bacon is a Rust code checker designed for minimal interaction, allowing users to run it alongside their editor to receive real-time notifications about warnings, errors, or test failures (I like having it show clippy's hints).
It prioritizes displaying errors before warnings, making it easier to identify critical issues without excessive scrolling.
Screenshot (from an old version I think):
v3 adds support for cargo-nextest, plus some QoL improvements.
-
My frustrations with Rust. Why is this the most loved language?
I'm making this post after endless frustrations with learning Rust and am about to just go back to TypeScript. Looking at Rust from the outside, you'd think it was the greatest thing ever created. Everyone loves this language to a point of being a literal cult and its popularity is skyrocketing. It's the most loved language on Stackoverflow for years on end. Yet I can't stand working in it, it gets in my way all the time for pointless reasons mostly due to bad ergonomics of the language. Below are most of the issues I've encountered:
-
Cargo is doing too many things at once. It's a build system but also a package manager but also manages dependencies? Idk what to even call it.
-
Syntax is very confusing for no reason. You can't just look at rust code and immediately know what it does. Having to pollute your code &, ? and .clone() everywhere to deal with ownership, using :: to refer to static methods instead of a "static" keyword. Rust syntax is badly designed compared to most other languages I used. In a massive codebase with tons of functions and moving parts this is unreadable. Let's take a look at hashmaps vs json
rust let mut scores = HashMap::new(); scores.insert(String::from("Name"), Joe); scores.insert(String::from("Age"), 23);
Supposively bad typescript
javascript const person = { name: "joe", age: 23 }
Js is way more readable. You can just look at it and immediately know what the code is doing even if you've never coded before. That's good design, so why do people love rust and dislike typescript then?
-
Similarly, Async code starts to look really ugly and overengineered in rust.
-
Multiple string types like &str, String, str, instead of just one "str" function
-
i32 i64 i8 f8 f16 f32 instead of a single unified "number" type like in typescript. Even in C you can just write "int" and be done with it so it's not really a "low level" issue.
-
Having to use #[tokio:main] to make the main function async (which should just be inbuilt functionality, btw tokio adds insane bloat to your program) yet you literally can't write code without it. Also what's the point of making the main function async other than 3rd party libraries requiring it?
-
Speaking of bloat, a basic get request in a low level language shouldn't be 32mb, it's around 16kb with C and libcurl, despite the C program being more lines of code. Why is it so bloated? This makes using rust for serious embedded systems unfeasible and C a much better option.
-
With cargo you literally have to compile everything instead of them shipping proper binaries. Why??? This is just a way to fry your cpu and makes larger libraries impossible to write. It should be on the part of the maintainer to build the package beforehand and add the binary. Note that i don't mean dependencies, I mean scripts with cargo install. There is no reason a script shouldn't be compiled beforehand.
Another major issue I've encountered is libraries in Rust, or lack thereof. Every single library in rust is half-baked. Axum doesn't even have a home page and its docs are literally a readme file in cargo, how's that gonna compare to express or dotnet with serious industry backing? If you write an entire codebase in Axum and then the 1 dev maintaining it decides to quit due to no funding then what do you do? No GUI framework is as stable as something like Qt or GTK, literally every rust project has like 1 dev maintaining it in his free time and has "expect breaking changes" in the readme. Nothing is stable or enterprise ready with a serious team with money backing it.
As for "memory safety", it's a buzzword. Just use a garbage collector. They're invulnerable to memory issues unless you write infinite while loop and suitable for 99% of applications.
"But muh performance, garbage collectors are slow!"
Then use C or C++ if you really need performance. Both of them are way better designed than Rust. In most cases though it's just bikeshedding. We're not in 1997 where we have 10mb of ram to work with, 9/10 times you don't need to put yourself through hell to save a few megabyes of a bundle size of a web app. There are apps with billions of users that run fine on php. Also, any program you write should be extensively tested before release, so you'd catch those memory errors if you aren't being lazy and shipping broken software to the public. So literally, what is the point of Rust?
From the outside looking in, Rust is the most overwhelming proof possible to me that programmers are inheritly hobbists who like tinkering rather than actually making real world apps that solve problems. Because it's a hard language, it's complicated and it's got one frivelous thing it can market "memory safety!", and if you master it you're better than everyone else because you learned something hard, and that's enough for the entire programming space to rank it year after year the greatest language while rewriting minimal c programs in rust quadrupling the memory usage of them. And the thing is, that's fine, the issue I have is people lying and saying Rust is a drop in replacement for js and is the single greatest language ever created, like come on it's not. Its syntax and poor 3rd party library support prove that better than I ever can
"Oh but in rust you learn more about computers/low level concepts, you're just not good at coding"
Who cares? Coding is a tool to get shit done and I think devs forget this way too often, like if one works easier than the other why does learning lower level stuff matter? It's useless knowledge unless you specifically go into a field where you need lower level coding. Typescript is easy, rust is not. Typescript is therefore better at making things quick, the resourse usage doesn't matter to 99% of people and the apps look good and function good.
So at this point I'm seeing very little reason to continue. I shouldn't have to fight a programming language, mostly for issues that are caused by lack of financial backing in 3rd party libraries or badly designed syntax and I'm about to just give up and move on, but I'm in the minority here. Apparently everyone loves dealing with hours and hours of debugging basic problems because it makes you a better programmer, or there's some information I'm just missing. Imo tho think rust devs need to understand there's serious value in actually making things with code, the ergonomics/good clean design of the language, and having serious 3rd party support/widespread usage of libraries. When you're running a company you don't have time to mess around with syntax quirks, you need thinks done, stable and out the door and I just don't see that happening with Rust.
If anyone makes a serious comment/counterargument to any of my claims here I will respond to it.
-
-
I made a TUI soundboard in Rust! (cls)
github.com GitHub - North-West-Wind/cls: Command-Line SoundboardCommand-Line Soundboard. Contribute to North-West-Wind/cls development by creating an account on GitHub.
- tweedegolf.nl Rust is rolling off the Volvo assembly line - Blog - Tweede golf
In my job I get to speak to lots of people about Rust. Some are just starting out, some have barely ever heard of it, and then some people are running Rust silently in production at a very large c ...
-
Getting debugger setup in VSCode
Just started learning Rust today and got Rust installed, got the hello world example compiled and running. I installed
rust-analyzer
andCodeLLDB
extensions in VSCode. Enable thedebug.allowBreakpointsEverywhere
settings to VSCode to be true. Setup a debug configuration in VSCode.However I keep getting errors from
rust-analyzer
when I run the debugger...``` 2024-10-06T22:16:04.808655Z ERROR FetchWorkspaceError: rust-analyzer failed to load workspace: Failed to load the project at /home/john/Documents/Snippets/Rust/Cargo.toml: Failed to read Cargo metadata from Cargo.toml file /home/john/Documents/Snippets/Rust/Cargo.toml, Some(Version { major: 1, minor: 81, patch: 0 }): Failed to run
cd "/home/john/Documents/Snippets/Rust" && RUSTUP_TOOLCHAIN="/home/john/.rustup/toolchains/stable-x86_64-unknown-linux-gnu" "/home/john/.cargo/bin/cargo" "metadata" "--format-version" "1" "--manifest-path" "/home/john/Documents/Snippets/Rust/Cargo.toml" "--filter-platform" "x86_64-unknown-linux-gnu"
:cargo metadata
exited with an error: error: failed to parse manifest at/home/john/Documents/Snippets/Rust/Cargo.toml
Caused by: no targets specified in the manifest either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present ```
I not sure how to fix this.
I would like to get the VSCode debugger to work for launch debugging, attach debugging and launch and attach debugging for rust running inside a docker container. This will be a good setup for getting started I believe.
This is my VSCode debugger configuration...
``` { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "lldb", "request": "launch", "name": "Debug", "program": "${workspaceFolder}/hello-world", "args": [], "cwd": "${workspaceFolder}" } ] }
```
Any help and advice will be most appreciated.
-
kdl 6.0.0-alpha.1 (first version with a KDL v2 implementation)
github.com kdl-rs/CHANGELOG.md at f67e3d2998dcf0d198b4d03be7b23062cab21723 · kdl-org/kdl-rsRust parser for KDL. Contribute to kdl-org/kdl-rs development by creating an account on GitHub.
-
rust_analyzer takes forever to load;
cargo check
is instant.I was using Iced as a dependency, but wanted to tweak its source code for some reason, so I jumped into the folder where cargo downloads dependencies, and went into iced_wgpu 13.5 (I think that's the version).
I could make a change, then run
cargo clean -p iced_wgpu && cargo check
in my other project for instant feedback, yet it took rust_analyzer at least 5 whole minutes to stop hallucinating.
Can I disable some functionality of
rust_analyzer
? I only use it for jump-to-definition, linting and syntax highlighting; I don't even use autocomplete.Setup:
-
Desktop that thermally throttles only when both the IGPU and the CPU are under full load, and is cool otherwise.
-
CPU: Intel I5-7500
-
RAM: 8 GiB DDR-4
-
Editor: NVIM v0.11.0-dev | Build type: RelWithDebInfo | LuaJIT 2.1.0-beta3 (I had the same issue with other versions as well).
TLDR
What can I disable in rust_analyzer to boost performance while maintaining jump-to-definition, linting and syntax-highlighting, or what can I do to boost rust_analyzer for big projects in general?
-
-
Do people use Cargo?
I really like the idea of a package/dependency manager. It just seems that when ever I am reading a tutorial and they want to import something that is not standard they say write this in to your TOMOL not cargo install it. Like when reading python docs they all say to use pip or something. Sorry it just seems that Cargo is somewhat overlooked or is it just my perception?
- blog.rust-lang.org This Development-cycle in Cargo: 1.82 | Inside Rust Blog
Want to follow along with Rust development? Curious how you might get involved? Take a look!
- brevzin.github.io Code Generation in Rust vs C++26
One of the things I like to do is compare how different languages solve the same problem — especially when they end up having very different approaches. It’s always educational. In this case, a bunch of us have been working hard on trying to get reflection — a really transformative language feature ...
This is a blog post that really is about C++, but with a look at how Rust does things. So, this is an interesting C++/Rust comparison for once.
- github.com GitHub - RReverser/serdebug: Serde-based replacement for #[derive(Debug)]
Serde-based replacement for #[derive(Debug)]. Contribute to RReverser/serdebug development by creating an account on GitHub.
Last week I basically duplicated the serialization code to provide better debug output.... today, I see this pass in my Mastodon feed. 😀 Well... what are the odds... most likely close to 100% according to how the universe seems to operate.
-
Kellnr v5.2.6 released
kellnr.io Kellnr: The private Rust Crate RegistryKellnr is a private Crate registry for Rust written in Rust to self-host or run in the cloud.
Kellnr, the crate registry for Rust got an update. The latest version contains bug fixes and dependency updates. If you are interested in hosting private crates that must not be on crates.io, check it out.
-
What are you working on this week? (Sep. 29, 2024)
Hi rustaceans! What are you working on this week? Did you discover something new, you want to share?
- sabrinajewson.org “Truly Hygienic” Let Statements in Rust
Remon is a responsible library developer. She cares about stability, flexibility and correctness, using whichever tools are presently accessible to achieve those goals. Her authored libraries feature automated testing and extensive documentation; she allots design decisions rationale; she knows her ...
A short post on how variable names can leak out of macros if there is a name collision with a constant. I thought this was a delightful read!
- thehackernews.com Google's Shift to Rust Programming Cuts Android Memory Vulnerabilities by 52%
Google's shift to Rust for Android has cut memory vulnerabilities by 52%, highlighting the benefits of safe coding.
- blog.rust-lang.org Return type notation MVP: Call for testing! | Inside Rust Blog
Want to follow along with Rust development? Curious how you might get involved? Take a look!
-
Gitoxide August 2024 Progress report
github.com [August 2024] · Byron gitoxide · Discussion #1602As hoped, after last months dip my total time worked went back to 156h, up from 128, with 57h spent on open source maintenance (up from 39), and 48 of which went directly into Gitoxide (up from 32)...
-
Need some advice about creating game overlay in Linux
Hi. I've been learning Rust for a while, and I want to take on an actual project now to learn even more. I need to be pointed in the right direction for one aspect of the affair, and I hope someone here can help me.
I want to create a deck tracker for Hearthstone that runs natively in Linux. This is, on the back end, a fairly simple matter of parsing a constantly updated file that tracks everything that happens in the game. On the front end, however, I want to create a window that sits on top of the fullscreen Hearthstone window and shows me stuff. The "stuff" doesn't have to be images or anything fancy, I'll take whatever I can get, but I don't know how to get started on this part.
So the task is as follows: Create an overlay on top of the fullscreen Hearthstone client, preferably under Wayland, and update it constantly with new information about cards drawn, cards left in deck, that sort of thing.
How do I tackle this problem? Are there any crates that'll let me create such a window and render stuff to it? How would you approach the problem?
Thanks in advance.
-
Release 0.13.0 · iced-rs/iced · GitHub
github.com Release 0.13.0 · iced-rs/icedAdded Introductory chapters to the official guide book. Pocket guide in API reference. Program API. #2331 Task API. #2463 Daemon API and Shell Runtime Unification. #2469 rich_text and markdown wid...
-
I made a tool to aggregate git blame stats across any repo
github.com GitHub - martinn/repoblame: Aggregate git blame stats across any git repository. Find out top contributors by Lines of Code.Aggregate git blame stats across any git repository. Find out top contributors by Lines of Code. - martinn/repoblame
I've always been curious about this. If I were to take a snapshot of a git repo at a particular point in time, who would be the top contributors by active lines of code? And then, what type of files have they contributed the most? So I built this little tool.
I've been wanting to learn rust for quite some time now and this was one of my first projects in it. It was a lot of fun!
It uses
git
under the hood to obtain the information and it's nothing fancy, but keen to hear what you think. -
Don't ship your dev environment. Use Multi-Stage builds
YouTube Video
Click to view this content.
-
textdistance.rs, Rust crate with 25+ algorithms for comparing strings. Now with no_std support!
github.com GitHub - life4/textdistance.rs: 🦀📏 Rust library to compare strings (or any sequences). 25+ algorithms, pure Rust, common interface, Unicode support.🦀📏 Rust library to compare strings (or any sequences). 25+ algorithms, pure Rust, common interface, Unicode support. - life4/textdistance.rs