pornel

34 ms·

571.
by pornel 2y ago
Giving good feedback about Rust<>C bindings requires knowing Rust well. It needs deep technical understanding of Rust's safety requirements, as well as a sense of Rust's idioms and design patterns. C maintainers who don&#x27
572.
by pornel 2y ago
Rust already has several server frameworks that are relatively low-level network plumbing, and leave figuring out everything else to the user. If that's what you like, you can pick and choose from all the existing tools. The Rust&#x27
573.
by pornel 2y ago
It's not hard to just call C. Rust supports C ABI and there's tooling for converting between C headers and Rust interfaces. The challenging part is making a higher-level "safe" Rust API around the C API. Safe in the sens
574.
by pornel 2y ago
At this point it's too early to even worry about correctness, it doesn't work yet. But the years of work put into the existing project to make it robust don't mean the exact same years have to be spent on the reimplementation
575.
by pornel 2y ago
I wonder why timelines aren't implemented as a hybrid gather-scatter choosing strategy depending on account popularity (a combination of fan-out to followers and a lazy fetch of popular followed accounts when follower's timeline i
576.
by pornel 2y ago
Battery-only EVs have a much simpler drive train, and longer-lasting batteries. Hybrids are not simply EV+ICE, they have very different kind of batteries (low-voltage, high C-rate). In a hybrid, you have a battery that is 1/10th of the
577.
by pornel 2y ago
In the UK (and probably most of Europe) there is already regulation requiring new residential parking and garages to have a grid connection installed, to be able to easily add chargers at residents' request (even if they're rentin
578.
by pornel 2y ago
Exclusive access is nice, but not necessary. BEVs used just for city driving need to be charged about once a week, so you just plug in when there's an opportunity. A basic 7kW charger is enough to charge full battery overnight.
579.
by pornel 2y ago
GameBoy Advance had a CPU without cache, but with 32kbit of fast RAM on the chip. That was pretty close to a fully manual cache, and turned out to be a complete waste in practice. It was impractical to share/reuse it like a real cache,
580.
by pornel 2y ago
In more mature implementations a simple "doesn't parse" doesn't cut it. You may want to get specific error codes to know if you should retry the request, or blame the user for bad inputs, or raise an alarm because the AP
581.
by pornel 2y ago
EVs on public roads must still obey the same speed limits and common sense behavior. Having more torque doesn't mean drivers have to slam brakes like on a race track. In normal driving regenerative braking takes away most of the energy
582.
by pornel 2y ago
Who's going to pay for carbon capture? Definitely not the current polluters who benefit from fossil fuel prices that don't include the cost to clean that up. This is like a fossil fuel subsidy from a debt left to someone else to p
583.
by pornel 2y ago
I've said fields, not messages. It can exfiltrate data by copying it between fields of the single message it parses. Imagine a server calling some API and getting `{"secret":"hunter2"}` response that isn't supp
584.
by pornel 2y ago
> towards feeling safe about dependencies Sandboxed is better than unsandboxed, but don't mistake it for being secure. A sandboxed JSON parser can still lie to you about what's been parsed. It can exfiltrate data by copying sec
585.
by pornel 2y ago
The change itself was very reasonable. They only missed the mark on how that change was introduced. They should have waited with it until the next Rust edition, or at least held back a few releases to give users of the one affected packag
586.
by pornel 2y ago
Meaning of this code has not changed since Rust 1.0. It wasn't a language change, nor even anything in the standard library. It's just a hack that the poster wanted to work, and realized it won't work (it never worked). This
587.
by pornel 2y ago
> attempting to design a new programming language without first studying carefully the history of programming Rust's original designer credits these languages as the inspiration: http://venge.net/graydon/talks&#
588.
by pornel 2y ago
Here's the source: https://ec.europa.eu/commission/presscorner/detail/en/ip_25_... • strengthen the EU's generative AI talent pool through education, training, skilling and reskilling activitie
589.
by pornel 2y ago
There was also Cyclone before Rust, and Checked-C in the meantime. The concepts like regions and affine types existed long before Rust, and Rust started out by copying from older languages ( http://venge.net/graydon/talk
590.
by pornel 2y ago
Linus said he's worried that he and core kernel maintainers are getting old, and there may not be enough younger contributors to replace them. There's an implication there that Rust will continue to grow and attract more talent, a
591.
by pornel 2y ago
The Rust project started 15 years ago, and spent a decade growing userbase, library ecosystem, and proving that it's a serious language that's here to stay (which some C maintainers still don't believe). We don't have a
592.
by pornel 2y ago
I agree that 128 bits is on the lower end of "never", but you still need to store trillions of hashes to have a one-in-a-trillion chance to see a collision (and that's already the overall probability, you don't multiply
593.
by pornel 2y ago
Yikes. It's valid to assume "it will never happen" for 128 bits or more (if the hash function isn't broken) since chance of a random collision is astronomically small, but a collision in 64 bits is within realm of possib
594.
by pornel 2y ago
Storing values at the edges of cells makes the math simpler, but unfortunately makes a GPU implementation harder. In this setup one edge update affects two cells, so the cells are no longer trivially independent. It's still possible to
595.
by pornel 2y ago
Nothing in GCC or clang that exists today is anywhere near the level of expressiveness that Rust uses in its APIs (e.g. lifetimebound in [1]). The current problem is not technical, it's maintainers not wanting to even think about anoth
596.
by pornel 2y ago
C doesn't have syntax/typesystem to express ownership, lifetimes and thread safety, but Rust does. Personally I'd love if C was extended to be able define APIs more precisely, but that's not a realistic option at the mom
597.
by pornel 2y ago
In Rust, unsafe (unchecked) C interop is almost automatic. The hard part is in translating C code's high-level safety requirements into Rust APIs that enforce them. I'm talking about requirements that aren't expressed in th
598.
by pornel 2y ago
It's the other way around: there's an existing ratatui library that is pretty nice for making rich terminal UIs, and since ratatui is written in Rust, the easiest way of porting it to the web is through WASM.
599.
by pornel 2y ago
Ollama : llama.cpp :: Dropbox : rsync
600.
by pornel 2y ago
I'd be worried that LLMs are incredibly gullible. A phisher may insert text for an LLM with a disclaimer that's only an educational example of what not to do, or that they're the PayPal CEO authorizing this page.

More ›