But the game is “finished”. there is no need for alterations.
If only that was the case. But there is no chance a game built for windows 95 could run unaltered on an android phone. Things like the rendering systems, input handling, and sound output will need to be adapted to work on a new platform.
You could, but there isn’t much benefit. The purpose of all that extra information is generally to make the program easier to understand for a human. The computer doesn’t need any of it, that’s why it’s not preserved in compilation. So it is possible to automatically translate assembly to C++, but the resulting program would not be much (if any) easier for a human to understand and work with.
To give a bad analogy, imagine some driving directions: turn left at 9th street, enter the highway at ramp 36, go right when you’re past the burger king, etc. These are translated into physical control inputs by the driver to actually take the car to its destination. Now we could look at the driver’s physical inputs and turn that back into a written list of instructions: turn the wheel left 70 degrees, turn it right 70 degrees, push the gas for 10 seconds, and so on.
All the street name references are now gone. There are no abstracted instructions like “enter the highway” or even “take the second left.” It would be quite difficult for a person to look at these instructions and figure out the trip’s destination. Let alone make some alterations to it because there is roadwork along the way and a detour is needed.
Your thought is correct. The basic problem is that higher level languages contain a lot of additional information that is lost in the compilation process.
It’s addressed in the article. The brave CEO has stated they will continue to support manifest v2 as long as the needed code remains in Chromium. He made no promises what happens when it is removed, though (“I don’t write checks of unknown amount and sign them”)
Fun quote from an interview with Chris Sawyer:
Latterly the machine code came back to haunt us when the decision was made to re-launch the original game on mobile platforms as RollerCoaster Tycoon Classic a few years ago, and it took several years and a small team of programmers to re-write the entire game in C++. It actually took a lot longer to re-write the game in C++ than it took me to write the original machine code version 20 years earlier.
Technically there is no Hi syllable in Japanese either. There is ひ, which phonologically is neither “Hi” nor “Fi”, but somewhere in between. The exact pronunciation varies depending on surrounding sounds, as well as the speaker’s regional accent.
So I wouldn’t say they really use WiHi. They write WiFi and they say “ワイハイ” which is the closest you can get to WiFi using Japanese sounds. It will kinda sound like WiHi to an English speaker.
Microsoft and the European Commission agreed to an initial period of five years. That ended in 2014, and the measure was not extended mainly for two reasons:
With competition in the browser market seemingly healthy, and the browser ballot not doing much to affect it, it was seen as pointless to keep requiring Microsoft to display it.
The number has some connection to transistor density, in the sense that a lower number means generally higher density. However there is not any physical feature on the chip that is actually 3nm in length.
This has been true since the late 90s probably.
You now need to remember his velocity, his position on the map, the direction of his flight, his altitude, his plane’s weight and who knows what else, I’m not a pilot.
You’re not wrong per se, but I’m having trouble fathoming gigabytes of data being consumed by these types of parameters. You could probably track hundreds of thousands of airplanes with that much space. The only thing that I could imagine taking up that much memory is extremely detailed airflow simulation.
However, as a rule of thumb, the vast majority of memory data for video games is in most cases textures and geometry, and not so much the simulation. Based on the article, it seems this game streams high resolution geometry data based on your current location on earth, which I would say is the most probable reason it asks for so much memory.
The problem isn’t even the hard drives, it’s how they are managing them. There’s not many digital data storage solutions around that you can dump into a closet for a few decades and then still read.
You have to regularly test your hard drives, so that when one fails you can take your other copy of the data and put it on a new drive.
Efficiency records involving perovskites are generally not that interesting without any longevity data. As far as I’m aware, the lifetime of current SotA perovskite solar cells is measured in weeks or months. That’s not commercially viable.
Not that efficiency research is completely useless, but the longevity is the real challenge that’s holding this up.
https://docs.python.org/3/using/configure.html#cmdoption-disable-gil
The GIL appears to be slowly going away.