Surprised this article didn't mention his antics in Hawaii, where he tried using lawsuits to secure all of the parcels in his 700-acre Kauai property from native Hawaiians. (He dropped the lawsuits after the optics became terrible, but he's still reviled there.)
Zyruh, your individual comments & submissions are friendly, appreciative, and inquisitive... but they're a little uncanny when viewed as a whole. Are you a real person?
I'm the Mark who's referenced there. When I did that original benchmark I discovered that the underlying mutex used by MSVCRT did change between versions. For example, in Visual C++ 2013, they used the Windows Concurrency Runtime, which was awful under heavy contention. Newer MSVCRT versions use SRWLOCK.
(And I wouldn't characterize myself as being overly impressed... for my particular scenario I wrote, "if you have a poorly written app that's bottlenecked on a lock, then consider targeting Windows to make the best of a bad situation." A better approach, of course, would be to just improve your code!)
It looks like RDMA is kind of like IP4, in the sense that it wasn't originally designed with security in mind. Was this vulnerability a big deal when the paper was submitted in 2022, or more a case of doing cool research on a protocol vulnerability? The attack scenario looks pretty limited:
"We consider an adversary that is on one of the endpoints of the victim connection (i.e., it is co-located with either the NVMe-oF target or client). The attacker is an unprivileged user and is assumed to have obtained access to the machines using legitimate means. We assume that the attacker shares the same physical RNIC as the NVMe-oF entity and both can use it for communication. We assume that the attacker and the NVMe-oF entity are not separated through RNIC virtualization. The TLU model is prevalent in private clusters that use RDMA and NVMe-oF to accelerate their workloads."
An attacker is pretty deep into your infrastructure if they can even get a whiff of your storage fabric like this.
I can kind of understand being temporarily distracted when a message comes in and your phone chirps, but wow... watching a video while you operate a 3000 pound machine is next-level idiocy.
I haven't been driving as much in recent years wasn't aware of this trend. (Except for Tesla drivers: 5 years ago, I remember looking over to see a Tesla on autopilot next to me, doing 60 on Seattle's 520 bridge with the driver totally checked out and watching a video.)
You're getting close to making your own CHM format, which Sphinx could make for you.
I always thought CHM files were a nice self-contained option for multi-page HTML docs. (Though they'd happily execute whatever JavaScript the author embedded in there... Maybe that's why they fell out favor?)
It would be great if there was an open CHM-like format that was supported by all major browsers. The nice thing about browsers is that everyone already got one installed. They can even open PDFs natively these days. Sadly, they cannot even open epubs (which is almost like CHM without interactivity). I believe firefox used to be able to open epubs, not sure what happened.
Edge supported epub until the bitter end of the Spartan renderer. It was only Microsoft's attempt at an ebook store that died long before that. Admittedly, most people's visibility into Edge epub support was through the Store and the sidebar dedicated to store purchases, but if you had no other book reader app take over the .epub file extension (or if you realized that you could drag and drop DRM-free .epub files into new tabs) Edge would still read them right up to the Chromium switch.
I think it was too. I also think a lot of people missed that there was an app in the Microsoft Store from some team adjacent to the Edge team at the time called the boring and easy to overlook name "Reader" that just had the PDF and EPUB viewers from Edge in a file-based UI instead of browser chrome UI. It was such a useful app and you could set it to default for PDF (in Windows 8 and the early years of 10) and EPUB files (in early Windows 10, with some effort). I never understood why their ebook store effort focused on a sidebar in Edge that didn't work like anything else in Edge instead of beefing up a file-based app like Reader. Reader also died when Edge went to Chromium and I still miss it as a lightweight and fast PDF reader.
I did use Qt Quick and I've been having such a great experience (as someone that used to program GUI imperatively via Qt C++ or using other framework like React/React Native) in my opinion, Qt C++ and Qt Quick is the best combo for a GUI framework. You get the performance of C++ and the simplicity, fluid animations, reactivity of QML, etc... My block editor is build in such a way that the models are in C++ and the views are in QML. This separation of logic and presentation works really well. I'll probably wrote a blog post about it.
Must be Widgets since using QML at work makes me regularly wanna rip my hair out. Its one of the worst frameworks Ive used once you go beyond simple hello world programs.
I "upgraded" from a Samsung Galaxy S9 to a Pixel 7 this year, only because Samsung stopped doing security updates. Big disappointment for me, too. The fingerprint scanner from that 2018 phone was 10x more reliable than the in-screen thing that the Pixel uses.
I don't miss the battling software ecosystems (Samsung vs Google) on that old phone, though.
Oof. I forgot about how much better Samsung's sonic FP readers were. Yeah completely forgot about that from the S10e. I will say for the Pixel it's a little bit better now than it was at launch.
