Ygg2

5 ms·

31.
by Ygg2 2mo ago
I mean, zipping files in an archive and presenting them as a file is an ancient tradition in video games. For example Warcraft 3 used the MoPaQ archive to store data in .w3x file. And Starcraft 2 data is just bunch of XML files.
32.
by Ygg2 2mo ago
Office documents since the 2007 have used a zipped XML approach. Just take an .docx and open it in 7zip. EDIT: Narrowed the date.
33.
by Ygg2 2mo ago
It's not that weird. Most of Office and Open office formats are just zipped folders of XMLs. Better Zipped XML than whatever monstrosity Adobe files are. PDF/PSD... shudder.
34.
by Ygg2 2mo ago
Not even the sea floor. When whale carcass falls to the sea floor, it creates its own mini-ecosystem that lasts as long as the corpse lasts (couple of decades).
35.
by Ygg2 2mo ago
> Sadly Agent Smith was not wrong there. Wachowskis just don't know any better. You think it's air your breathing now? Oxygen? More like plant waste product. Also no ecosystem is in perfect harmony. It's basically jenga to
36.
by Ygg2 2mo ago
Vantablack pattern?
37.
by Ygg2 2mo ago
I'd say unwrap isn't a subtle case either. Yet people see examples and think - "This is the way!"
38.
by Ygg2 2mo ago
Keep in mind it's UB to be: > Executing code compiled with target features that the current thread of execution does not support I.e. calling AVX512 on Neon architecture. You need to wrap it in target attributes to even dream of it
39.
Rust Project goals 2026: Reflection and Comptime(github.com)
2 points by Ygg2 2mo ago|1 comments
40.
by Ygg2 2mo ago
Seeing how people were interested about immobile types. Why not discuss the silent MVP of the goals. Rust comptime.
41.
by Ygg2 2mo ago
> # How does this relate to the "pin ergonomics" initiative? > This work is an alternative to Project Goal 2025H2: Continue Experimentation with Pin Ergonomics, which includes the following extensions: >
42.
by Ygg2 2mo ago
Pretty sure they ditched that motto long time ago.
43.
by Ygg2 2mo ago
I wonder if in a few years, there'll be heads of Google paraphrasing the old skit "You know, in hindsight, allowing autonomous AI drones to carry fusion bombs was a bad move, but for that one quarter we really earned a lot of shar
44.
by Ygg2 2mo ago
Sure, but C code is way older so most of the bugs there should have been excised by now...
45.
by Ygg2 2mo ago
Some is doing heavy misrepresentation. Latest batch of LLM's Linux had 423 vulnerabilities. Out of which 10 were Rust*. Would you prefer more or less CVEs? But it's like seat belt analogy. It's a helper not a panacea. * Grant
46.
by Ygg2 2mo ago
With Fil-C and Rust the memory safety shouldn't even be discussed. It should be the bare minimum. Presence of worse bugs won't make memory bugs disappear.
47.
by Ygg2 3mo ago
> You're just splitting hairs and trying to weasel around the fact No. I said borrow checker allows unbound lifetime. I didn't disagree with you. I noted you didn't read the argument. > If you know what I meant, then wh
48.
by Ygg2 3mo ago
> Proof: You just listed examples of unbounded lifetimes. > I said "effectively disable". For example: Not sure what you meant by this example since it doesn't compile. It seems the borrow checker caught your mischief.
49.
by Ygg2 3mo ago
Andreas Kling talked about it. It boils down to C++ interop sucks (no surprise for lang made by Apple), ecosystem is tiny, Rust works well enough with LLMs. https://youtu.be/DbHjKi_jASY
50.
by Ygg2 3mo ago
Mu. Invalid question. Rust doesn't disable compiler features. It gives you extra set of footguns when you ask for it. As for the actual unloaded question, "What's the point of unsafe in Rust?" it is to contain and make i
51.
by Ygg2 3mo ago
If you saw the "Institute for Typesafe Memetic Research" and thought, "This is the den of Rust evangelists!" I don't want to break your illusion, because it's much funnier this way. Especially since there are l
52.
by Ygg2 3mo ago
> Calling him "smelley"? Turnabout is fair play. > Frankly, that entire "Institute for Type Safe Memetic Research" seems like either an elaborate satire or an account run by genuinely insane people who think type a
53.
by Ygg2 3mo ago
> True, but unsafe let's you conjure up any lifetime you want The only thing unsafe does is let you have an unbounded lifetime. As I said, it doesn't check those: fn get_str<'a>(s: *const String) -> &&#x2
54.
by Ygg2 3mo ago
You didn't just quote The Institute of Typesafe Memetic Research as proof of anything... It's a shitposting, hyperbolic bait account. As funny as calling Andrew Kelley Smelley, it's not meant to be taken as gospel.
55.
by Ygg2 3mo ago
Unsafe Rust doesn't automagically disable typesystem (& borrow checker, but lifetime are a sort of types). Once raw pointer is turned into a T, &T or &mut T, the borrow checker is on.
56.
Goodbye, and Thanks for All the Bikesheds(queue.acm.org)
295 points by Ygg2 3mo ago|266 comments
57.
by Ygg2 3mo ago
> Developer & time-cost of a rewrite is a big unknown... An optimist might say this cost has vanished. I wouldn't say it vanished. I'd say it moved from unknown to known. It's highly likely that for code the size of Bu
58.
by Ygg2 3mo ago
> By the engineer's wit of course! Seeing how the Rust compiler isn't an LLM, it can't really work on wit. From the POV of a programmer, how would you implement an unsafe block? What is disabled vs what's enabled? &gt
59.
by Ygg2 3mo ago
Ok, and how does, in your opinion, compiler rules enforcement work in an unsafe block? And how does Miri help solve this issue?
60.
by Ygg2 3mo ago
No. I just think you're taking judge by number of segfaults out of context. That said, I wrote this before the edit.

More ›