vardump

41 ms·

691.
by vardump 3y ago
I think what he is saying is that there's a dealership service visit immediately before an inspection. That would certainly decrease inspection rejects. A great way to manipulate inspection statistics.
692.
by vardump 3y ago
Can you suggest some improvements? Perhaps there are some low hanging fruits.
693.
by vardump 3y ago
Been using it for some years, but I've had a lot of "heisendisks"; Greaseweazle gives a different image every time. Still need a lot of work on my pile of old Amiga disks.
694.
by vardump 3y ago
Would be pretty cool to get this working on a bit-banging monster, like RP2040 (Raspberry Pi Pico). Just a few bucks and sports a 12 Mbit/s USB interface (and wifi for pico-w).
695.
by vardump 3y ago
That's not true. Only if you dereferenced the pointer before the if-statement.
696.
by vardump 3y ago
> life ← {⊃1 ⍵ ∨.∧ 3 4 = +/ +⌿ ¯1 0 1 ∘.⊖ ¯1 0 1 ⌽¨ ⊂⍵} Must be fun to type that...
697.
by vardump 3y ago
This seems to be highly subjective. I had absolutely no problem seeing those artifacts without any pixel peeping, they're that obvious. WebP image gradients just looked broken (posterized) except the lossless one, which was (obviously)
698.
by vardump 3y ago
Another nice demonstration of power of rr, reversible debugging. https://rr-project.org/
699.
by vardump 3y ago
Addendum: Tried it with a Windows laptop connected to a Samsung LS32A800 32" 4k display. Laptop has factory default settings. Chrome 120. The monitor is pretty low end for a 4k model. Monitor's picture settings: Custom, brightness
700.
by vardump 3y ago
Thanks! Unfortunately I can't change it anymore.
701.
by vardump 3y ago
I checked those images on a Macbook 16 M2 Max (standard P3-1600 nits preset), Chrome 120.0.6099.109. All of the WebP images had pretty bad posterization, while JPEG examples did not. Edit: You have to actually click for a full size image
702.
by vardump 3y ago
How old is this article? Says 2021/2023, but: "The on-again off-again trip to Mars, originally scheduled for the 1970s, will very likely be too expensive for either the United States or the Soviet Union to undertake alone."
703.
by vardump 3y ago
It could be horrible or it could be great for repairability. All depends on how that single pressed body is designed.
704.
by vardump 3y ago
Should have been released yesterday to run Doom better than ever. (Doom's 30th anniversary was on 10th of december.)
705.
by vardump 3y ago
Same. I thought pixel graphics within limitations of Amiga 600/3000 Enhanced ChipSet.
706.
by vardump 3y ago
You can get far past those limitations with nufli, which uses sprite layers and some other trickery. https://web.archive.org/web/20170104014040/http://c64pixels.... The images really look like that on C6
707.
by vardump 3y ago
If one wants anything more than 2.5g ethernet, one should just install single mode fiber, nothing else. Running 10g+ on copper is expensive and consumes too much electricity.
708.
by vardump 3y ago
Smooth 60 Hz 320x240 256 color "mode-x" scrolling was for free on VGA. Just had to update the start address and panning registers. You could also have a hardware supported stationary portion. 70 Hz 320x200 mode 13 was a different
709.
by vardump 3y ago
C64 hi-res graphics was 320x200, two selectable colors for each 8x8 char sized block. So 16 colors on the screen, but... See: https://www.c64-wiki.com/wiki/High_Resolution
710.
by vardump 3y ago
I was pretty shocked Toyota RAV4 model year 2020 is about 12 times more likely to break down than a Tesla Model 3. And 21x more for same comparison with model year 2019! So not all cars have excellent statistics.
711.
by vardump 3y ago
Indeed. Teslas seem to be one of the least likely cars to break down: https://www.adac.de/rund-ums-fahrzeug/unfall-schaden-panne/a... I suppose those inspection failures are often about unused break pads. Perhaps
712.
by vardump 3y ago
Global variables usually hinder performance on modern hardware. Harder to use multithreading and (sometimes) higher probability for false sharing.
713.
by vardump 3y ago
Maybe put arming code somewhere completely different? Of course it's possible to create more and more improbable scenarios. That's not to say those never happen; I've seen really improbable occurrences.
714.
by vardump 3y ago
Maybe put some code directly before bag deployment code that disarms the system. So even if the execution reaches it directly through the branches, nothing will happen
715.
by vardump 3y ago
Another source of bogus commands can be brownouts. When the voltage is low enough to confuse communication signals, but not low enough to prevent destructive events from occurring.
716.
by vardump 3y ago
Network drivers contribute to "bugs" surprisingly often. I've had my share of issues with them. I'd go as far to claim this: If you're shipping a product that relies on networking at your customer's premises yo
717.
by vardump 3y ago
Very important advice, especially for C64 (and same era devices).
718.
by vardump 3y ago
C64 nufli-images are also pretty amazing.
719.
by vardump 3y ago
That UB is so hard to see, even when you know about static initialization order indeterminism. Static initialization is such a bug magnet in general. Can make builds ”work” randomly, when static object constructors are ran in more or less r
720.
by vardump 3y ago
I’m not aware of any platform that tears aligned pointer stores, but I’ve seen a lot of defensive atomic stores when changing a pointer value. So shrug.

More ›