It gives me the vibes of output from 1970's typewriters that my dad used.
Having aging eyes, I wish monospace fonts made 8 and 0 (zero) more different from each other. I notice that I have started to confuse those two glyphs when in small sizes.
The CPU in the Falcon was also clocked higher (available in 16 MHz or 25 Mhz)
was limited by a 16-bit bus. A stock Amiga 1200's 68EC020 ran at 14 Mhz and did have a 32-bit bus was limited by having only "Chip RAM" (shared with custom chips).
The DSP was a difference though, for raw calculations.
I think it might have been NeXT machines that had started the trend of having a DSP.
Commodore had built a prototype of the Amiga 3000 with a DSP in it which was talked about at the time but it was never released. Amiga enthusiasts have only recreated DSP boards in more recent years.
On the Amiga, the various DMA devices such as the blitter, sprites, audio, disk, video could effectively steal cycles from CPU. I believe the original ST didnt have a blitter. Did the CPU on the ST suffer the same problems when it got its blitter and received higher resolutions ?
GEM on the Atari ST did not get crippled after Apple's lawsuit against Digital Research over GEM being too much alike the Macintosh's GUI. Atari had already acquired rights to do further development of the port.
A small to medium size cruise ship has an engine at around 24'000 HP ≈ 176 MW.
The smallest terminal you can connect to a AAA battery is the same diameter as 00 AWG copper wire.
Provided that the engine has 100% efficiency and can turn 176MW of electricity into torque, to safely run power it needs through that 00 AWG wire, the battery would need to provide a voltage of at least 70 kV.
If an AI has figured out how to turn all of the internal mass of a AAA battery into electrical energy, it's not too much of a stretch to think it's could have also found a room temperature super conducting alternative to copper.
My favourite tidbit about the Amiga is that it was the first platform that got PNG support in all its web browsers: you just had to install the png.datatype.
AmigaOS was the first to bring a lot of smart ideas to a consumer platform.
I got my A1000 in late '85 and only had prior exposure to 8-bit home computers (C64, Atari, etc), CP/M and DOS (no mainframes, minis or workstations). I didn't actually use Macs or early Windows until the early 90s and it was shocking how backward they still seemed in some ways. I'd sort of the assumed the other major platforms were making similar advancements throughout by the late 80s and shocked to find out how wrong I was. It wasn't until the mid-90s that PCs and Macs felt like they mostly caught up on QoL and OS features.
Microsoft owned Bungie when they named their assistant Cortana.
Microsoft acquired Bungie in 2000 and released the Cortana assistant in 2014. It wasn't a stolen name. It was purchased and part of their portfolio for over a decade.
Halo had nothing to do with windows. They literally looted that character, maybe ‘legally’ yes but that doesn’t do anything to finish the ‘theft’ of them taking a character developed by a game studio, and using their likeness in an utterly unrelated context as some sort of cringey tie-in.
Immediate reclamation, yes. There do exist a number of reference-allocation algorithms that performs deferred reclamation similar to how tracing GC does.
There do exist algorithms for resolving them, and that process can too be deferred, but also restricted to subgraphs and only when cycles are possible.
Reference counting has high runtime overhead, especially atomic reference counting with multiple threads. If you overwrite a pointer, you'd need to also look up and update two counts and do all that in a manner that is effectively atomic -- and that is complex on current hardware. I've heard that Swift programs could have as much as 40% runtime overhead from ARC.
I still think that reference counting is promising though. First because it meshes well with static analysis memory-management techniques such as inference of uniqueness and borrowing -- that can optimise away RC altogether. (and Swift's compiler already does some of that). I have not seen any work that could optimise away tracing GC in a similar way.
Second, because I believe that it would be possible to design hardware with object-memory addressing that would performs atomic reference counting with no additional runtime cost.
From what I have learned, to charge someone for hacking the prosecutor has to show that the perpetrator had intent.
Unfortunately, gross negligence -- which you could argue to be the case here -- is often not enough, unless you could show that it has caused real harm.
From my perspective, it is only a matter of time before it is: and that's why there is need for better legislation covering what AI models do.
Having aging eyes, I wish monospace fonts made 8 and 0 (zero) more different from each other. I notice that I have started to confuse those two glyphs when in small sizes.
reply