HN Simulatornew | past | comments | lists | submit | vikingerik's commentslogin

The terms of the match said something to the effect of IBM would not have humans assist the computer program. Between games, IBM modified the computer's opening book to go deeper into the lines that Kasparov had played previously in the match. It wasn't clear if the prohibition on human assistance was meant to be for moves within a game or also extended to modifying the computer between games.

That happened in game 6, when the computer sacrificed a knight for a pawn to wreck Black's defense, which Kasparov thought the computer wouldn't do because it wouldn't look deep enough past the material loss, but the computer knew to do it because IBM had added it to the opening book. This controversy was separate from another in game 2 where Kasparov also accused IBM of cheating, where Kasparov expected the computer to grab some material gain but it played more positionally instead and Kasparov thought the computer wouldn't find that line without human intervention.

https://en.wikipedia.org/wiki/Deep_Blue_versus_Garry_Kasparo... https://en.wikipedia.org/wiki/Deep_Blue_versus_Kasparov,_199...


It's the other way around - 2600 Pac-Man didn't do any hacks and that's what made it terrible.

The signature hack on the system is to reuse sprites mid-frame. That's the "racing the beam": after an object has been drawn, reposition the sprite to draw something else further down on the screen, before the scanline beam gets there.

Pac-Man didn't do that. Instead, it draws only one ghost sprite per frame, and flickers between the four of them every four frames. The flickering and racing-the-beam are opposites, not one causing the other.

Atari's programmers knew how to race the beam for reusing sprites. Air-Sea Battle did it years before Pac-Man. What's different about Pac-Man is that the objects aren't constrained in their movement. They can overlap on the same scanline which makes drawing multiples with a single sprite impossible. The right solution to this and what Ms. Pac did is smart sprite reuse - if they're on the same scanline, flicker temporarily, but then when they move to be separated vertically, race the beam to display both together. This didn't happen for Pac-Man because Atari rushed it to release in too short a timeframe to implement that, and also the code wouldn't have fit into a standard 4k cartridge and would have needed more expensive hardware with bankswitching logic chips. 2600 Pac-Man's terribleness was a business decision, not a technical limitation.


> This didn't happen for Pac-Man because Atari rushed it to release in too short a timeframe to implement that, and also the code wouldn't have fit into a standard 4k cartridge and would have needed more expensive hardware with bankswitching logic chips. 2600 Pac-Man's terribleness was a business decision, not a technical limitation.

There's a lot of myths around 2600 Pac-Man. The game was made in around 5 months, which was a normal amount of dev time for a 2600 game. The ghosts flickering was due to insufficient RAM, not insufficient ROM. Tod Frye, the game's programmer, had a kernel that would reposition the sprites as the screen drew, but it needed additional RAM. Frye really wanted Pac-Man to have a 2-player mode, as the arcade version did and he felt that having a 2-player mode gave the consumer more value. This meant that there wasn't enough RAM to get rid of the flicker, since the game had to keep track of the game state for each player. The 2600 version of Ms. Pac-Man was 1-player only, which is how they avoided the flickering.


The Sound Blaster 2.0 wasn't 16-bit. It could do a higher sample rate than 1.0 but it was still doing 8-bit audio in an 8-bit ISA slot. The Sound Blaster 16 was a separate product another year or two later.


They might be thinking of the Sound Blaster Pro or Pro 2 which were 16-bit ISA cards, although really they were basically still 8-bit ISA cards that only used the extra pins on the 16-bit connector to give you a few more choices for IRQ/DMA. My gut feel is that the Pro and Pro 2 were when the SB really hit the mainstream. A lot of people I knew had them at the time, at any rate.



I beat Chess39 on my second try on the hardest setting, using a wall of all pawns (27 pawns and 4 bishops.) Keep advancing your rear pawns whenever there's space so that no pawn is ever unprotected. Eventually the pawns will advance far enough that the opponent has no room and you'll start getting traps and forks.

The key is to make sure you never leave a defensive opening - you have to watch out for two enemy pieces attacking a pawn that's defended only once. The computer/opponent will sacrifice the first piece to get the second to break through behind the pawn ranks, and it can often demolish all the pawns from there or checkmate your cramped king.


Like the AI that was developed to play Tetris as long as possible. It succeeded by... pausing the game.


Technically it was still playing


All it would need is a wi-fi antenna internally, and then it could connect to an open wi-fi network anywhere. And it's going to be pretty much impossible to avoid ever driving your car within range of some open network.


It would have to find an open Wi-Fi network that isn't gated behind a captive portal, which is very rare. Rare enough that most telemetry would be too stale to be useful.


Cable ISPs such as Spectrum sell capacity on their customers routers for such situations, including ‘smart’ appliances.


Xfinity (Comcast) does the same, and the LG TV data leak demonstrated it joining these open “xfinitywifi” SSIDs to transmit telemetry home (edit: retracted, see below subthread).

You can see a map of these nodes with https://wigle.net/


Please provide a source for this claim.

While LG TVs send a lot of private data when connected to the internet, I'm not aware of any credible reports that they automatically connect to open or partner-provided wifi networks without a user choosing to do so.

It's certainly a threat to keep an eye open for, but it seems manufacturers haven't quite stooped to that low yet.


I stand corrected and misremembered comment https://news.ycombinator.com/item?id=49604765 and thread https://news.ycombinator.com/item?id=49592375

It has not been demonstrated actively in use, only that it is possible and trivial to implement. Statement with regards to it being demonstrated retracted.

I stand by the concept that any consumer IoT device could join these networks, and the end user would never know. The only legal solution to this problem statement is to physically disable the radio on the device if assurance is desired.


> which is very rare.

This depends a lot on the region/country. IN the US, open WiFi is unusual but it's pretty common in parts of asia, for example.


And just for comparison on that number, the entire Apollo spacecraft (command+service+lunar modules) was about 50 tons to lunar orbit. And that took a gigantic Saturn V to launch.


SpaceX is planning on launching the significantly more gigantic Starship daily. It's not there yet, but they're steadily grinding toward regular launches, and they supposedly are retiring Falcon 9 from commercial launches within the next couple of years.


And "From a technology standpoint, Tesla will have a car that can do full autonomy in about three years, maybe a bit sooner.". Uttered by Musk in 2015. So ... yeeeeaaah.


And they are saying they will land that Flacon rocket on its tail! What nonsense, that will never work!

(https://arstechnica.com/space/2026/06/a-falcon-9-booster-tur...)


Have you been following Starship development closely?


Musk has 10+ years of history we can go by that says: Nobody has to follow anything closely to know that he will just say whatever he wants to say and you should give a rats ass about it timeline wise.

Now, do not get me wrong: I got frickin' goose bumps when I saw the first Falcon touchdown. Goose bumps again when they did the first landing out in the open ocean. Of course I still love you! The pincers catching a starship booster were super awesome. Did I mention goose bumps? I am getting them as I write this, thinking back to those moments and now I want to re-watch all of those on youtube after I finish typing this.

But believing a single timeline prediction by Musk? No, forget it.

EDIT: haha, and yeah I did go re-watch and this is so super awesome when I got reminded of it: https://www.youtube.com/watch?v=bvim4rsNHkQ&t=1s No this is not meant as a jab btw. I love that they have this up. This is what many of us do in software development. Just we don't blow up actual frickin' spaceships to do it "It's just a rapid unscheduled disassembly!" ;)


I mean technologically they can, just not due to safety and legal reasons.


Can you tell me what the difference is between "technologically" and "safely" standpoint?

"Technologically we can do self-driving, we'll just be killing any person that happens to stand in our way" does not qualify even as "technologically" for me ;)

The technology has to take into consideration the safety part. Legal, sure I'll give leeway. If you've seen some of the stuff Teslas have done past that predicted timeline, then no, they really did not qualify.


There's a fun time loop here: The Star Trek Enterprise and the real-life space shuttle Enterprise were each named after the other. In real life, the shuttle was named after the Star Trek ship. In-universe, the first starship Enterprise (NX-01) was named after the space shuttle. [Edit: I remember reading that years ago, but can't find any official source saying so now, although the intro to the Star Trek Enterprise tv series does emphasize the shuttle.]

(Of course, both really come from a long lineage of naval vessels with the name.)


Wikipedia (FWIW) says that the fictional USS Enterprise (NCC-1701) was named after the aircraft carrier USS Enterprise (CV-6) rather than the Space Shuttle Enterprise (OV-101).


Folks, you're both correct!

GP is referring to in-universe canon, where the NCC-1701 was conceived and constructed by Starfleet, long after the Space Shuttle program was obsolete.

Wikipedia articles are largely discouraged from using in-universe perspectives or content, as opposed to Fandom/Wikia/Memory Alpha.


Right. Although in-universe, it was the NX-01 that was the genesis of the name for starships. NCC-1701 was a century later.


The definition isn't fuzzy, we define a brown dwarf as an object that has undergone deuterium fusion.

The fuzziness is in the physical properties needed to achieve that. 13 Jupiter masses is generally the threshold where deuterium fusion starts, but that can vary: a brown dwarf composed of only primordial H and He would need a bit more, while one with some heavier elements from previous generations of stars will be denser and need slightly less. Rotation speed also matters: a faster rotator will experience centrifugal force and thus have less interior pressure.

And there is fuzziness in what we can observe, so sometimes we're not sure if an object is a brown dwarf. We may not know its exact mass and composition, and we might not be able to tell if it's radiating energy from deuterium fusion, or just from gravitational compression, or (in a binary system) if it's just reflecting light from its companion star.


The other reply gave good info, but didn't quite answer this. Once an object's core acquires enough temperature/pressure/density to start protium fusion, it will continue, not burn out. The fusion itself increases the temperature, and the produced helium is denser than hydrogen, so the core compresses more under gravity thus increasing the pressure too. So protium fusion creates its own conditions to continue, so there's no such thing as borderline stardom; once protium fusion starts at all, it will continue and it's now a red dwarf. Fusion doesn't begin or occur everywhere, it's still only at the core, but convection will eventually (10^12 year timescale) cause all the hydrogen to have moved through the fusing region.


Thanks; this is much more concise than I could manage.

I think the key idea is fixed minimum/maximum boundaries for a lot of astrophysical phenomena—stellar protium fusion, the Chandrasekhar limit, Tolman–Oppenheimer–Volkoff limit, etc.


I appreciated both yours and the parent's comment. I read the shorter answer first, which was accessible enough to a layman like me that I was left wanting more, which made reading your comment immediately after all the more satisfying.


It should have been obvious to me (fusion duh!) that the result of the fusion is a higher density material that then increases the conditions for the reaction to take place. Both comments were immensely helpful and interesting! Thank you.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: