unrealhoang

claim your password to be some derivative of the duress PIN, for example: 1234 is password reminder for 2444 (one 2 three 4), the device is erased anyway.

This is awesome, is there a way to render the graphics/chart in svg so that we can implement something like hover & popup (with data information)?

isn't this https://clojure.org/reference/transducers?

What if one day they do? Or appears to be, in the way that you couldn't distinguish? Will you update your priors?

It’s a good one, if you can still write functionally and same algorithmic complexity then it should not matter if you know strrev or not.

So not being able to write fizzbuzz is nowhere close to me.

And they can have an alternate screen outside the FoV of the second camera.

Or to automatically write command bitching about it.

Maybe not lootboxes but most certainly battlepass.

a bit tangent question: the communication between Python & Rust, could the pyo3 ser/de of Python objects be better than MsgPack?

it will be much less power-efficient, when jailbreak you could schedule the kindle to wake up once per 15/30/60 minutes to fetch the new data, set it as screensaver and then go back to sleep.

There’s split_at_mut to avoid writing unsafe yourself in this case.

> My groceries are cheaper if I walk out of the store without paying for them too. Who's going to stop me?

If you can consistently do that, then it IS the correct thing to do.

uv made that choice and users use them, is there an objective truth of what is “correct” to do version parsing?

Wow, now no more discussion and an accuse of bot? I’m flattered.

Also you are doing tech, be specific, what is much shallower or hollow?

All of `Vec` is much smaller than all of the place using Vec. IIRC, Vec is around 3k LoC. And for even low level code like Oxide & Android core, they are observed less than 4% of their code is inside or related to unsafe, that’s a massive improvement.

Yes, Rust is not new in term of allow building hard to misuse abstraction, it’s just allow abstraction over memory safety without relying on GC or runtime checks. Rust achieve this by adding capability to enforce shared XOR mutability with its borrowck which C++ couldn’t.

That would be the unsoundness of `Vec` itself, but if the abstraction of `Vec` is sound, there would be no way to use `Vec` outside of `unsafe` that can cause memory unsafety.

The point coming back to abstraction and responsibility, in Rust, you can build abstraction that is sound and guarantee memory safety from there. There can be soundness bug inside your abstraction, but it will be a massively smaller surface for auditing and expert required to write such abstraction. Also, when soundness bug appears, the responsibility is solely on the abstraction writer, not the user.

Whereas in C, without those safe abstraction, the surface of doing thing right to avoid memory safety issue is your entire codebase, and responsibility of "holding the knife correctly" is on the user.

from TFA, the main advantage would be for embedded (as a library) use case, FFI with Go is harder.

> logic bugs outside "unsafe" can cause bugs unsafe.

This is the wrong understanding of Rust's unsafety encapsulation. For example, no logic bug outside of `unsafe` can cause undefined behavior of Rust std's `Vec` abstraction, which is using underlying unsafe to build.

The point that "because unsafe is used so the entire Rust program is also unsafe" is a real major myth. It's as absurd as saying "because Java runtime using unsafe underlying to build so Java is also unsafe".

The get started section seems to be broken or missing content.

No but this time RFK is saying that, before it was devil Dems saying (Michelle Obama), so people had to eat trash food and be lazy out of spite.

Memory safety has a specific meaning, and panic isn’t it.

C++ can have UB, compilable non-unsafe Rust can’t, that’s what static analysis of memory safety is.

Main point here is you don’t know (and refuse to learn) new knowledge.

A panic is memory-safe, so static checking of memory safety holds. Perhaps you should understand your own claims.

Without a borrowck, inside your mutable block, another variable can reference to the mutable version of your x or items, and be mutated outside of that block.

> no company anywhere would just shrug something like this off as "the cost of doing business".

Fox News did, they lost 10 times as much money and is more successful than ever BECAUSE they did it, so for them it's just "the cost of doing business" or even an "investment".

People are already appreciate the accessibility to low level native libraries like duckdb, sqlite, imagemagick, ffmpeg… allowed by wasm. Or high performance games/canvas based applications (figma).

But CRUD developers don’t know/care about those, I guess.

And you disregard user experience and other developer experience with your own custom parsing code. Acts as if there's no trade-off whatsoever in your own decision and my way is holier than thou in engineering is beyond sad.

no yaml programming please :(

> everyone is now bankrupt

A good reason enough for a lot of people, no?

Yes, serde is just a struct to visitors codegen infrastructure that you can rely on to do anything. https://serde.rs/data-model.html

There’re fundamental libraries that can be used on the web because of wasm: imagemagick, ffmpeg, opencv, duckdb, sqlite, figma’s render engine...

Just because 95% of web apps are crud DOMs doesn’t mean such technology is not important.