That'd mean we have a different compiler in CI than what the developers use on their workstations - which is not a good thing. And wouldn't be tolerated there anyway - people already had some doubts when we were wrapping IAR with wine and a bit of shell to look like a standard UNIX toolchain.
(Shout-out to IAR, though. I still think they're overpriced and you don't really need them - but if you're stuck with them their support is excellent. When an update broke license handling in our setup they didn't tell us to go away like any other vendor would've done for that kind of wildly unsupported use case, but actually made it work again in the next release. They also got us access to native Linux binaries way before they even were talking in public about working on that to play around with for our CI)
There's no reason why stealth technology should have to advance faster than detection technology. In fact, in many applications with strong incentives to advance both stealth and detection capabilities, the modern world has trended towards being increasingly transparent.
If we culturally/economically wanted it, I'm sure we could all have cheap nonlinear junction detectors in our pockets.
Compare human cone cell spectral sensitivity to the camera modules inside the glasses. [0][1]
Usually digital cameras have some major differences from human eyes, particularly near UV and IR. Find dyes with spectral albedo that integrates to the same strengths for (most) humans' cones, but not for the glasses.
Though human eyes have pretty good dynamic range, and some degree of variation. Maybe add dithering around the edges.
Yepp, saw that number and I am very hopeful about it. But numbers are not everything and can be gamed (heh), the "feel" during gameplay is most important. I hope to try it out "early 2026" :).
I get very annoyed by the atrocious audio delay of Bluetooth, so I'll keep my long USB cable ready.
P.S. I am aware of USB also not being zero latency, but it is the lower bound, the dongle is USB as well.
Typical Bluetooth latency (in my experience as a HW dev) is 9.5ms. I'm pretty skeptical of 8ms for a proprietary protocol, but in an optimistic sense. I would be shocked if the latency is that high for a custom protocol.
Raw 802.11 with no IP stack can get below 5ms IIRC
Submission title is taken from the `<meta property="og:title">` tag on the page that shows on search and social media embeds. The full title from the page wouldn't fit.
WebRecorder [0] is the best implemention of this that I've tested. It runs as an extension in your browser, intercepting HTTP streams, so as long as you open a page in your browser the data is captured to reproduce it exactly. It outputs WARC files that are (in theory) compatible with the rest of the web archiving ecosystem, and has a WARC explorer interface to browse captured archives.
For pages with dynamic content that can't be trivially reproduced by their HTTP streams— E.G., opening the archive triggers GETs with a mismatched timestamp, even if the file it's looking for is in the WARC under a different URI— There's always SingleFile [1], and Chromium's built-in MHTML Ctrl+S export, which "bake" the content into a static page.
Last non-bot commit was over 2 weeks ago, and it seems to be mostly 1 account working on it. I don't think it looks active enough to be the big schism it's made out to be?
Nim itself has very few core developers. Comparing the number of developers involved in a hard fork to the number of Nim developers is silly, in my opinion at least.
The project has 21.5k commits authored, most of them oriented at replacing the existing compiler backend with a CPS-oriented one. Nim 3.0 is replacing the backend with one that is focused on CPS. There is no doubt that the developers responsible for the hard fork of Nim inspired Nim 3.0.
Yes, it very much is the big schism it's made out to be. I don't know what kind of activity level you expect, when the Nim language itself has few core developers working on it.
> Maybe if you trust the software, then trusting the install script isn't that big of a stretch?
The software is not written in a scripting language where forgetting quote marks regularly causes silent `rm -rf /` incidents. And even then, I probably don't explicitly point the software at my system root/home and tell it to go wild.
0: https://news.ycombinator.com/item?id=36994418