Viewing profile — ssokolow

My point is that your argument is comparable to faulting Ford for making cars disposable with crumple zones when nobody else has found a better way to meet the crash-safety require…

If you're offering a new package manager up for installation (which, Steam aside, isn't the kind of thing that's normally practical to put inside a Flatpak sandbox) on a platform w…

By that simplistic logic, we should ban all seatbelts and airbags because they cause authoritarianism.

Here's a better exploration of defect rates: https://security.googleblog.com/2022/12/memory-safe-language...

*nod* I remember an interview with Steve Gibson (author of SpinRite) 10 or 20 years ago where he was talking about how much modern-at-the-time hard drives relied on ECC to reliably…

I remember seeing a blog post about that years ago and I probably bookmarked it but Firefox doesn't seem to have a way to search bookmarks for "Java" but not "JavaScript" and it ap…

Yes. In practical terms, because optimizers like GCC and LLVM track uninitialized values and it's undefined behaviour to read from them, so you essentially have a split between wha…

*nod* As someone who came from Python for easier maintainership (strong compile-time checks, an ecosystem that tries to follow the toolchain's "fearless upgrades" philosophy, almos…

Back when that happened, this post came out: https://blog.yossarian.net/2021/02/28/Weird-architectures-we... TL;DR: Look at it from our perspective. It's not reasonable for us to b…

That's not a property of the language, it's just an optimization they made in line with the "Release a minimum viable product, then improve it" strategy they inherited from Mozilla…

https://play.rust-lang.org/?version=stable&mode=debug&editio...

The word "correct" already had a meaning. Memory safety is a subset of correctness in the same way that Rust can't statically prevent race conditions but it can prevent a subset of…

Bearing in mind that "there should be no room for a language above assembly and below Rust" (i.e. something like what C or C++ is to Python, Java, C#, etc.) was an intentional desi…

True... but if you go by what you're most likely to encounter, I'd argue the biggest unaddressed flaw in Rust is the lack of a current, maintained analogue to tools like Rustig! an…

*nod* They're from before I started bookmarking rigorously, but in the early days of Rust, there was a sentiment in the blog posts from the people developing it that the point of R…

*nod* As-is, we're stuck with hacks like custom shortcodes and emoji. ...though, given the inconsistent naming of consistently laid-out buttons, I think anything that makes its way…

By "game tutorials", I think they mean modern successors to the role GameFAQs used to play. There is a combining character that, by its description, sounds like it should be implem…

I know Sylvain Kerkour is a perennial "Rust should be more like Go. I don't care that they're trying to meet different needs" person and has been for many years now, but I do wish …

That's fair. I still think the "because it's not in the fast path" part of "Most software will not see a bottleneck because of bounds checking because it's not in the fast path" is…

*nod* Give https://blog.readyset.io/bounds-checks/ a read. They tried doing a comparison between ReadySet compiled normally and ReadySet with bounds checking removed so thoroughly …

*nod* ...and stemming is that taken to a greater extreme. I was just pointing out that Unicode itself has various forms of normalization and normalization-adjacent functionality th…

> Before comparing strings or searching for a substring, normalize! ...and learn about the TR39 Skeleton Algorithm for Unicode Confusables. Far too few people writing spam-handling…

My anglophone Canadian brother's name is André. Even if you're fine with alienating the ~50% of the world population using non-latin writing systems, probably best to at least stic…

Technically, a superset would have to somehow Schrödinger's cat around \ in latin1 and ¥ in Shift-JIS being the same codepoint. Unicode just took it upon themselves to reliably rou…

According to a sibling to what you replied to, it's because the shapes of the glyphs are still under copyright by known-litigious rightsholders and the Unicode consortium doesn't w…