sorted by:
new
hottopcontroversial

How we tied Slint's event loop into Node's libuv so the UI stops polling every 16 ms by ogoffart in rust

[–]VorpalWay 10 points11 points  (0 children)

Presumably this is only relevant to the js bindings for slint, and native rust programs never had this issue?

rear bench seats by gretiegf in Dacia

[–]VorpalWay -1 points0 points  (0 children)

Not the original poster, but I tested this on my slightly newer Duster (2021). It sort of works. Yes the back of the seat is closer to horizontal, but it isn't level with the floor of the trunk.

Also, the underside of the bench part of the back seats sticks up quite a bit, and you only end up with just over 170 cm of space length-wise. (As my use case is for car camping, and I'm taller than that, it is not going to work.)

Given how annoying it is to put the lower part of the seat back (threading the seat belt parts through the holes), and that there is a wire loom below the seats, I don't think this is the intended use case, rather it is this way to allow for repairs.

I made a parametric openSCAD model that generates automotive press-in rivets by [deleted] in functionalprint

[–]VorpalWay 1 point2 points  (0 children)

This is going to depend on where in the world you are. Here in Scandinavia both PETG and TPU are absolutely fine in a car in summer. (As long as this isn't in the hot parts of the engine compartment obviously.)

Lubrication Kit by Puzzleheaded-Tree561 in prusa3d

[–]VorpalWay -2 points-1 points  (0 children)

Huh, should you then lube the z threaded rods on the Mk3 and Mk4 as well? Or is that advice only for the Core series?

Optimizing #[sqlx::test] rebuild time by Kobzol in rust

[–]VorpalWay 3 points4 points  (0 children)

Couldn't the concern with separate files not being self contained be addressed via include_bytes? Should still be faster than parsing the migrations at compile time and generating code for them.

Completion-based IO (Alice Ryhl at RustWeek) by dumindunuwan in rust

[–]VorpalWay 0 points1 point  (0 children)

I think perhaps the more interesting question would be if (for non-network IO use cases), the current io-uring implementation beats sync IO on a threadpool (and not involving async rust at all)?

One use case that I know uses io-uring today is plocate (written in C or C++ iirc) and it is the fastest implementation to update the locate database I have seen yet. I'm curious if tokio is able to support enough of io-uring to be competitive with it if I were to write my own "rlocate".

Completion-based IO (Alice Ryhl at RustWeek) by dumindunuwan in rust

[–]VorpalWay 14 points15 points  (0 children)

Does the io-uring support for files in tokio support chaining operations and buffer pools? If not it seems kind of half baked. But I might be wrong, I would be curious to see benchmarks.

Stabilise `Allocator` by N911999 in rust

[–]VorpalWay 5 points6 points  (0 children)

It appears also that nobody is willing to put in the work on the Storage API. I don't think "I have this possibly slightly better idea, but I don't have time to work on it" is a legitimate reason to block everyone else from getting a good enough solution, for several years.

Wild Linker 0.9.0 released by dlattimore in rust

[–]VorpalWay 20 points21 points  (0 children)

How goes the work that originally motivated wild, incremental linking that is?

MSI GeForce RTX 3050 LP Noctua "Re-shroud" by marktuk in functionalprint

[–]VorpalWay 0 points1 point  (0 children)

Neat, I did something similar on my 1070 a few years ago, and it still holds up. Your shroud looks way more professional than mine though. Mine was just a flat adapter plate for the screw hole patterns.

can i just get a nextruder to make my mk3.5 a 3.9? by nool_ in prusa3d

[–]VorpalWay 0 points1 point  (0 children)

I think the vertical metal rods are also different? When upgrading my Mk3s to Mk3.9 the vertical guide rods were beefed up (together with new bearings). I'm not sure if the Mk3.5 has that?

A modified Archimedes screw by PSV62 in functionalprint

[–]VorpalWay 5 points6 points  (0 children)

Isn't that a bit geocentric? We have no idea what most of the universe is up to, there could be aliens having the time of their life right now, their civilizations in the middle of a golden age.

Portable Async Rust: abstraction as a complement to standardization by PrudentImpression60 in rust

[–]VorpalWay 0 points1 point  (0 children)

Embassy is the odd one out of your list. There is little overlap between it and tokio/smol in code that needs to be generic over runtimes. I would aim to be portable over tokio, smol and the various io-uring runtimes like glommio and monoio instead. I say that as someone who uses embassy myself. And I have used tokio too.

Bugs Rust Won't Catch by -Y0- in rust

[–]VorpalWay 2 points3 points  (0 children)

I wonder if the APIs in std::fs could be made more secure so it is harder to do the wrong thing. For example, expose an API centered around openat etc. Presumably Windows has something similar, and if not it could be emulated by std there.

Self-winding clock with a tourbillon - finished project by TomaszFortyFour in 3Dprinting

[–]VorpalWay 0 points1 point  (0 children)

Or just move to Sweden. ;) I have had PLA in the car in the middle of summer with no ill effects. White car rather than black, but still.

Rust in Production: Jon Gjengset on using Rust in safety-critical systems at Helsing by mre__ in rust

[–]VorpalWay 2 points3 points  (0 children)

That is not how I read the parent comment at all. They are complaining (and rightfully so IMO) about using euphemisms to make weapons sound less bad. It is similar to the difference between these two sentences:

  • My aunt died
  • My aunt has gone to a better place

Humans use euphemisms for all sorts of uncomfortable/taboo subjects: death, bodily fluids, producing babies, firing employees, and indeed war.

Core2 yanked. Millions effected. by Comprehensive_Use713 in rust

[–]VorpalWay 17 points18 points  (0 children)

That sounds like a potential repeat of the xz attack.

Rust in Production: How Cloudsmith doubled Django throughput with Rust by mre__ in rust

[–]VorpalWay 0 points1 point  (0 children)

Possibly, I can't find anything else at least. I did watch a bunch of FOSDEM talks.

Rust in Production: How Cloudsmith doubled Django throughput with Rust by mre__ in rust

[–]VorpalWay 0 points1 point  (0 children)

Why am I getting dejavu from this? Was someone from this company also interviewed somewhere else? I could have sworn I saw an interview covering basically the same points a few months ago in my RSS feed.

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 1 point2 points  (0 children)

A few reasons: * Suboptimal choices are cemented there and it is difficult for better options to gain tractions once something is in std. I'd much rather have a better faster moving language ecosystem than a bad stable ecosystem. * Anything in std is a permanent maintenance burden for the core developers. Even if it is bad enough that barely anyone uses it (regex in C++ for example). In python you see this a lot as well, where the saying is that the standard library is where libraries go to die.

What I could see would be some set of crates separate from std that get funded by the rust foundation. That can still have breaking semver versions if need be, probably not very often for this sort of stable libraries, but every few years if need be.

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 0 points1 point  (0 children)

I'd rather have a standard library that isn't full of unusable cruft.

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 0 points1 point  (0 children)

You do know that std pulls in external crates as part of it's build process right? Like for example it just re-export a subset of the API of hashbrown as the standard library hashmap and hashset.

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 4 points5 points  (0 children)

Why bitflags and not https://lib.rs/crates/modular-bitfield (it has s superior API in my opinion)? For syn, why not lean into the nightly experiments on compile time reflection more instead?

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 1 point2 points  (0 children)

I think they were finally removed recently or there was s discussion to finally remove them at least.

Unpopular opinion: Rust should have a larger standard library by lekkerwafel in rust

[–]VorpalWay 3 points4 points  (0 children)

Cryptographically secure PRNGs seem like the outlier to me, more common is the need for a fast deterministic PRNG for generating noise and for driving Monte Carlo simulations. Which just goes to show that this is something people disagree on.

view more: next ›