Archive for: javascript
If you aren’t the type to follow Pwn2own and the various trickery that the contest caters to, you should. It is there that some of the world’s most talented hackers crack their way into the gadgets we love and use every day, ultimately making our lives (and gadgets) safer and more secure. However, part of that added safety is dependent on the hardware manufacturers and mobile OS developers actually implementing fixes for said hacks in a timely manner. With that said, RIM’s response to the recently exploited BlackBerry browser on OS version 6 is hardly reassuring — they recommend you completely disable Javascript to stay safe. Seeing as how countless web forms, login forms, and general web browsing overall requires some level of Javascript, this pretty much ruins your whole mobile browsing experience. Add in the fact that RIM isn’t the fastest with OS upgrades/updates (and carriers are even slower to approve and push out said updates) and you’ve got a problem brewing for BlackBerry users.
RIM has the ability to push upgrades OTA themselves. Seeing as how this would be a relatively small update, now more than ever RIM should take advantage of the included feature to keep BlackBerry users’ mobile browsing experiences up to par. BlackBerry users: Thoughts?
On a slightly more optimistic note veering away from the UK Government’s decision to stick with the overly beaten dead horse that is IE6, we share the good news that IE9 is one step closer to release. For today, (actually it was later yesterday) Microsoft has officially taken the wraps off of the latest “Final” Preview of IE9.
The latest release still intended more for developers, has it conquiring Apple’s Safari web browser in SunSpider benchmarks as well as almost netting a perfect 100% on the hallowed Acid 3 test. (Come on MS, you still can’t manage 100% on a test that’s over a year old?) Though, I’m sure as the browser moves into the beta stage we’ll see even more tweaks made in the name of improving performance. Still, by the time IE9 is released later this year, Chrome will be nearing double digit numbers (based on new 6-week major update cycles) and Firefox 4 will be legit. With two big browsers receiving substantial updates at far shorter intervals, it looks like Microsoft will be forever playing catch-up.
Whataya think: Will IE9 be relevant?
One of Apple’s routine talking points of their mobile Safari browser is just how fast it is, often citing Javascript performance as a good indicator. Yesterday however, several sites started running with a story showing that Android 2.2 (Froyo) and the Nexus One in particular downright stomp on iOS 4 when it comes to Javascript.
But more than two can tango at this game. MeeGo may not be widely available (hell, a lot of people probably haven’t the slightest idea what it is), but that doesn’t mean it can’t throw down a beating of its own.
Granted, the MeeGo phone in question is a prototype Moorestown device running mobile Firefox. So the “stock” nature of this claim is somewhat iffy. But either way, it’s nice to see the competition going at it hard and fast, no?
Steve Jobs may be doing his damnedest to keep Flash out of the iPhone by way of App Store regulations, but there’s one thing he can’t cripple — the browser. And that’s precisely where “Smokescreen” comes in — a 175KB, 8,000-line javascript-based Flash player…
Good god, potatoes. Can you believe it! When we talk browser speed tests, it usually entails multiple passes of Javascript benchmarks that show just how much muscle a particular browser has. But leave it to Google (the one’s with the now somewhat infamous gamut of job applicant questions) to truly think outside of the box. Instead of the normal, plain jane benchmarks, the Google Chrome team used more “real-life” examples and took it up another notch thanks to the use of 2700fps slo-mo cameras. Oh yeah — it’s nerdy and super awesome. Click your way inside and give it a watch…
Generally speaking, pushing your hardware past it’s “factory limits” is seen as a big no-no by the manufacturer. It makes sense though. If the manufacturer only tests the hardware between variables 1-10 and you take it to 13, anything negative happening rests solely on your shoulders. With Palm’s announcement today, speaking against users going down the 800MHz kernel overclocking route, I can say I honestly see both sides of the story. Yes, overclocking is bad news if you care about the warranty. At the same time, it makes the Pre enjoyable for the tech inclined few curious (and brave) enough to venture down the OC route.
The fact of the matter is, Palm is doing the right thing here by playing it safe and merely “suggesting against” overclocking. The worst thing they could do would be to go all Apple on the ever talented developer community and seek to constantly block/outlaw overclocking and other hardware/software related hacks. It is those hacks alone that are keeping the webOS platform alive and relevant. The only reason such crackdowns work for Apple is because they appeal to such a mass populous. Palm does not.
Frankly, Palm should take any and all sales/press/hacks with stride. They’re not exactly in the position to be choosey with whom they “allow” to own their devices and what they allow said users to do with those devices. Just don’t go crying to Palm when your 800MHz Pre+ melts into a brick Albeit a nicely rounded, sculpted brick.
PhoneArena
- December 17, 2009 1:44 pm
The App Store is for mobile devices what iTunes was for mp3 players. Apple’s 180 on native applications after first announcing web apps were the way to do back in 2007 was a shock to many and welcomed by most. Since the App Store’s launch however, numerous complaints have been made and even websites created to highlight Apple’s draconian and sometimes senseless decisions concerning the App Store and polices within. It is that negative image and bad press that has re-energized the view of many iPhone devs into the world of web apps.
Wait a second. Weren’t web apps poo-pooed because they were inferior to native apps back in ’07? Why yes, yes they were. Don’t forget however that the mobile market has undergone some vast changes over the last year and a half. Not only has the mobile app world changed in regard to the limits mobile apps could obtain but also in the technologies used for said apps. Like their native cousins, web apps and the supporting technology have equally improved.
We are now at a point where tools such as “PastryKit” allow web developers to code and create webapps that feature some of the most desktop/native-like style and features yet, blurring the line between what is native and what is web. Right about now you’re probably asking yourself what the heck PastryKit is. Allow me to indulge…
PastryKit
- PastryKit is an innovative and constantly improving set of tools allowing web apps. A blend of multiple technologies and languages including JavaScript, CSS, and some supporting graphics resources ensures the new generation of web apps is more robust, functional, and visually appealing. Need an example? If you own an iPhone, simply navigate to support.apple.com/manuals/iphone/ and notice the iPhone optimized manual that loads. Said manual relies on — you guessed it — PastryKit.
For now, consumers will have to wait it out or figure out the workings of PastryKit themselves as Apple hasn’t released the necessary information and source material to include PastryKit in any non-Apple/3rd party solutions. Such an approach has to at least have to do in some part with preventing App Store devs an easy out from App Store restrictions by way of open and free web apps powered by PastryKit. Still, those with the know-how will figure it out soon enough and spread the knowledge to others.
I’m not a developer so I couldn’t begin to explain the pros and cons to each method being used, but if any developer — native or web — want’s to speak up and give some insight into this hotly debated topic, feel free to jump in.
Ars Technica
- September 22, 2009 9:23 pm
So your corporate IT policy requires you to use the ever popular though web standard deficient and downright pokey IE? Well, now’s your chance to give them the sly finger and have the last laugh. Google has released a rather clever little plugin for IE that will allow you to run Google Chrome 3 inside a frame within IE. The IE Google Chrome Plugin allows IE to make use of a whole host of open source technologies with one of the more popular goodies being HTML 5. Of course, IE isn’t really doing any work as it is again a full fledged version of Chrome running inside a frame.
On the developer end, adding a simple X-UA tag will allow the IE Trident rendering engine and the Google Chrome webkit engine to the tango peacefully with IE bowing out when said tag is read in giving rendering control to the far superior webkit beast within. While all of the high tech stuff that goes on behind the scenes is hardly high tech, the efficiency and peace of mind it brings to web developers and end users a like is enough reason to install the plugin. On one side you’ll get dramatically improved javascript performance, an actual web standards compliant browser, and an overall speed boost. On the other side, your IT department will be all the merrier knowing you’re still rockin’ their browser of choice.
Gizmodo > Ars Technica
