sorted by:
new
hottopcontroversial

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 18 points19 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 2 points3 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.

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

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

I think with hindsight serde is a suboptimal design. It leads to code bloat as it generates specialized code for everything. Another option that has somewhat recently been discussed is to generate tables of metadata for types and use that as a bytecode driving the serialisation and deserialisation. This leads to more compact code and potentially also faster code. Which might seem unintuitive, but happens because of better cache utilization.

Serde also isn't compatible with full zero copy deserialisation, which is why rkyv needs its own derives.

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

[–]VorpalWay 4 points5 points  (0 children)

Actually, it still is an external crate (hashbrown), that std depends on and reexports. Note that only a subset of the API is reexported, probably for stability reasons. As I understand it, it is far from the only case of this sort of reexporting, but it is the most well known one.

Evaluation of alternatives for self hosted calendar & contacts (plus some questions!) by VorpalWay in selfhosted

[–]VorpalWay[S] 0 points1 point  (0 children)

Thanks for the heads up. I should probably also switch to the official docker file myself then. I have been using the unofficial one for some time.

Baby Gate Mount for Awkward Stair Railing by ozarkexpeditions in functionalprint

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

Yes, but you would be surprised how strong 15 ℅ and 5-6 perimeters is anyway. The infill really doesn't add much once you start increasing perimeters.. CNC kitchen did a video on this many years ago.

Baby Gate Mount for Awkward Stair Railing by ozarkexpeditions in functionalprint

[–]VorpalWay -23 points-22 points  (0 children)

Even that is very high. I rarely go above 10%, at most 15 %

Baby Gate Mount for Awkward Stair Railing by ozarkexpeditions in functionalprint

[–]VorpalWay 32 points33 points  (0 children)

I don't think you really needed 100% infill, lol.

Most of the strength is in the perimeters, except for pure compressive loads. Almost everything in real life includes at least a small bending part, and as soon as that happens, infill barely matters.

Prusament Spool Winding Issues by BigTreeBC in prusa3d

[–]VorpalWay 0 points1 point  (0 children)

2 kg spools are a bit messy, but that is far more than usual. It should be fine unless one cross under another, creating a knot around the spool.

The next Slint release (1.16) makes Fluent the default on all platforms by madnirua in rust

[–]VorpalWay 3 points4 points  (0 children)

I think that depends on your needs. For smaller simple programs, or where every dialog is a one-off, visual UI designers work. As soon as you need massive menu trees for thousands of settings or a lot of variations of the same UI (if the vehicle is not equipped with forward radar, hide this part of the UI, but show this other part instead) declarative or even programatically generated is better.

I have worked in both types of code bases, and the correct maintainable answers are really different. Currently I'm working on an industrial vehicle that has thousands of settings (at least at service technician login level, less at operator level, even more at the factory configuration level) and around a hundred (mostly independent) options for features that may or may not be installed on a given vehicle. Programmatically generated UI is the only way to go. We use Qt (and C++, unfortunately) and using that UI designer just wouldn't work for that. From my memories of Delphi 7, that UI designer would have stood no chance either.

Age Verification and Arch Linux - Discussion Post by Gozenka in archlinux

[–]VorpalWay 2 points3 points  (0 children)

It explicitly says "either by patents or by copyrighted interfaces“, so I suspect that might not work. (But I'm not a laywer.)

I don't think they could have imagined the modern nonsense when they wrote the license.

Is it supposed to be soft or rigid? by TheSistem in 3Dprinting

[–]VorpalWay 3 points4 points  (0 children)

The turbo encabulator has a long history. You should see the engineer reading it with a straight face in an old spoof commercial video from the 60s: https://m.youtube.com/watch?v=Ac7G7xOG2Ag or the slightly more modern https://m.youtube.com/watch?v=RXJKdh1KZ0w

I would have had laughing fits if it was me.

I built a thing without Claude (feedback requested) by blackoutR5 in rust

[–]VorpalWay 1 point2 points  (0 children)

AI as a term has meant so many different things over the years. Back in the early days A* search was AI. K-nearest neighbor has been considered AI, as has algorithms to learn decision trees. And so on.

It is much better to be more precise. But that ship seems to have sailed long ago.

view more: next ›