104 karma · joined November 8, 2012
Take a look on Windows:
Windows XP: hardware mixing
Windows 7: change to software mixing which cause serious latency problem http://www.youtube.com/watch?v=iujDVsg_2xY
Windows 8: http://msdn.microsoft.com/en-us/libr.../br259116.aspx they realize their mistake and go back to hardware mixing again
The only way I was able to solve the cracking and latency issues on my Linux box was to replace ALSA with OSS. Recently some newer software is causing issues again and I might have to give ALSA another shot. Things would be so much better if the Linux kernel just adopted OSS4
With a population of 1.3 billion, I'm not surprised you can "Pick an age — any number — and put “raped” after it in a Google search and see results from India."
Google "Vatican City + raped" You'll find a 9 yr old was raped in the smallest city in the world! The Vatican no less!
Rape happens all over the world. I'd love to see how long this woman lasts on 110 and Broadway in NYC without her "modesty scarf"
My girlfriend is from LA and never stops dressing like it, even when traveling throughout India. From large cities like New Delhi to a little town called Ichhawar, we never had any issues with all these supposed rapists. I'm guessing the reason why is my g/f has perspective and a handle on reality, where Meenakshi probably needs a b/f more than her bottle of pepper spay.
The more you abstract, the more functionality you lose and the more generic your mobile apps will look. Facebook learned this lesson the hard way when they tried to make their mobile App in HTML5.
CSS, javascript, and DOM are just kudge piled upon kludge. HTML5 trying to shoehorn poorly thought out technologies created for hyperlinked static text documents into dynamic applications.
Until some disruptive technology completely replaces that massive HTML5 spec you speak of, the natives apps will always rule the mobile space and performance critical spaces.
Since Firefox OS limits you to running HTML5 apps, the best you can do is create a new skin for Mozilla's browser. The same limitation that iOS imposes on its users.
So basically, with Firefox OS, you're limited to using the Mozilla browser. Sounds like Firefox is trying to lock you into their standards, exactly what they're accusing Apple of doing with the webkit engine in iOS.
Android and Ubuntu Mobile look to be the only solutions that give me the flexibility I want in a phone OS.
It's clear from my own experience, posts here, and benchmarks that Chrome has strayed from it's original design goals of being a lightweight browser. My reference to this iPhone was just to point out that I think it's a issue with Chrome itself, and not the underlining webkit browser.
http://blog.ffextensionguru.com/2011/11/20/electrolysis-proj... Add-on were one of the major issues blocking Multi-process Firefox.
>Not to mention Firefox ate memory like a pig until recently, despite not having sandboxing.
Agreed. Sandboxed Chrome was like a gift from the IT gods back in the bloated FF3 days.
>Now it's somewhat better with post 16 stuff, but still it's slow. Chrome is much more responsive and fast.
Responsive and fast until it starts thrashing when your physical RAM gets all used up.
Before giving up, and switching to FF, I tried the --disable-gpu --disable-software-rasterizer switches to disable the GPU process but that prevented videos from playing at full speed. Some people here mentioned Chrome runs great on their rigs with 16GB of RAM. But for the rest of the world, Google should force their devs to use Chrome on a machine with a mere 2GB.
How is it that sites like anandtech and investing.com run fine on my old iPhone 3GS, yet take up 256+ MB in Chrome, more RAM than the phone has? Somehow the 3 year old phone loads and displays the sites smooth as butter. Apple is doing something right or Google is doing something terribly wrong to webkit.
Before giving up, and switching to FF, I tried the --disable-gpu --disable-software-rasterizer switches to disable the GPU process but that prevented videos from playing at full speed.
If you want to contribute back, Google has been good about accepting patches into its AOSP project. For patches they won't accept, there's always CyanogenMod.
"JS engines are pretty fast" Good enough for simple text based apps and casual games, yes. Modern 3D games, not by a long shot. Native code, NDK, or Java under HotSpot are the only decent options creating for modern responsive 3D games.
I had a WebOS phone and despite loving the beautiful UI and it being ahead of iOS in many ways like notifications and task switching, I dumped it. HTML5 killed the user experience. I need fast, responsive apps that only Android and iOS can deliver.
There's no way I'd ever go back to generic, laggy, HTML5 Apps.