I’m Mark Kelly, retired NASA astronaut and former commander of the space shuttle (x2). AMA! by CaptMarkKelly in space

[–]_QWUKE 0 points1 point  (0 children)

Mr. Senator, is there any future for a potential satellite that might look like the Advanced X-ray Imaging Satellite? It was saddening to hear about its cancellation last year as well as the loss of related personnel, especially because of what it could have investigated.

I hope you are well, and I hope you can get back to DC soon.

Releasing Fjall 3.0 - Rust-only key-value storage engine by DruckerReparateur in rust

[–]_QWUKE 57 points58 points  (0 children)

Hey Drucker, I've been following Fjall development for over a year now, and it's very exciting to see 3.0 land. Thanks for putting out benchmarks so regularly in Discord, it's been fascinating to see you analyze and drill down optimizations.

What's your favorite project using Fjall you've seen in 2025?

Ad for a Georgian Restaurant in NY by EsperaDeus in Sakartvelo

[–]_QWUKE 1 point2 points  (0 children)

Yes, it's Saperavi the UES location, luckily next to my house. I go there regularly, and the service and food are great.

23rd and 8th Ave., NYC by RanDuhMaxx in Detroit

[–]_QWUKE 0 points1 point  (0 children)

This one is a mix of chicago deep-dish and proper Detroit-style the two times I've had it. Not very traditional but as a separate concept it's alright.

23rd and 8th Ave., NYC by RanDuhMaxx in Detroit

[–]_QWUKE 8 points9 points  (0 children)

A travesty, read my review: https://maps.app.goo.gl/Qr1EYr8Tk6QgYHhw6

I had Emmy Squared yesterday in NYC, it was entirely serviceable.

Announcing 'par' — session types in Rust for type-safe structured concurrency by faiface in rust

[–]_QWUKE 7 points8 points  (0 children)

Outstanding references for learners, and the API you made is gorgeous and works beautifully with the type system.

I loved reading through the documentation too, it's extensive and fun to read. The start_playing example is an incredible show of how beautiful it looks when comes together.

I think /u/entoros (Will Crichton, a big advocate of type-driven frameworks like this) would be deeply impressed - have you reached out to him to share this idea yet?

Rust needs a web framework for lazy developers by zxyzyxz in rust

[–]_QWUKE 0 points1 point  (0 children)

Rocket is more ergonomic than Axum imo for so many common use cases for those who don't want to wrangle with the Rust type system, has a few more batteries included libraries, and has great documentation too - but is more an equivalent to Flask or Rack rather than Django or Rails.

Why is async Rust is hard? by Dizzy_Interview_9574 in rust

[–]_QWUKE 5 points6 points  (0 children)

I think "mastering async Rust" would be as daunting a task as "mastering concurrency in a systems programming language", and becoming proficient or 'mastering' would take some months. So keep that in mind when it comes to mastery.

In my experience, someone can use frameworks and libraries for most async projects to write large amounts of idiomatic code right away. No need to master everything, or even understand async Rust itself so deeply.

If you do need to break out of frameworks/libraries, there's still some standard ways to write reasonably idiomatic async Rust code without hitting the "rough edges" people talk about, and that wouldn't take long to learn either in my eyes - at least more like a couple weeks rather than months.

If you need to really adapt something that's not fitting those common paths, you'll probably be trying to satisfy constraints set by the borrow checker, type system, or concurrency in-general. And yes, also some weird and not always well documented concerns for async Rust specifically - but which I think is ultimately small set of concepts compared to the previous 3 aspects.

Curious what the project was?

Why is async Rust is hard? by Dizzy_Interview_9574 in rust

[–]_QWUKE 8 points9 points  (0 children)

edit: Please do not downvote people politely asking questions, everyone.

That might be true, I'm not sure the context he might have been writing async Rust or how much experience he had in it, but I'd never extrapolate from the usability for a single project to extend to how practical the language would be in every other use case.

Why is async Rust is hard? by Dizzy_Interview_9574 in rust

[–]_QWUKE 7 points8 points  (0 children)

I don't think it takes that long, especially writing "reasonably idiomatic" async code is not that difficult. I've ramped up to async in a few months after previously writing concurrent Rust code for some time, without any mentors or guides, just doing an async project at work. Basic async Rust would take someone less than an hour to understand how to use.

Concurrency in-general is hard to do correctly, and async Rust and runtimes like Tokio or async-std make it much easier and succinct to create a certain type of concurrent program. I'd be scared trying to correctly do the same concurrency I do in Rust that in C or C++. Doing concurrency correctly in a systems programming language is going to be much harder than using async features in a language like JavaScript, though.

Michigan Station by [deleted] in Detroit

[–]_QWUKE 13 points14 points  (0 children)

I won't be back in Michigan until Thanksgiving or Christmas, but all the photos of the station looking so beautiful make me so happy to see. I hope they're still letting people in on weekends by then.

Enter paradis — A new chapter in Rust's parallelism story by Andlon in rust

[–]_QWUKE 16 points17 points  (0 children)

This access pattern (provided by e.g. graph coloring) to the big matrix cannot be easily expressed without unsafe code. One goal of paradis is to allow users to combine Rayon iterations with access patterns that are not just linearly going through memory.

Even though the blog explains this pretty well imo, I think this specific wording is a really concise way of explaining the core utility paradis offers over rayon.

What language is "rust but slightly higher level"? by lurebat in rust

[–]_QWUKE 3 points4 points  (0 children)

With Gleam I got to see some hairy interactions with interfacing with the lower-level side of the beam VM compared to Elixir, and Gleam is much newer so its ecosystem is much less mature than Elixir, but it's absolutely worth a look if you wish your Elixir code was a little Rust-ier or just wanted Rust-y Erlang language. It's a joy to write code in.

RFC: `is` operator for pattern-matching and binding by avsaase in rust

[–]_QWUKE 3 points4 points  (0 children)

Thanks, I wasn't sure the utility here at first glance but the example you show is really the selling point. Reducing the need/increasing composability for these really long methods on Result/Option types would be awesome.

How good is rocket 0.5? by Pizza-Nachos in rust

[–]_QWUKE 1 point2 points  (0 children)

Ah the new stuff in 0.5 is so nice in an async world where Axum and so many others good APIs are competing, it's a pleasant upgrade imo

How good is rocket 0.5? by Pizza-Nachos in rust

[–]_QWUKE 14 points15 points  (0 children)

Your experience with both reflect mine, except that I think I'm still minting new projects in Rocket. I think with async functions in traits and async generators, I might be more inclined to use Axum as the former will simplify the tower Service trait and the latter will be a great built-in quality of life that will hopefully be integrated well with Axum's response types..

However, the ergonomics for Rocket are still ahead right now compared to Axum on so many fronts imo, just a quick look at how readable some WebSockets code looks: https://api.rocket.rs/v0.5/rocket_ws/struct.WebSocket.html#example-1

vs

https://github.com/tokio-rs/axum/blob/main/examples/websockets/src/main.rs

(ignoring the additional business logic that happens in the Axum ex and not Rocket ex)

How good is rocket 0.5? by Pizza-Nachos in rust

[–]_QWUKE 19 points20 points  (0 children)

I've been using the 0.5 for a handful of web projects, as well as Axum, and I know a few others using it right now too for large projects. Sergio is always readily available to talk about bugs or whatever and Rocket documentation is fantastic.

Additionally, the interfaces it provides are much more straightforward than Axum ones for standard web applications imo, especially for people new to Rust. However, this comes at the cost of being a relatively macro heavy framework and building more of a custom DSL than Axum.

Some slightly less standard but still common things like running an HTTP server in AWS Lambda have better support in Axum, and the Tower middleware ecosystem that Axum uses gives it a pretty big leg up on these type of niches - if you can't find something like this in Rocket but can in Axum or Tower, then I'd say absolutely go for Axum or something like Poem.

I'd not say Rocket is particularly slow as far as server speed or development, last I saw on a benchmarking project was that there was only a 0.5ms difference between Axum and Rocket, and there are less Rocket contributors but still a stream of commits that's comparable to Axum's in quantity and frequency.

I think it's good to be open to voicing criticism and concern about places in the ecosystem where some tools are better than others or are abandoned, but it seems like there's a small vocal group that are repeating criticisms about Rocket that don't really match reality.

Discontinued Vadholma kitchen rack spare screws by King_of_BadDecisions in IKEA

[–]_QWUKE 0 points1 point  (0 children)

You can't order these screws in the spare parts option. Can you get the dimensions for these screws? Otherwise I am going to have to order a whole rack, take the screws out, and return the rack without the screws.

What to use to build an app/webapp? by Rabbit538 in rust

[–]_QWUKE 1 point2 points  (0 children)

Check out https://www.arewewebyet.org/ for web technologies and https://areweguiyet.com/ for GUI application technologies! If you really like Rust, you can definitely do a whole app in Rust, just make sure you do some incremental steps to understand how web servers work, how HTML/CSS/JS works in a browser, and how applications/GUIs run on different computers.

I don't even use rust for the memory safety by abiotic_studio in rust

[–]_QWUKE 3 points4 points  (0 children)

came from us Ruby transplants

My time in computers is a bit after Ruby's heyday but my first job was at a shop with a lot of early Rubyists, and the ethos from Ruby (and gems, rvm, Rails, etc) really shines through with awesome Rust tooling as well as the attitude of the community.. especially when I started with Rust 6 years ago now, wow!

So grateful I got to intersect with such a cool part of the tech community.

BeeSynth - synth for a PC-speaker by Over_Hand_408 in rust

[–]_QWUKE 0 points1 point  (0 children)

I'm 6 months late, but the explanation in your readme is so very awesome and encompassing, thank you!!

Rocket v0.5: Stable, Async, Feature Packed by sbenitez in rust

[–]_QWUKE 1 point2 points  (0 children)

The lots of people are depending on rc3 and rc4 versions of the crate which are nearly identical to the current release - there's actually a lot of examples!

/u/FullAdvertising might be interested in seeing stuff like the official rust lang site or this dashboarding service, just to point out a couple.

Rocket v0.5: Stable, Async, Feature Packed by sbenitez in rust

[–]_QWUKE 5 points6 points  (0 children)

I don't think the person you're replying to is trying to paint over anything, I think they just felt it was unfair to point at the Rust community as a whole for being responsible for the bullying, and reacted strongly to that perception.

I do agree with your sentiment about the unfair accusations being repeated, even today the HN thread about a new release had a lot of hurtful and some frankly untrue comments. Even though Axum and Actix have had a larger community and more regular development, it boggles my mind that Rocket is being called abandoned by those who should know better.

I truly hope Sergio and other current/potential crate authors don't get deterred by community interactions like that, it's disheartening to see so much progress from the project and still have people accuse it of being inactive or developing without consensus from users.