The diffuse part got me puzzled - the beam is one degree wide and works over 50m distance so it can't be diffuse. The camera flash is way more powerful than 75W but due shortness of the pulse not very energetic. The article did not mention anything about flashing light.
They drift because they move and fast relative to ground based clock. At those speeds the drift or time traveling predicted by special relativity becomes noticeable. Even our peaceful corner of the universe is a crazy place to be:)
Even with absolutely precise clocks we would have to count in relativistic effects. The satellites move relative to ground based clock at significant speed and that will cause them to travel in time by microscopic amounts.
I might not need math for programming but I definitely need math to understand what I'm programming. Tasks from game development to automation can not be completed without understanding basic math (we'll they can.. but in order to do them properly some understanding is necessary).
The probable root of this error is that there are two types of calories - gram calories (written with small c) and kilogram Calories (written with capital C).
Jokes aside tho - if you task 1000 teams with a task one of them is bound to come up with something that looks cool (even if it really doesn't work). The plane might be like my android phone - it has really great specs but can't make use of it. In case of my phone it has awesome GPU but there aren't many apps on my phone that would take full use of it.
I completely agree with you - there are processes that no money in the world can speed up.
Because writing a goog GUI requires different skill/toolset. Requirements for user interfaces have changed over time - 30 years ago requirement was "it has to work", 20 years ago "it also has to be simple" and since 10 years ago "it also has to look good".
The first requirement is fundamental - app that does not work is useless. The second requirement is related to usability. The third requirement is for "perceived quality" - windows, mac os, ubuntu, iOS, WP7 and android all have distinctive user interfaces and users can tell if an app looks out of place.
Modern user interfaces are designed by designer using photoshop/expression studio/illustrator/etc (hence the different skill/toolset). While I still have to design user interfaces for my programs I can't jump between code and designer as it will have an effect on code/design quality.
Anyways - i'm here to share my experience not to give a lecture. I bet there are completely orthogonal experiences that are also valid:)
Apple faces fierce competition from Steam. Valve has almost unbelievable sales. Last Christmas they sold indie packs with 93% discount - to put it into perspective: they took a pack of 5 indie games and made 50% discount and then again 50% and again 50% and finally 44% discount. I wish I could buy a house with such a discount.
I do think this specific topic is very relevant and he has valid arguments. The H.264 is an established standard and has industry support while WebM is only supported by Google and is inferior format.
Coincidentally the nexus s is also made by Samsung. If you care about openness and buy Nexus S you only reinforce the Samsung strategy by funding its mobile department.
Disclaimer: I own the Nexus S and don't feel bad about it. Maybe I don't care about openness so much.
The problem is not that hardware is too slow to do it - original iPod touch is much slower than Nexus S - but it's because business logic and UI update are in same thread. No JIT or dual core processor will make the problem go away.
Microsoft and Apple are using retained mode graphics - app describes what's on screen and drawing is taken care by asynchronous process or GPU. After an animation is dispatched the app itself may suspend if it wants but the animation will complete without an hitch.
Android is using immediate mode graphics meaning the app must draw every line on screen and if app pauses the animation also pauses. Implementing the draw commands in GPU (as suggested by Roman Guy from android team) does not help to solve the problem because (even if it makes the draw commands faster) when app pauses there won't be any draw commands.
No amount of hardware will fix the problem that android is facing, current hardware is way faster than needed for silky smooth UI.
I'm not really sure but I believe android is using immediate mode graphics for 2D while iOS and WP7 are using retained mode graphics. The advantage of retained mode is that GPU deals with drawing the screen and processor does not have to deal with it meaning that if app is blocked by garbage collector an animation may continue.
OpenCL is using GPU for tasks that are normally done by CPU. The problem at hand is exactly opposite: CPU is doing stuff that GPU should do. OpenGL is the solution.
I believe the original answer to "java in handhelds" is "java is safe". Back when running apps on your cell phone (and color screens and polyphonic ringtones) was a novel idea the phone makers were afraid of runaway apps. I still believe that security is the original reasoning why apple did not allow third party apps on iPhone at the beginning and only opened tightly controlled store a year later - it's an alternative to java. Now there's more politics than technical reasons. I can be wrong tho.
Unfortunately most of the results in science are hidden behind paywall and the data from most apparatus is not publicly available. I don't even have access to my own publications not to mention others - how would I know if anyone else has already made discovered what I am researching?
Slashdot Mirror
Nope; just Athens that is in Georgia that is in America.
Europeans find it amusing that Athens is in Georgia.
The diffuse part got me puzzled - the beam is one degree wide and works over 50m distance so it can't be diffuse. The camera flash is way more powerful than 75W but due shortness of the pulse not very energetic. The article did not mention anything about flashing light.
How is it different from looking into a laser?
They drift because they move and fast relative to ground based clock. At those speeds the drift or time traveling predicted by special relativity becomes noticeable. Even our peaceful corner of the universe is a crazy place to be :)
Even with absolutely precise clocks we would have to count in relativistic effects. The satellites move relative to ground based clock at significant speed and that will cause them to travel in time by microscopic amounts.
An earthquake may take out the clocks the GPS satellites are synced against.
The browser might be faster but I hate the way android changes page layout during zooming.
I might not need math for programming but I definitely need math to understand what I'm programming. Tasks from game development to automation can not be completed without understanding basic math (we'll they can.. but in order to do them properly some understanding is necessary).
The probable root of this error is that there are two types of calories - gram calories (written with small c) and kilogram Calories (written with capital C).
In china, 900 women can make a baby in a day.
Jokes aside tho - if you task 1000 teams with a task one of them is bound to come up with something that looks cool (even if it really doesn't work). The plane might be like my android phone - it has really great specs but can't make use of it. In case of my phone it has awesome GPU but there aren't many apps on my phone that would take full use of it.
I completely agree with you - there are processes that no money in the world can speed up.
Because writing a goog GUI requires different skill/toolset. Requirements for user interfaces have changed over time - 30 years ago requirement was "it has to work", 20 years ago "it also has to be simple" and since 10 years ago "it also has to look good".
The first requirement is fundamental - app that does not work is useless. The second requirement is related to usability. The third requirement is for "perceived quality" - windows, mac os, ubuntu, iOS, WP7 and android all have distinctive user interfaces and users can tell if an app looks out of place.
Modern user interfaces are designed by designer using photoshop/expression studio/illustrator/etc (hence the different skill/toolset). While I still have to design user interfaces for my programs I can't jump between code and designer as it will have an effect on code/design quality.
Anyways - i'm here to share my experience not to give a lecture. I bet there are completely orthogonal experiences that are also valid :)
Apple faces fierce competition from Steam. Valve has almost unbelievable sales. Last Christmas they sold indie packs with 93% discount - to put it into perspective: they took a pack of 5 indie games and made 50% discount and then again 50% and again 50% and finally 44% discount. I wish I could buy a house with such a discount.
Bush might be your opponent but Bin Laden is an active enemy. There's a difference.
I do think this specific topic is very relevant and he has valid arguments. The H.264 is an established standard and has industry support while WebM is only supported by Google and is inferior format.
Nexus S is a Samsung phone.
Coincidentally the nexus s is also made by Samsung. If you care about openness and buy Nexus S you only reinforce the Samsung strategy by funding its mobile department.
Disclaimer: I own the Nexus S and don't feel bad about it. Maybe I don't care about openness so much.
Especially because he is genuinely bright guy. I've been reading hes articles with great interest an as a rule he's an insightful man.
The problem is not that hardware is too slow to do it - original iPod touch is much slower than Nexus S - but it's because business logic and UI update are in same thread. No JIT or dual core processor will make the problem go away.
Microsoft and Apple are using retained mode graphics - app describes what's on screen and drawing is taken care by asynchronous process or GPU. After an animation is dispatched the app itself may suspend if it wants but the animation will complete without an hitch.
Android is using immediate mode graphics meaning the app must draw every line on screen and if app pauses the animation also pauses. Implementing the draw commands in GPU (as suggested by Roman Guy from android team) does not help to solve the problem because (even if it makes the draw commands faster) when app pauses there won't be any draw commands.
No amount of hardware will fix the problem that android is facing, current hardware is way faster than needed for silky smooth UI.
I'm not really sure but I believe android is using immediate mode graphics for 2D while iOS and WP7 are using retained mode graphics. The advantage of retained mode is that GPU deals with drawing the screen and processor does not have to deal with it meaning that if app is blocked by garbage collector an animation may continue.
OpenCL is using GPU for tasks that are normally done by CPU. The problem at hand is exactly opposite: CPU is doing stuff that GPU should do. OpenGL is the solution.
I believe the original answer to "java in handhelds" is "java is safe". Back when running apps on your cell phone (and color screens and polyphonic ringtones) was a novel idea the phone makers were afraid of runaway apps.
I still believe that security is the original reasoning why apple did not allow third party apps on iPhone at the beginning and only opened tightly controlled store a year later - it's an alternative to java. Now there's more politics than technical reasons.
I can be wrong tho.
Unfortunately most of the results in science are hidden behind paywall and the data from most apparatus is not publicly available. I don't even have access to my own publications not to mention others - how would I know if anyone else has already made discovered what I am researching?
He just noted that the frogs were everywhere - you only need to count them for statistics.
Thanks! You gave me hope :)