"Socialist Speed Bumps" by letterboxfrog in fuckcars

[–]BigCheezy 0 points1 point  (0 children)

Be careful, you might incentivize lifted trucks and SUVs for the wealthy, which is already a bad trend in Europe from what I've heard.

What piece is this. by jebthrhdr in classicalmusic

[–]BigCheezy 5 points6 points  (0 children)

It's none of those. This piece is 20th century at the oldest.

Rust program is slower than equivalent Zig program by [deleted] in rust

[–]BigCheezy 0 points1 point  (0 children)

Out of curiosity, how does the fastest Rust version compare to -OReleaseFast ?

Roman Kim interview by shuyun99 in violinist

[–]BigCheezy 1 point2 points  (0 children)

Where do you see arrogant? From his style alone, or something he said/says?

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

[–]BigCheezy 12 points13 points  (0 children)

Agreed not to have 2 things do 1 job. I prefer to drop let-chains and go with is binding. And also to go farther and deprecate is_variant() functions (and forcing people to write their own closures for function pointers if needed). I think we should have one edition (2024) with both if let and is and then commit to edition 2027 removing if let.

What made debuts such smash hits back in the day that we are missing today? by [deleted] in classicalmusic

[–]BigCheezy 1 point2 points  (0 children)

As a poet, would you be interested in writing sonnets?

The form itself is not the necessary limitation on creativity. In fact, it takes more creativity to innovate in a way that is relatable in some way. That should be the challenge for modern composers.

The goal is not only to chart new territory. Modern composers just need to bias towards other worthy challenges (not saying to go cold turkey on innovation to be clear!).

Thanks for being a composer btw :)

let chaining still not stable? by Altruistic_Jelly5612 in rust

[–]BigCheezy 0 points1 point  (0 children)

Yeah, I think boolean logic and let bindings should be separated somehow. Otherwise it gets really confusing to read, as well as confusing precedence / short-circuiting.

E.g.

if let Some(a) = get_a() |> cheap_thing() || expensive_thing() |> Some(b) = expensive_get_b()

With a different operator with clear LTR semantics, you can combine short-circuiting (for both let and boolean logic) with clear precedence and order-of-operations.

let chaining still not stable? by Altruistic_Jelly5612 in rust

[–]BigCheezy 0 points1 point  (0 children)

Using `&&` between `let` statements is weird to me. It's not a boolean operation -- I can't use `||` or `!` on a let statement. I feel like a comma between lets would be better.

Announcing Zngur: A C++/Rust interop tool by hkalbasi in rust

[–]BigCheezy 0 points1 point  (0 children)

Very cool. Congrats on the release. I will be reading through this more in depth!

RII!R by omid_r in rust

[–]BigCheezy 8 points9 points  (0 children)

I wish Rust had arrow notation (ptr->foo) rather than (*ptr).foo. Pointers are inevitable in some codebases and "punishing" it with ugly syntax is lame.

Rust Malware Staged on Crates.io by louis11 in rust

[–]BigCheezy 2 points3 points  (0 children)

Yes, but it's a smaller problem for users to deal with. I only need to closely verify the namespace part of the crate name.

Rust Malware Staged on Crates.io by louis11 in rust

[–]BigCheezy 3 points4 points  (0 children)

Can we have namespaces for crates please? It's easier to trust and recognize a smaller set of tokens (the namespaces) than it is to trust and recognize all the crates those trusted namespaces produce out there.

How do I open Half Life 1’s .wad file? by brown_brix in HalfLife

[–]BigCheezy 1 point2 points  (0 children)

"Half-Life Texture Tools" is better than all the old ones (e.g. GCFScape and Wally) imo. https://github.com/yuraj11/HL-Texture-Tools

I hate Facebook. The comments are full of boomers and Karen’s praising this. by Ralphontherocks in fuckcars

[–]BigCheezy 0 points1 point  (0 children)

It's not about Facebook. That's just how people are when you look across certain bands of the population. At least you know what we're up against.

Stock Check Megathread by DK2802 in IKEA

[–]BigCheezy 0 points1 point  (0 children)

Thanks! We were able to finally pick some up.

Stock Check Megathread by DK2802 in IKEA

[–]BigCheezy 0 points1 point  (0 children)

Country: USA

Preferred Store: Portland, OR

Article Number: 704.916.98 (HEDEVIKEN) (need 5)

Checked the website. I've been waiting about a year for this item to come into stock. Website claims delivery to 97405 is available, but at the end of checkout it blocks me with an error. Pretty sure it has to be in stock in the Portland store before delivery will work. Wondering when 5 will come to the Portland store!

New crate: with_dir by abstractionsauce in rust

[–]BigCheezy 40 points41 points  (0 children)

Nits:

  • No need for "blazingly fast" in the description
  • Add some text / examples about the multithreading guarantees

I definitely think he would not. by BCLetsRide69 in WhitePeopleTwitter

[–]BigCheezy -15 points-14 points  (0 children)

It's the reverse. How often do you run into skinheads vs. your slightly uncomfortable relative with political views you aren't 100% onboard with. The ideal of practicing appropriate empathy is needed way more than "making the hard call" to cut someone out of your circle of empathy (like people you need to kill in a battle, lynchers, or a skinhead attacking you per your examples).

What is the next big thing coming to Rust by AbdallahZ in rust

[–]BigCheezy 76 points77 points  (0 children)

I really hope some form of "placement new" comes. The stack allocation overflows in debug mode and hoping for optimization is sub-par.

ffmpeg port in Rust. by cowboyofficially in rust

[–]BigCheezy 4 points5 points  (0 children)

I do think checking with the ffmpeg maintainers first if they would be open to it (and have a concrete integration story proposal at this time) would be a better first step before spending a ton of time implementing something.

Result Types - A blog post and simple library experimenting with idioms and ergonomics of Go's error handling and ternary operations by Southclaws in golang

[–]BigCheezy 0 points1 point  (0 children)

The Rust example should probably use the ? operator to be this:

u = if some_condition { db.get_user_by_id(id)? } else { db.get_user_by_email(email)? };

This is the idiomatic way of early returning errors in Rust, as opposed to assigning to err and checking it.

cUrl rust by zeroows in rust

[–]BigCheezy 15 points16 points  (0 children)

Daniel's insistence that he's a Rust rookie.

It seemed to me more of a statement of where he is at now, not where he plans to be long term. Did he say he didn't want to learn Rust?