Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
anyfoo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
62 ms
·
811.
▲
by
anyfoo
3y ago
Re-encoded low bitrate MP3, even...
812.
▲
by
anyfoo
3y ago
Now do chocolate. The first time I tasted Hershey's chocolate was... interesting, to say the least. For the uninitiated: It tastes like vomit. No, I'm not being purposefully annoying, it literally tastes like vomit. And that
813.
▲
by
anyfoo
4y ago
Though in most cases, you can just type “reset” to reset your terminal to a sane state. If the problem is not the terminal’s state, but how software is trying to talk to it, setting TERM=vt100 (with a “reset” for good measure afterwards) us
814.
▲
by
anyfoo
4y ago
It seems you need at least: 1. A PowerPC machine (with IOMMU, so I guess it can't be too old). 2. A PCI VGA card. (Emulated, it seems.) 3. IBM VIO bus support compiled in. 4. A KASAN kernel booted to get told about the issue so clearly
815.
▲
by
anyfoo
4y ago
Super interesting, thanks. Another thing I just noticed: > Apparently a comprehensive solution (e.g. counting the prefixes or providing a buffer to hold prefixed during an interrupt) was impractical for the 8086. Did you have a particula
816.
▲
by
anyfoo
4y ago
I forgot that it moves from DS:SI to ES:DI, but that's actually super interesting that the registers were named differently originally (and I did notice that the AX/BX/CX/DX order is weird before)... What were CS and SS
817.
▲
by
anyfoo
4y ago
Ah, I forgot that it's DS:SI to ES:DI. Thanks.
818.
▲
by
anyfoo
4y ago
> SI → IND R DS,BL 1: Read byte/word from SI > IND → SI JMPS X0 8 test instruction bit 3: jump if LODS > DI → IND W DA,BL MOVS path: write to DI Is "W DA,BL" a typo, should it be "W DS,BL&qu
819.
▲
by
anyfoo
4y ago
> Finally, the address adder increments and decrements the index registers used for block operations. It's kind of surprising to me that it's the address adder that increments/decrements the index registers. Since it'
820.
▲
by
anyfoo
4y ago
Today I learned. I in my mind briefly went through anything that would foil such a plan, but with no caches whatsoever... should indeed have worked, even if it's weird (and deeply incompatible with what PCs did, of course). The only th
821.
▲
by
anyfoo
4y ago
I grew up with a "Siemens PC-D", 80186 and not fully IBM compatible for the reasons you said. However, it seems that the folks at Siemens were very enthusiastic about it, and ported a lot of software that accessed the hardware mor
822.
▲
by
anyfoo
4y ago
And it's been stated in related threads numerous times (and by you as well if I recall correctly) how Intel at that time strangely treated their low pin count limit as almost a religion... apparently that influenced many decisions.
823.
▲
by
anyfoo
4y ago
I see, thanks! Looks like I might try both. The "no proper lightweight anonymous function syntax" sounds weird to me, I would have thought that's paramount for an array language? Do I misunderstand?
824.
▲
by
anyfoo
4y ago
Hmm, so why J over Dyalog APL then?
825.
▲
by
anyfoo
4y ago
From the way I often use Haskell, Matlab, and even crazy shell one-lines with lots of pipes, awk, sort, and other stuff, I often have the impression that array languages are exactly what I'm looking for for certain problems. The questi
826.
▲
by
anyfoo
4y ago
I don't know if I'm still in the target audience (or ever was), but for one thing, I can't even begin to describe how much "games as a service" games put me off. It's really not disgruntlement, but active repul
827.
▲
by
anyfoo
4y ago
One can fully understand the type coercion rules and the effects that result from them, and still acknowledge that said type coercion rules are not optimal, at least because they lead to very non-optimal outcomes. I for one am tired of peop
828.
▲
by
anyfoo
4y ago
I don't think "Oprah giving away a CPU to everyone" is really one side of the spectrum, though. In this case, everyone affected already bought the "car", and by themselves. I understand that replacing every CPU wo
829.
▲
by
anyfoo
4y ago
Good point. At the time, if Intel had had a better response to it, perhaps many people would have been fine to continue using their faulty CPU as a Pentium "without FPU", or only in contexts where they did not really care that muc
830.
▲
by
anyfoo
4y ago
It was pretty bad from the get go, though. It was a trivially occurring bug without a good workaround. You literally could not fully trust floating point divisions on that CPU, and you could even see that by just using the Windows calculato
831.
▲
by
anyfoo
4y ago
Oh sweet. I've definitely used sqlite (in a zsh script) for file deduplication. Very simple, mostly just rows consisting of paths and file content hash. But partial file deduplication is something else...
832.
▲
by
anyfoo
4y ago
Indeed a bit difficult without an actual example. OP was alluding that caches and hierarchical memory in general are distinct from „memory reordering“. If I understand correctly, you are saying that the situations you have in mind are i
833.
▲
by
anyfoo
4y ago
Can you elaborate? Genuinely curious.
834.
▲
by
anyfoo
4y ago
“avatars walking around on top of our company home page”?
835.
▲
by
anyfoo
4y ago
It's important to note that sometimes in university or elsewhere, you are just getting rigorous definitions, and while those are unquestionable useful or important, they might be entirely insufficient to build the necessary intuition.
836.
▲
by
anyfoo
4y ago
Yes. They are much, much more likely to do the right thing than what one can cook up themselves. And if used correctly, work consistently and performantly across platforms (e.g. in theory at least, release and acquire barriers could be just
837.
▲
by
anyfoo
4y ago
I don't think that's a distinctive explanation, though (i.e. "memory accesses were reordered" covers it already). On common architectures, from one core itself it never looks like the memory accesses were reordered. From
838.
▲
by
anyfoo
4y ago
I think you understood it. To your last point: > it doesn’t really prove that the only cause of x != y issue [...] is caused by the memory barrier problem (eg maybe a rare buffer overflow sets done to true too early). I mean, you can nev
839.
▲
by
anyfoo
4y ago
Towards the end it says: > At Communities.com we developed a system called Passport (I’ll save the astonishing trademark story for a later posting) that let us do some pretty amazing things with web browsers. For example, with just a few
840.
▲
by
anyfoo
4y ago
I don't know, but I'm pretty sure that's why they called the (backwards compatible) 32bit variant "CardBus", instead of PCMCIA32 or something.
More ›