gcthomas
New member
Bit hard of reading, aren't you?
Can I add that inanity to the 'stripe program' responses? it's a great one!
Bit hard of reading, aren't you?
I just went to that link and put in some numbers. I'm confused. :idunno:
Numbers will do that.
I see what the program does now. It just takes a document of some fixed size and it systematically goes through and alternates every single pixel one at a time, until it has exhausted all pixel combinations. By doing so you iterate through every single possible image that could fit onto that area - meaning book pages, sheet music, source code, etc.
An interesting little program but I don't think it demonstrates the finiteness of man's creativity. All it really demonstrates is the finiteness of how many different images can be produced over a given area with a specific resolution. And it seems to be black and white only at that - so it can't reproduce works of art, which are a major area of human creativity. Granted, it would not be terribly difficult to rewrite the program so that it alternates through all color combinations as well.
I did see that. But I am still not sure he is accurate in his claims that it can reconstruct the source code of a program strictly based on the compiled machine instructions. For it to do that it would also have to referrence every compiler (cobol, rpg, assembly, basic...) known to man. Not sure that would be something worthwhile anyways. Though I have used utilities that can take a compiled object and produce the source code from which they were compiled. They are not exact in their production. They often make assumptions based on programming standards, and there are often many ways to program the same exact function for obvious
His program doesn't take a program name as an argument. All it does is produce pictures. He argues that by iterating through all possible images for a given area and resolution it will also iterate through the source code for any given program.
This is not false but it relies upon the assumption that he can combine the various images of his program. For you would be hard pressed to fit a program's source code onto a single page. See my previous post where I tackle Bob's argument and use his assumption to show that man's creativity is infinite rather than finite.
Then that is certainly not reconstructing the source code of a compiled object into whatever language the original program was.
I personally have worked on programs that are over 6,000 lines long (200 pages at 30 lines per page). Granted that was in the heyday of legacy programming and prior to object oriented programming standards. In one project I reduced the lines of code from about 8k to about 2k and added more functionality to the program in the process. This use to be a major issue in MIS because one could not just increase the horsepower of a machine when necessary back then.
Yes - his claims are highly exaggerated.
I currently work as a Software Programmer - trust me programs have not gotten any smaller. To the contrary - 200 pages would be nothing compared to the software I currently work with.
I can't believe any of you guys ever took this seriously.
Only the followers of Bob took it seriously. Although I did find the use of programming to make a theological point interesting.
I will now use Bob's idea to prove that man's creativity is INFINITE rather than finite.
I did see that. But I am still not sure he is accurate in his claims that it can reconstruct the source code of a program strictly based on the compiled machine instructions. For it to do that it would also have to referrence every compiler (cobol, rpg, assembly, basic...) known to man. Not sure that would be something worthwhile anyways. Though I have used utilities that can take a compiled object and produce the source code from which they were compiled. They are not exact in their production. They often make assumptions based on programming standards, and there are often many ways to program the same exact function for obvious
Only the followers of Bob took it seriously.
I currently work as a Software Programmer - trust me programs have not gotten any smaller. To the contrary - 200 pages would be nothing compared to the software I currently work with.
I personally have worked on programs that are over 6,000 lines long (200 pages at 30 lines per page). Granted that was in the heyday of legacy programming and prior to object oriented programming standards. In one project I reduced the lines of code from about 8k to about 2k and added more functionality to the program in the process. This use to be a major issue in MIS because one could not just increase the horsepower of a machine when necessary back then.
I see what the program does now. It just takes a document of some fixed size and it systematically goes through and alternates every single pixel one at a time, until it has exhausted all pixel combinations. By doing so you iterate through every single possible image that could fit onto that area - meaning book pages, sheet music, source code, etc.
I was a programmer/analyst for 16 years. I worked on programs written in COBOL, RPG3, RPG4, RPGILE, JCL, CLP, Basic, Dbase, Foxpro...Most of my work was surrounding canned business applications software packages (GL, AP, AR, MRP, Wholesale Distribution...) as well as interface programs between various platforms. Though I did do work at 2 software houses for about 5 years of that time.
So you are a follower of Bob? You and noguru?
The program can do what it was claimed it could do. :idunno:
Who thinks they won the bet?