Can mathematics be used to prove God?
- Thread starter soberxp
- Start date
-
Christian Chat is a moderated online Christian community allowing Christians around the world to fellowship with each other in real time chat via webcam, voice, and text, with the Christian Chat app. You can also start or participate in a Bible-based discussion here in the Christian Chat Forums, where members can also share with each other their own videos, pictures, or favorite Christian music.
If you are a Christian and need encouragement and fellowship, we're here for you! If you are not a Christian but interested in knowing more about Jesus our Lord, you're also welcome! Want to know what the Bible says, and how you can apply it to your life? Join us!
To make new Christian friends now around the world, click here to join Christian Chat.
yes, exactly that. say you only have 8 bits operating system. that's like you have 8 boxes, that can either have a 1 or a 0 in them. and say you want to express a number. you need one of those boxes to tell you if a number is negative or positive, so you're left with 7 boxes to use to make your number.
binary numbers are written like this, say you only have two bits:
00 = 0*(2^0) + 0*(2^1) = 0
10 = 1*(2^0) + 0*(2^1) = 1
01 = 0*(2^0) + 1*(2^1) = 2
11 = 1*(2^0) + 1*(2^1) = 3
with two bits the biggest number you can make is 3.
say you have 7 bits to work with, then the biggest number you can have is
1111111 = 2^1 + 2^2 + 2^3 + . . . + 2^7 = 2 + 4 + 8 + 16 + 32 + 64 + 128 = 254
that is simplified of course; we do more clever things with computers to express bigger numbers with smaller number of bits. but still, you can see ((i hope?)) that a computer has a limit on what it can encode, based on how much memory it can compute with.
the same thing is true for small numbers; a computer can only calculate some smallest number, depending on bit storage. so calculations can end up wrong, depending on what kind of math you are trying to do. it is possible to get very bad results if you don't understand this when you write code for your computer to calculate math.
so the problem with phone app calculators is for one thing, the operating system is not using 64 bit operating systems etc. and for another thing, it's more likely that someone has not taken these things into account, and you could get a calculator telling you you have 0 for an answer when you really don't, if it's not a sophisticated operating system 'under the hood' -- another thing that's common is that a calculator only shows so many digits, maybe ten, and any number smaller than ten digits, it just calls zero.
that is what happened when soberxp calculated this:
the answer is not infinity, it's a finite number.
this is what they did:
6^1,000 is about 14 followed by 777 zeroes. very big number ((big is still a relative term)).
divide that by 365 and you get around 39 followed by 774 zeroes. still very big number.
more digits than the phone can show, so the programmer of that phone calculator made it just show ∞ -- but the answer is not infinite.
binary numbers are written like this, say you only have two bits:
00 = 0*(2^0) + 0*(2^1) = 0
10 = 1*(2^0) + 0*(2^1) = 1
01 = 0*(2^0) + 1*(2^1) = 2
11 = 1*(2^0) + 1*(2^1) = 3
with two bits the biggest number you can make is 3.
say you have 7 bits to work with, then the biggest number you can have is
1111111 = 2^1 + 2^2 + 2^3 + . . . + 2^7 = 2 + 4 + 8 + 16 + 32 + 64 + 128 = 254
that is simplified of course; we do more clever things with computers to express bigger numbers with smaller number of bits. but still, you can see ((i hope?)) that a computer has a limit on what it can encode, based on how much memory it can compute with.
the same thing is true for small numbers; a computer can only calculate some smallest number, depending on bit storage. so calculations can end up wrong, depending on what kind of math you are trying to do. it is possible to get very bad results if you don't understand this when you write code for your computer to calculate math.
so the problem with phone app calculators is for one thing, the operating system is not using 64 bit operating systems etc. and for another thing, it's more likely that someone has not taken these things into account, and you could get a calculator telling you you have 0 for an answer when you really don't, if it's not a sophisticated operating system 'under the hood' -- another thing that's common is that a calculator only shows so many digits, maybe ten, and any number smaller than ten digits, it just calls zero.
that is what happened when soberxp calculated this:
the answer is not infinity, it's a finite number.
this is what they did:
6^1,000 is about 14 followed by 777 zeroes. very big number ((big is still a relative term)).
divide that by 365 and you get around 39 followed by 774 zeroes. still very big number.
more digits than the phone can show, so the programmer of that phone calculator made it just show ∞ -- but the answer is not infinite.
-
2
- Show all
K
Huh, well I was thinking of the one who created the four leaf clover midst of three, or is that random or as some would say because of the fall of man the ground was cursed thus the appearance of corruption.
there’s about three reason that I know of for that to happen unless you might know of another reason.
there’s about three reason that I know of for that to happen unless you might know of another reason.
what you calculated was this:
View attachment 197865
which works out to about 0.00000 ... 00005
((imagine there are 2,563 zeroes after the decimal))
the answer is not zero; it's just too small for your phone's calculator to figure out. you'd need to use something with i think a 32 bit logic? computers don't do 'math' exactly; there are 'smallest' and 'largest' numbers they can process - no matter what computer you use - because of some intricacies having to do with how they encode numbers.
the answer is 'approximately' zero, but not zero. just a very small number -- but 'small' is a relative term
View attachment 197865
which works out to about 0.00000 ... 00005
((imagine there are 2,563 zeroes after the decimal))
the answer is not zero; it's just too small for your phone's calculator to figure out. you'd need to use something with i think a 32 bit logic? computers don't do 'math' exactly; there are 'smallest' and 'largest' numbers they can process - no matter what computer you use - because of some intricacies having to do with how they encode numbers.
the answer is 'approximately' zero, but not zero. just a very small number -- but 'small' is a relative term
-
1
- Show all
even the phases of the moon don't match the phases of night and day on earth.
God made two 'clocks' in the sky, per Genesis, the sun and the moon -- but they don't coincide with each other. i asked a teacher, why isn't the solar year evenly divisible by a number of lunar cycles? or even a lunar cycle divisible by a number of day/night cycles?
he said, post, you should meditate on entropy.
smart dude, IMO.
God made two 'clocks' in the sky, per Genesis, the sun and the moon -- but they don't coincide with each other. i asked a teacher, why isn't the solar year evenly divisible by a number of lunar cycles? or even a lunar cycle divisible by a number of day/night cycles?
he said, post, you should meditate on entropy.
smart dude, IMO.
-
2
- Show all
