-
Webkit Browser Caught In Action � BerryReview
New RIM Webkit browser still appears plagued by the same memory issues that RIM reps blamed for the current screen redraw issues that the current browser has. It does appear that all RIM did with this new version is to just implement Webkit rendering capabilities into the existing old and tired browser, which obviously wouldn't have fixed anything else but the rendering capabilities of the webpages being pulled up. Seems the speed is slighly improved, but when hitting Crackberry, it's still VERY slow... must slower then what other current-gen smartphones can do.
Again... RIM... too little, too late. This is what the browser experience should have been when the S1 came out almost 2 years ago. But, in the tradition of RIM... they have certainly not let us down with this one either, since they're always last to the party and always bring a "re-gift".
Only positive I have to say about it... thanks for the pinch-zoom capabilities. Not put that in the HTML email rendering engine in OS6 and you'll impress me.
07-10-10 09:58 AM - Altough its still early, and its only been one video we've seen I'm generally impresses with the new browser, I had kept my expectations pretty low
As for using the rendering engine in e-mail it would make sense, Mike Lazaridis hinted at it at WES:
Source: http://crackberry.com/rim-founder-mi...ay-os6-0-cominWebKit clarification - Mike L. clarified that the WebKit browser is an integrated part of OS 6.0. It's not a standalone app (you won't be able to install the WebKit browser on OS 5.0 for example). He further elloborated saying that it's not really a "webkit browser" but a WebKit rendering engine, which can be/is leveraged in areas/apps beyond just the browser.07-10-10 10:05 AM - Yeah, I know about that "hinting". That's why I'm hoping they actually did it because a big gripe for me now is also the quality of HTML email rendering the fact that I can't zoom in to see the details contained within pictures that someone pasts into the body of an email. (Think screen prints of issues that people paste into emails and ask "What does this mean?" I can't answer the question while on the road because I can't see the damn pic clearly enough to read the error message or whatnot. Pinch-zoom and better HTML rendering in email would GREATLY improve email on a BB in my opinion.)
Oh, and one last thing. I'm tired of the same old "And please remember that this is an early version..." BS excuses. We all know the same line has been used before about OS version or something else on BB and when it finally released, it wasn't any better. So, I don't see that as a valid excuse anymore on anything BB related. It is what it is... once it's out, it seems improvements can be made, but there is either always a tradeoff or some kind of "kick in the nuts" change that breaks something else that should have been left alone to begin with (i.e. swipe up on the Storm keyboard
). So, I guess what I mean by that is, I wouldn't put it past RIM to get rid of kenetic scrolling in the browser to fix the screen redraw issue, etc. I'm not saying this is what will happen, but just saying that RIM's always had to take something away to fix another issue, it's a constant compromize with the BBOS. It's never as easy or simple as "Let's just fix the issue at hand and leave everything else as is since it's working and people like it." Somehow that idea doesn't compute for RIM and its engineers.Last edited by JRSCCivic98; 07-10-10 at 10:16 AM.
07-10-10 10:10 AM - She's right. I'm tired of the old beta product excuse.
Apples developers wrote OS4 and then released it to production immediately. They are so good they didn't have to test it.
Google wrote the android operating system and then released it to production without testing a line of code. Yes, they are that good.
Microsoft/Oracle/IBM developers write major operating systems and infrastructure products without testing. They are good at their jobs also.
Aerospace companies can design/build/deploy their aircraft without testing anything.
RIM developers need a refresher course. They obviously suck and don't know what their doing? The code and methods requires testing and constant rework and patches. They ought to learn a lesson from the big guys who write fast/defect free code the first time, that never has to be patched.
07-10-10 10:42 AM - You can't be serious. I mean, you seriously think either of the companies mentioned simply write their code and release it directly to the public? You've got to be kidding me. Didn't happen and never will.She's right. I'm tired of the old beta product excuse.
Apples developers wrote OS4 and then released it to production immediately. They are so good they didn't have to test it.
Google wrote the android operating system and then released it to production without testing a line of code. Yes, they are that good.
Microsoft/Oracle/IBM developers write major operating systems and infrastructure products without testing. They are good at their jobs also.
Aerospace companies can design/build/deploy their aircraft without testing anything.
RIM developers need a refresher course. They obviously suck and don't know what their doing? The code and methods requires testing and constant rework and patches. They ought to learn a lesson from the big guys who write fast/defect free code the first time, that never has to be patched.07-10-10 10:58 AM - This is the most dumbest post I seen so far. Get real.She's right. I'm tired of the old beta product excuse.
Apples developers wrote OS4 and then released it to production immediately. They are so good they didn't have to test it.
Google wrote the android operating system and then released it to production without testing a line of code. Yes, they are that good.
Microsoft/Oracle/IBM developers write major operating systems and infrastructure products without testing. They are good at their jobs also.
Aerospace companies can design/build/deploy their aircraft without testing anything.
RIM developers need a refresher course. They obviously suck and don't know what their doing? The code and methods requires testing and constant rework and patches. They ought to learn a lesson from the big guys who write fast/defect free code the first time, that never has to be patched.Last edited by blazed12; 07-10-10 at 11:43 AM. Reason: whoops?
07-10-10 11:42 AM
