In those positions the only way for the device to record accelerations that represent a "whack" is for the car to crash or the wearer to crash. In which case you bet you want the device to auto pick up and give you a chance to an early response rescue.;-)
There is no reason why one would need an additional layer of abstraction to implement such a thing. That's why Firefox OS is even possible. You just get rid of all the java, replace it with a nice js compiler and of you go. So instead of having to write a java vm for each new architecture, device devs just implement the compiler onto it.
Not new but unfortunately it deals with tech that is sufficiently advanced to be indistinguishable from magic by an uneducated observer. Or in this case the tech involved could be perceived as non obvious by a patent judge.
Some might even argue that every sharp acceleration while in an alarm state could be classified as a whack. Since the operator is in the state of directly moving the device he is aware of the alarm.
We need an OS which does not inject two additional abstraction layers between a webpage/app and the hardware. So yes Android sucks now and it will keep sucking in the near future.
IMHO chrome has become too much of a behemoth. I'd migrate them to Firefox. A fresh OS with chrome on a 7 year old laptop grinds to a halt on the first page. The same setup is perfectly usable with an up to date Firefox
Most of the videos uploaded to youtube now come from phones or tablets
Phones yes, tablets not so much. Also, that is most as in number of submissions. The most stuff as in the stuff you watch by the millions and accounts for the 90% of video views is still shot on DSLRs and Pro Cinematography gear.
Also, nobody does real work on smartphones and tablets atm.
TBH I do not think that your average Linux distro, except maybe Ubuntu, entertains the concept of making a "bold release" and in one move lure millions of new users to their platform.
It's people like the guy you replied to that actually do the biggest disservice to projects like the Linux desktop.
Adaptability is key to progress. Every single electronic device I have had came with a minutely or largely different interface. What? Did I throw my hands up in the air and cry foul just because my new dishwasher got a rotating knob (or touchscreen) as well as the buttons it already had? No. Every `new` device you get (and here new reads as progress, not just a next season's sequel) will have different conventions/experience than the device(s) it replaces.
Stop excusing people for being learn-shy and tell them to finally man up (or that relevant girl thing) and learn to adapt to progress!
Fitts' law is correct. What it means for global menus is that they are completely wrong and not helpful to productivity. window menu bars are useful on the window for one reason: When you need them, typically, your pointer is already on the window (ergo: much less distance to travel for same size target)
One design decision that might have steered towards the global menu bar (in 1999?) was that it would generate a much cleaner UI/window presentation. Plus the side effect that users that were clueless would find it more difficult to accidentally switch on some "pro" feature through the window menu when it is located on the far top left corner.
To be fair about the Gimp thing, the guy was trying to run an extended life OS and install the latest and greatest. Such a thing usually needs a lot of skill (and probably hacking on sources). On Linux you have four main ways of doing things: 1. You live on the bleeding edge, update religiously and cautiously at least once a month and reap the benefits of eternally fresh binaries and deal with the fear that one day you will update something that will irrecoverably break your system (which doesn't actually happen, making these kinds of distros actually stable too). aka the Gentoo, Arch way 2. You live on the sta(b)le end and are happy with what software you have got (getting some limited wiggle room on newer versions) and the fact you probably won't have to sacrifice a day because some haywire kernel dependency tainted your ramdisks and made your precious desktop unbootable for a short time. 3. You install a common man's distro and shut up. 4. You roll your own OS from sources and keep your software updates manual and based on personal preference/beliefs, in which case good luck.
Running stale but half bleeding edge is not a thing most Linux users could pull off.
Ok, I do not know about IS{ in the us but: You can't "`not'" install war. at least not until the `almost educated` idiots that govern the world give credence to the fat that data on an Inter-net is Public domain. And with data I mean every single bit that is there.
Slashdot Mirror
In those positions the only way for the device to record accelerations that represent a "whack" is for the car to crash or the wearer to crash. In which case you bet you want the device to auto pick up and give you a chance to an early response rescue. ;-)
There is no reason why one would need an additional layer of abstraction to implement such a thing. That's why Firefox OS is even possible. You just get rid of all the java, replace it with a nice js compiler and of you go. So instead of having to write a java vm for each new architecture, device devs just implement the compiler onto it.
I have no idea about windows. Sorry.
Also the best way to measure a browser's responsiveness is after you have done a bit of work and expanded your session to more than ten tabs.
Startup times are pretty much irrelevant.
Not new but unfortunately it deals with tech that is sufficiently advanced to be indistinguishable from magic by an uneducated observer. Or in this case the tech involved could be perceived as non obvious by a patent judge.
Very acute.
Some might even argue that every sharp acceleration while in an alarm state could be classified as a whack. Since the operator is in the state of directly moving the device he is aware of the alarm.
Also you can go the data crunch way and just train a device to recognize your whacks with a support vector network.
What? You mean Software Patents actually slow down technological progress and induce price inflation due to licensing overhead?
No news here folks, keep moving....
It's laughable. Not to mention that there is prior art. Humanity has been whack silencing things since we had opposable thumbs!
That depends. Do you want the device to do anything interactive?
No, Chrome is a behemoth. In my recent experience Basic Firefox is more responsive and more efficient across all hw configs you can do.
Hmm... Interesting. I don't get this experience on arch.
OMG!!!! ACs are getting all over my posts pulling fantasies out of their behinds! The end of the world must be here!
We need an OS which does not inject two additional abstraction layers between a webpage/app and the hardware. So yes Android sucks now and it will keep sucking in the near future.
I don't get it. You are implying that Firefox is bloated? Firefox is the leanest browser there is atm.
My guess is that IE8 users will just get a huge chrome browser ad when their support gets cut of.
IMHO chrome has become too much of a behemoth. I'd migrate them to Firefox. A fresh OS with chrome on a 7 year old laptop grinds to a halt on the first page. The same setup is perfectly usable with an up to date Firefox
Most of the videos uploaded to youtube now come from phones or tablets
Phones yes, tablets not so much.
Also, that is most as in number of submissions. The most stuff as in the stuff you watch by the millions and accounts for the 90% of video views is still shot on DSLRs and Pro Cinematography gear.
Also, nobody does real work on smartphones and tablets atm.
TBH I do not think that your average Linux distro, except maybe Ubuntu, entertains the concept of making a "bold release" and in one move lure millions of new users to their platform.
It's people like the guy you replied to that actually do the biggest disservice to projects like the Linux desktop.
Adaptability is key to progress. Every single electronic device I have had came with a minutely or largely different interface. What? Did I throw my hands up in the air and cry foul just because my new dishwasher got a rotating knob (or touchscreen) as well as the buttons it already had? No. Every `new` device you get (and here new reads as progress, not just a next season's sequel) will have different conventions/experience than the device(s) it replaces.
Stop excusing people for being learn-shy and tell them to finally man up (or that relevant girl thing) and learn to adapt to progress!
That is just like saying "give the hungry people their fish".
We as a species will never go forward if all our smartest do is just cater to our immediate needs!
Please stop supporting that plainly xenophobic argument and face the fact that people need to embrace adaptability.
Fitts' law is correct. What it means for global menus is that they are completely wrong and not helpful to productivity. window menu bars are useful on the window for one reason: When you need them, typically, your pointer is already on the window (ergo: much less distance to travel for same size target)
One design decision that might have steered towards the global menu bar (in 1999?) was that it would generate a much cleaner UI/window presentation. Plus the side effect that users that were clueless would find it more difficult to accidentally switch on some "pro" feature through the window menu when it is located on the far top left corner.
To be fair about the Gimp thing, the guy was trying to run an extended life OS and install the latest and greatest. Such a thing usually needs a lot of skill (and probably hacking on sources).
On Linux you have four main ways of doing things:
1. You live on the bleeding edge, update religiously and cautiously at least once a month and reap the benefits of eternally fresh binaries and deal with the fear that one day you will update something that will irrecoverably break your system (which doesn't actually happen, making these kinds of distros actually stable too).
aka the Gentoo, Arch way
2. You live on the sta(b)le end and are happy with what software you have got (getting some limited wiggle room on newer versions) and the fact you probably won't have to sacrifice a day because some haywire kernel dependency tainted your ramdisks and made your precious desktop unbootable for a short time.
3. You install a common man's distro and shut up.
4. You roll your own OS from sources and keep your software updates manual and based on personal preference/beliefs, in which case good luck.
Running stale but half bleeding edge is not a thing most Linux users could pull off.
Ok, I do not know about IS{ in the us but:
You can't "`not'" install war. at least not until the `almost educated` idiots that govern the world give credence to the fat that data on an Inter-net is Public domain. And with data I mean every single bit that is there.
How you get modded to 1 and 2 is beyond me.
It's called karma bonus.
And medical and television and F1 IIRC.