What's new

my last dumb phone

This is why I respond to Salty 2 maybe 3 times and then do everything I can to keep from participating in the thread anymore.
 
This is why I respond to Salty 2 maybe 3 times and then do everything I can to keep from participating in the thread anymore.

Well respond to this one then. Do you agree with One Brow that Rock Band on Xbox is a different game than Rock Band on PS3 just because the game won't play on the other platform?
 
Well you're saying despite what the law/courts say,

No one consults courts to determine if one codeset is the same as another. You can find that out with a diff statement. Mind you, I expect you to keep making some point about app identity or something similar, which was never being argued. I just don't see the need to play along.

Yes, they say it's the same WebKit engine.

1) The engine is a small part of the app, and 2) I believe that means teh algorithms are the same in that particular functionality, not that the code is the same. However, it's quite possible that section of code is the same.

That is my point.

Exactly, we both agree. The difference is that your point is irrelevant to the argument of which device is faster.

No, I don't have to define it that way at all, lol.

You already have. You already said that if you saved time by taking a shortcut, that made you faster.

You can't seem to separate "processes more data" with "processes data faster." The 2 are not the same thing.

If you give each one a million transactions to process, the PC does it faster. They both process one million transactions, so the PC does not process more.

And if you open the same webpage in chrome on your pc and your smartphone, the phone will be faster every time.

Your not opening the same webpage, as I understand it. You are opening a reduced-instruction-set page that has to be specially coded for smartphones. If you try to open the exact same webpage as PC will open, because that coding has not been done, it will open more slowly.
 
Do you agree with One Brow that Rock Band on Xbox is a different game than Rock Band on PS3 just because the game won't play on the other platform?

Dpo you agree the One Brow is knowledgeable enough to distinguish being a different game from having different code?
 
No one consults courts to determine if one codeset is the same as another. You can find that out with a diff statement. Mind you, I expect you to keep making some point about app identity or something similar, which was never being argued. I just don't see the need to play along.
This is a false argument. The definition of "the same app" is not "has identical code" like you keep trying to say. It isn't now, and hasn't ever been.

1) The engine is a small part of the app, and 2) I believe that means teh algorithms are the same in that particular functionality, not that the code is the same. However, it's quite possible that section of code is the same.
The engine is absolutely not "a small part" of a browser, lol.

Exactly, we both agree. The difference is that your point is irrelevant to the argument of which device is faster.
Lol, No it isn't.

You already have. You already said that if you saved time by taking a shortcut, that made you faster.
If you are going to the same place and you get there faster, that is all that matters. You keep arguing that you can carry more weight, so that somehow means you got there faster.

If you give each one a million transactions to process, the PC does it faster. They both process one million transactions, so the PC does not process more.
And if you give each 10 transactions, the smartphone does it faster. Again, the smartphone will be faster until you start overloading it.

Your not opening the same webpage, as I understand it. You are opening a reduced-instruction-set page that has to be specially coded for smartphones. If you try to open the exact same webpage as PC will open, because that coding has not been done, it will open more slowly.
You are wrong. You're opening the same exact webpage on both. You can set chrome to open a mobile version if you want, but that is obviously not what I'm talking about here.

Dpo you agree the One Brow is knowledgeable enough to distinguish being a different game from having different code?
I agree that One Brow is mistaken if he is trying to say that it has to have identical coding in order to be considered the same app. Lol, that is not how it works at all. Hint: Rock Band on Xbox is absolutely the same game as Rock Band on PS3.
 
Well respond to this one then. Do you agree with One Brow that Rock Band on Xbox is a different game than Rock Band on PS3 just because the game won't play on the other platform?

But let's drop the analogies. What the hell are we talking about here?
 
But let's drop the analogies. What the hell are we talking about here?

That's not an analogy man, lol. One Brow is arguing that any app that doesn't have an identical coding is a different app, regardless of look, functionality, etc.

He specifically said the Wii version of Rock Band was a different game than the Xbox version because it won't play in the Xbox. I am arguing that they are different versions of the same game.

This isn't an analogy, it's the actual debate at this point
 
That's not an analogy man, lol. One Brow is arguing that any app that doesn't have an identical coding is a different app, regardless of look, functionality, etc.

He specifically said the Wii version of Rock Band was a different game than the Xbox version because it won't play in the Xbox. I am arguing that they are different versions of the same game.

This isn't an analogy, it's the actual debate at this point

Exactly.
 
That's not an analogy man, lol. One Brow is arguing that any app that doesn't have an identical coding is a different app, regardless of look, functionality, etc.

Except, I'm not in the sense you are using app (some generalized set of features). I'm saying that thew stored code is different, the programming is different, so the implementation of the app is different. It's a different app, in implementation. Comparing the use of one implementation to another is comparing apples to oranges.

The definition of "the same app"

Unless you quote a source for your definition, you don't really have a basis for such pronouncements.

If you are going to the same place and you get there faster, that is all that matters. You keep arguing that you can carry more weight, so that somehow means you got there faster.

Exactly. I'm faster than Carl Lewis. It takes him about ten seconds to run around a circle of 100 meters, I can go directly to the finish line that's 100 inches behind us in well under two. I'm five times faster.

And if you give each 10 transactions, the smartphone does it faster.

Show me the benchmarks that say that. Frankly, I don't believe you. I think you made that up on the spot, with no evidence at all.

You are wrong. You're opening the same exact webpage on both. You can set chrome to open a mobile version if you want, but that is obviously not what I'm talking about here.

I recall Jason had to work on a mobile version of this site for a little while. Perhaps I misremembered.
 
Except, I'm not in the sense you are using app (some generalized set of features). I'm saying that thew stored code is different, the programming is different, so the implementation of the app is different. It's a different app, in implementation. Comparing the use of one implementation to another is comparing apples to oranges.
The implementation is not different, and not all of the programming is different either.

Unless you quote a source for your definition, you don't really have a basis for such pronouncements.
I showed that the courts agreed with me, in several examples. I also have the example of Google saying they are different versions of the same browser. I also listed Rock Band on Xbox, PS3, and Wii. How many sources do you need? Lol, your turn to list even one that agrees with your definition.

Exactly. I'm faster than Carl Lewis. It takes him about ten seconds to run around a circle of 100 meters, I can go directly to the finish line that's 100 inches behind us in well under two. I'm five times faster.
If Carl Lewis was required to run further than you, then you would have a point. In that case, you would probably constantly beat him to the finish line.

Show me the benchmarks that say that. Frankly, I don't believe you. I think you made that up on the spot, with no evidence at all.
Do you even know what ARM is? Are you aware of the history of RISC? If Microsoft didn't have a deal with Intel, most computers would already be ARM based. Even Apple computers were RISC until they gave up and signed with Intel a few years ago (for business reasons, not performance reasons). Check this out:
https://www.cnx-software.com/2012/0...da-energycore-ecx-1000-vs-intel-xeon-e3-1240/

Heavy server benchmarks show a 1.1 GHz ARM processor having almost the same "power" as a 3.3 GHz Intel Xeon. When rating it at performance per watt, the ARM was 15x more "powerful" than the Xeon.

I recall Jason had to work on a mobile version of this site for a little while. Perhaps I misremembered.
No, Jason didn't "have" to create a mobile version in order for smartphone users to be able to access the site. I think you are confused by a few things, let me try to clarify.

1: Smartphones can display either full webpages or mobile versions. You set the browser how you like it. The smartphones of today have no problem displaying full webpages. The smartphones from several years ago weren't as good, and some sites had problems on some devices.

2: There is a very popular smartphone app called Tapatalk that is much better for message boards than a browser. I won't go into why it's so much better than a web browser, but I'll just say it is a whole lot better. What you recall Jason doing was making this site compatible with that app. Please note that when Jason did that, I had already been accessing this site on my phone for several years. It wasn't required that he do that, it just made it better for those of us that use that particular app. It has absolutely no effect on how a browser accesses or displays this website.
 
The implementation is not different, and not all of the programming is different either.

If any of the programming is different, the implementaiton is different.

I showed that the courts agreed with me,

Please link to the court definition of "the same app".

Lol, your turn to list even one that agrees with your definition.

I have a definition for "the same app"?

If Carl Lewis was required to run further than you, then you would have a point. In that case, you would probably constantly beat him to the finish line.

So, according to you, I'm faster than Carl Lewis. OK.

Check this out:

Your link said ARM was slower.

having almost the same "power"

AKA less power.

1: Smartphones can display either full webpages or mobile versions. You set the browser how you like it. The smartphones of today have no problem displaying full webpages. The smartphones from several years ago weren't as good, and some sites had problems on some devices.

OK. Smartphones are faster loading mobile versions. Agreed.
 
Actually, SawltyDawg has argued so masterfully, that I will concede the argument here.

He has me completely convinced that smartphones are faster than destop browsers, in the same manner in which I am faster than Carl Lewis.

I am completely convinced that smartphones process things faster, in the manner of taking 20% longer to process information.

I am completely conviced that smartphones are doling this using the exact same code, in the manner a court of law said the underlying design of the applicaiton was the same.

No reasonable person could possibly dispute any of that. Therefore, I must concede.
 
Actually, SawltyDawg has argued so masterfully, that I will concede the argument here.

He has me completely convinced that smartphones are faster than destop browsers, in the same manner in which I am faster than Carl Lewis.

I am completely convinced that smartphones process things faster, in the manner of taking 20% longer to process information.

I am completely conviced that smartphones are doling this using the exact same code, in the manner a court of law said the underlying design of the applicaiton was the same.

No reasonable person could possibly dispute any of that. Therefore, I must concede.

You forgot to concede that ARM is more efficient. x86 is all over the place, but ARM is like BAM!
 
Actually, SawltyDawg has argued so masterfully, that I will concede the argument here.

He has me completely convinced that smartphones are faster than destop browsers, in the same manner in which I am faster than Carl Lewis.

I am completely convinced that smartphones process things faster, in the manner of taking 20% longer to process information.

I am completely conviced that smartphones are doling this using the exact same code, in the manner a court of law said the underlying design of the applicaiton was the same.

No reasonable person could possibly dispute any of that. Therefore, I must concede.

Smartphones do load the same webpages as desktop computers. You can choose to load a mobile version if you want, or you can load the full version. And if you aren't aware of this, then you should either brush up on your skills or get out of the I.T. business.

As I said in the first place, someday you will get a smartphone and wonder how you ever got by without it (after your grandkids show you how the blasted thing works).

Speaking of being completely convinced, I'm completely convinced that you were lying when you said you worked in I.T. And anyone who reads this thread and knows anything about it, whether they agree with me on any other point or not, will also believe you lied about that. You're confused about basic things that any I.T. pro would know inside and out (not knowing how fast a 10/100 switch moves data? Thinking different versions of the same app are actually different apps? Thinking smartphones are not capable of loading full web pages and mobile versions are required?).
 
Last edited:
Smartphones do load the same webpages as desktop computers. You can choose to load a mobile version if you want, or you can load the full version. And if you aren't aware of this, then you should either brush up on your skills or get out of the I.T. business.

As I said in the first place, someday you will get a smartphone and wonder how you ever got by without it (after your grandkids show you how the blasted thing works).

Speaking of being completely convinced, I'm completely convinced that you were lying when you said you worked in I.T. And anyone who reads this thread and knows anything about it, whether they agree with me on any other point or not, will also believe you lied about that. You're confused about basic things that any I.T. pro would know inside and out (not knowing how fast a 10/100 switch moves data? Thinking different versions of the same app are actually different apps? Thinking smartphones are not capable of loading full web pages and mobile versions are required?).

I can squash ants with my moped faster than I can in a Bugatti.
 
You're confused about basic things that any I.T. pro would know inside and out ...

I don't work in networking or front-end programming. I work in database design. I'm quite competant b-tree indexsing, fifth normal form, the relative advantages and disadvantages of embededed SQL versus sotred procedures, etc. I have yet to meet a network engineer or front-end programmer who understands these things (although I am sure some exist).

As I said in the first place, someday you will get a smartphone and wonder how you ever got by without it (after your grandkids show you how the blasted thing works).

Don't hold your breath. I've seen mjy wife and kids use them. There is no attraction for me.
 
Back
Top