Yeah, ping is a issue. A very large one. And if this goes on ahead, its going to be the nr 1 issue. Now, it would not surprise me that the bandwidth could be good, but even then, ping is a big issue.
Wikipedia claims "Minimum 200km/h as normal speed, for European Union Directive 96/48/EC, Annex 1". So that is what the term means. As a Norwegian, I do know that we would not be familiar with the term either, since most Norwegian trains operate with a speed limit of 80-90km/h due track speed limit.
I am not sure who in their sane mind, writes such a poorly paced 2 page article. I am sure its up to journalistic standards, but please, learn how to cut it down. Its far too long for something thats essentially "This is a thing, this is the company, and this is how it works, and this was my experience with this thing". Especially when you forget to talk about the third and fourth point.
"No" is a quite rude word. And you can still weasel ways to say "No" to not directly mean No. And then you have a problem. Its also over email, at which the point comes: Email is not verbal communication. It has a large set of features real speech has not, and a large list of features real speech has that email does not. And being sublte or conveying something, without directly stating it, can not be done on email.
Yes. Specs do matter. If the hardware is bottlenecked in anything the OS really needs: Anybody remember those CD drives that locks the system IO while attempting to read? Or what it felt like going from a HDD to a SSD? There is also a few slashdot articles about significant app launch gain by using a faster SD card over the internal storage, due shitty design
And yet, the answer should be: No: We should already be past the issue. And software should have solved the issue long time ago. Browsers should almost expect to be used on some of the early Android devices, and then take advantage of any speedup. And more.
You have problems with consistent client behavior over 140 ping. This research document supposedly went up to either 200 or 400, depending on what RTT means. Here is the real problem: What happens if you introduce random packet drop to the system? Over mobile broadband, shitty long line connections, Australias landline, and more, you get packet loss. A small amount with a random amount added. Does this research paper even touch on the subject?
Lets talk about this. I talked about my parents about clothing, and at some point we talked about wear of clothes. Not just mechanically wear, but time. For instance, a lot of t shirts have some form of plastic used to maintain the collar shape. Some string are made out quite degradable materials. Buttons might be made of a material that mis color due time, like SNES machines due oxidation. Socks are made out of materials that wear very fast, in some cases. Sewing might fix a little, but it won't do anything if its keeps on happening.
Have you ever seen the example? XP did a simple thing: Shut down went to the shutdown menu where the choices was. Vista implemented 2 buttons, one which looks like a Lock, the other which is a colored Off symbol. The problem is that its not a off symbol: by default its the hybrid sleep button. Yes something that should look like a bunch of lined up "zzzzzzzzzzzzzzz"s looks like a off button. Its a Microsoft problem.
Well, the thing is, roads do not ban bikes from them. And bikes are obliged to follow much of the same laws as cars, at the least for driving. Not safety.
Yes, once tech gets there. Essentially "google glass like models for manuals". And its not been that long since I played Metal Gear Rising, whatever about the game, but they got their terminology right: AR for manuals would be really nice. VR would likely have no practical use until a genius comes along with a good idea.
Because the controller by design does not need a dpad. It only needs extra buttons in case you run out of practical mapping. You have a left analog zone and haptic feedback on it. And a right analog zone with haptic feedback. Each zone notices the difference between push down and just swiping on the surface. Each zone also has 3 parts, where you can do stuff like map things to the outer and inner edges. So for a lot of 3D games, you would do something like -Left analog is left zone. Outer edge is used as dpad(since dpad is only used for rare commands.) -Right analog is mapped to right zone, but so is the face buttons. Swipe = Move camera, push down = use button. Outer circle is still not used for anything, but can be. -Map bumpers and analogs to the back, just like on the original gamepad setup -Start/menu is start/menu, and select/back is select/back.
For 2D games, you already got a nice primary surface. Just map the "dpad" to the left touch surface, and use push down. And face buttons to the right surface. Its not magic. Its not hard to map the controller to work for a game like Starcraft either, since you can do left zone for panning and right for mouse control. You also have 8 buttons free for control groups.
"Forbidden to speak X on official purposes" is very normal in all countries. Just like any merchant inside their border have to accept the national currency. Usually enforced by law.
Code optimised for the PowerPC processors found in the Xbox 360 and PlayStation 3
Having worked on other hardware consoles, I suppose that we were rather spoilt by having mature toolchains that integrated nicely with our development environment. ----... ---- This doesn't sound bad, but when you are debugging and making lots of changes, these additional times add up. If you made 10 changes to a file in a morning, you could be spending over 50 minutes waiting for the linker to complete, which is a lot of wasted time.
Alarm bells *rings for the wrong reason
Look at it, read it trough. There is several hints that the writer is not a competent developer in quite a few meanings of the word. There is also backtracking of several of the statements. I guess that is what happens when development turns into setting a bunch of third party tools in chain, including the compiler and Visual Studio.
Its sort of obvious. Wireless one could be 2G with extensions. You know what? Browsing internet on that would be slow, but it works if it where not for one major problem: Packet drops. With a guaranteed 20% packet drop(if not more), its painful to use. And with such a low speed, its even worse. It would be unable to even browse slashdot properly.
Slashdot Mirror
Yeah, ping is a issue. A very large one. And if this goes on ahead, its going to be the nr 1 issue. Now, it would not surprise me that the bandwidth could be good, but even then, ping is a big issue.
Somebody mod up.
Wikipedia claims "Minimum 200km/h as normal speed, for European Union Directive 96/48/EC, Annex 1".
So that is what the term means. As a Norwegian, I do know that we would not be familiar with the term either, since most Norwegian trains operate with a speed limit of 80-90km/h due track speed limit.
Even in Russia, all you need is to change the type of tires to use a bike on the winter.
I am not sure who in their sane mind, writes such a poorly paced 2 page article.
I am sure its up to journalistic standards, but please, learn how to cut it down. Its far too long for something thats essentially "This is a thing, this is the company, and this is how it works, and this was my experience with this thing". Especially when you forget to talk about the third and fourth point.
"No" is a quite rude word. And you can still weasel ways to say "No" to not directly mean No. And then you have a problem. Its also over email, at which the point comes: Email is not verbal communication. It has a large set of features real speech has not, and a large list of features real speech has that email does not. And being sublte or conveying something, without directly stating it, can not be done on email.
Yes. Specs do matter. If the hardware is bottlenecked in anything the OS really needs: Anybody remember those CD drives that locks the system IO while attempting to read? Or what it felt like going from a HDD to a SSD?
There is also a few slashdot articles about significant app launch gain by using a faster SD card over the internal storage, due shitty design
And yet, the answer should be:
No: We should already be past the issue. And software should have solved the issue long time ago. Browsers should almost expect to be used on some of the early Android devices, and then take advantage of any speedup. And more.
Who are you even replying to?
More or less this.
You have problems with consistent client behavior over 140 ping. This research document supposedly went up to either 200 or 400, depending on what RTT means.
Here is the real problem: What happens if you introduce random packet drop to the system? Over mobile broadband, shitty long line connections, Australias landline, and more, you get packet loss. A small amount with a random amount added.
Does this research paper even touch on the subject?
Mind to answer quoted post? You failed to do that.
Lets talk about this. I talked about my parents about clothing, and at some point we talked about wear of clothes.
Not just mechanically wear, but time. For instance, a lot of t shirts have some form of plastic used to maintain the collar shape. Some string are made out quite degradable materials. Buttons might be made of a material that mis color due time, like SNES machines due oxidation.
Socks are made out of materials that wear very fast, in some cases. Sewing might fix a little, but it won't do anything if its keeps on happening.
>Game boy
>3D shell for Raspberry Pi to run a emulator
Please don't mix the too together.
Because movie popcorn is sorta like a experience.
Its called "Bad defaults". So please shut up.
Have you ever seen the example? XP did a simple thing: Shut down went to the shutdown menu where the choices was. Vista implemented 2 buttons, one which looks like a Lock, the other which is a colored Off symbol. The problem is that its not a off symbol: by default its the hybrid sleep button. Yes something that should look like a bunch of lined up "zzzzzzzzzzzzzzz"s looks like a off button.
Its a Microsoft problem.
Well, the thing is, roads do not ban bikes from them. And bikes are obliged to follow much of the same laws as cars, at the least for driving. Not safety.
Yes, once tech gets there. Essentially "google glass like models for manuals".
And its not been that long since I played Metal Gear Rising, whatever about the game, but they got their terminology right: AR for manuals would be really nice. VR would likely have no practical use until a genius comes along with a good idea.
You sacrifice shaders that has too many passes or other things that has become the standard.
This.
Because the controller by design does not need a dpad. It only needs extra buttons in case you run out of practical mapping.
You have a left analog zone and haptic feedback on it. And a right analog zone with haptic feedback. Each zone notices the difference between push down and just swiping on the surface. Each zone also has 3 parts, where you can do stuff like map things to the outer and inner edges.
So for a lot of 3D games, you would do something like
-Left analog is left zone. Outer edge is used as dpad(since dpad is only used for rare commands.)
-Right analog is mapped to right zone, but so is the face buttons. Swipe = Move camera, push down = use button. Outer circle is still not used for anything, but can be.
-Map bumpers and analogs to the back, just like on the original gamepad setup
-Start/menu is start/menu, and select/back is select/back.
For 2D games, you already got a nice primary surface. Just map the "dpad" to the left touch surface, and use push down. And face buttons to the right surface. Its not magic.
Its not hard to map the controller to work for a game like Starcraft either, since you can do left zone for panning and right for mouse control. You also have 8 buttons free for control groups.
"Forbidden to speak X on official purposes" is very normal in all countries.
Just like any merchant inside their border have to accept the national currency. Usually enforced by law.
What tipped you off?
Look at it, read it trough. There is several hints that the writer is not a competent developer in quite a few meanings of the word. There is also backtracking of several of the statements.
I guess that is what happens when development turns into setting a bunch of third party tools in chain, including the compiler and Visual Studio.
Its sort of obvious. Wireless one could be 2G with extensions. You know what? Browsing internet on that would be slow, but it works if it where not for one major problem: Packet drops. With a guaranteed 20% packet drop(if not more), its painful to use. And with such a low speed, its even worse. It would be unable to even browse slashdot properly.
Remember, in US versus THEM: You are living somewhere, and the prices escalate from others presence, why the fuck would you move for others fault?
Is this because not having a job forces the people out, or some other reason? That statement is meaningless.