ssokolow

7 ms·

1.
by ssokolow 1mo ago
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 requirements while satisfying the other requirements too. As for &q
2.
by ssokolow 2mo ago
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 where every distro has its own package manager
3.
by ssokolow 2mo ago
By that simplistic logic, we should ban all seatbelts and airbags because they cause authoritarianism.
4.
by ssokolow 2mo ago
Here's a better exploration of defect rates: https://security.googleblog.com/2022/12/memory-safe-language...
5.
by ssokolow 2mo ago
*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 achieve higher data densities when it used to be a sign of
6.
by ssokolow 2mo ago
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 appears "memory" wasn'
7.
by ssokolow 2mo ago
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 what memory is allocated from the perspective of write ope
8.
by ssokolow 2mo ago
*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, almost Go-like ease of deployment, etc.) I'd
9.
by ssokolow 2mo ago
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 be beholden to the lim
10.
by ssokolow 2mo ago
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. Just look at how long it took LLVM to
11.
by ssokolow 2mo ago
https://play.rust-lang.org/?version=stable&mode=debug&editio...
12.
by ssokolow 2mo ago
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 them called data races.
13.
by ssokolow 2mo ago
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 design decision for Rust which resulted in `unsafe`.
14.
by ssokolow 2mo ago
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! and findpanics, which would analyze your compiled, o
15.
by ssokolow 2mo ago
*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 Rust was "to give good ideas a second chance"
16.
by ssokolow 6mo ago
*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 into Unicode should include something that follows the
17.
by ssokolow 6mo ago
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 implemented to do the desired thing (U+20DD Combinin
18.
by ssokolow 2y ago
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 we could at least get a little acknowl
19.
by ssokolow 3y ago
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 a bit too much of a blan
20.
by ssokolow 3y ago
*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 that they needed to use a patched tool
21.
by ssokolow 3y ago
*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 that people are far too unaware of.
22.
by ssokolow 3y ago
> 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 code know about that thing. (Basically, it generates mat
23.
by ssokolow 3y ago
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 stick to the stuff covered by the latin1 legacy enco
24.
by ssokolow 3y ago
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 round-trip legacy text... thus the precomposed forms. Most
25.
by ssokolow 3y ago
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 want to subject font authors to that.
26.
by ssokolow 3y ago
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 want to subject font authors to that.
27.
by ssokolow 3y ago
"Extended (Grapheme Cluster)". The .graphemes() method in Rust's unicode-segmentation crate takes an is_extended boolean as an argument and, if you set it to false, you're iterating legacy grapheme clusters.
28.
by ssokolow 3y ago
Cookie consent is only necessary if you're sharing it with others (eg. ad networks, Google Analytics, etc.) or using it for "non-essential" functions (again, stuff like analytics). Sites just don't want the general publi
29.
by ssokolow 3y ago
Yes. Give https://www.youtube.com/watch?v=_mZBa3sqTrI a watch... especially the "Oh my God! We've been hacked!" part at 36:20. TL;DR: They had a transient glitch in their network switch and, because Windows u
30.
by ssokolow 3y ago
Give the "Indic scripts" section of https://manishearth.github.io/blog/2017/01/15/breaking-our-l... a read. TL;DR: Unicode is complicated because some non-Latin writing systems are complicated

More ›