-  [WT]  [Home] [Manage]

[Return]
Posting mode: Reply
Name
Email
Subject   (reply to 578)
Message
Captcha
File
Embed   Help
Password  (for post and file deletion)
  • Supported file types are: 7Z, GIF, JPG, M4A, MID, MP3, OGG, PDF, PNG, RAR, SWF, TXT, WAV, XZ, ZIP
  • Maximum file size allowed is 2097152 KB.
  • Images greater than 200x200 pixels will be thumbnailed.
  • Currently 189 unique user posts. View catalog

  • Blotter updated: 2012-05-14 Show/Hide Show All

File 134021748493.png - (6.35KB , 220x80 , mozilla-firefox.png ) Thumbnail displayed, click image for full size.
578 No. 578
Here's something interesting. Mozilla is going to use Webkit for Apple's iDevices since they can't get Gecko running (due to Apple's insistence on not using competing technology on their devices)

Here's the pasta:
>From the 'Fennec Fail' files:

>For the last four years, every time I've asked a Mozilla person if Firefox was going to come to Apple iOS, the answer has always been no.

>Apple's own restrictive policies will not allow another rendering engine and that means that Mozilla's core Gecko rendering engine is not an easy option. Mozilla is now investigating another route, by building a new browser - codenamed junior.

>Since Marc Andreeson and Netscape, Mozilla and its forebears have always been Gecko based. Junior will be the first Mozilla browser tech to use WebKit.

>WebKit dominates the mobile landscape as the default rendering engine on iOS, Android and even Blackberry. Mozilla's move to WebKit means they have finally admitted that Gecko (alone) cannot win mobile.

>Will Firefox for Android suffer?

>Of course it will. It stands to reason that a 'native' Mozilla browser tech that uses WebKit would also be faster on Android too. So in time, if Junior turns out to be a real effort, the core base on which Firefox and indeed all of Mozilla's success has been built could be left behind for the mobile world.

>As Mozilla itself is now clearly focused on Mobile, its new CEO is from mobile and its new head of PR is too, it also stands to reason that Junior is a serious effort too. A split Gecko/WebKit effort would not be a good thing initially for Firefox, though it is the right decision for Mozilla's mobile aspirations. Mozilla could end up with a two track development cycle, but then again that's not that strange.

>The core rendering engine development can potentially be carved out from the interface development - sure it's not the same type of control that Mozilla is used too -- and sure they'd be tied very closely to Google and Apple's WebKit development efforts, but hey that just might be a good thing too.

I think some of this is FUD. Mozilla isn't going to abandon Gecko, but they probably will take advantage of Webkit for the iPhone/iPad/et al. If they do this, we'll probably see an abstraction layer of some sort.
Expand all images
>> No. 579
>abstraction layer

yeah, but wouldnt that come at a higher price, resource-wise? we're talking mobile devices.
>> No. 580
>>579

>wouldnt that come at a higher price, resource-wise?

Probably, but I hope not. I think it's insane that we have to worry about resources on the current generation of smartphones and tablets. These things are several times more powerful than the computers that sent people to the moon, yet we still find ways to suck up all their performance. Maybe the Mozilla team will find a way to get the iDevices to handle the load.
>> No. 585
>>580
Introducing the New Samsung Galaxy Selene!

can defeat earth gravity, and launch the user towards other stellar bodies.
>> No. 587
>>585
I'd buy that for a dollar...
>> No. 590
>>578
I really hope they don't abandon their main platform development for a mobile market just because stove jobs was an iron-fist dictator when it came to his products. Firefox is great because it lets you customize just about anything. Apple built their "it just works" reputation by putting users in the passenger seat when it came to computing. You can't screw it up, but you can't make it better either.
>> No. 591
>>590
I don't think they'll abandon the Gecko platform, but the big issue is video. They tried to push Ogg as the format of choice, but Apple, Google, and Microsoft wouldn't go with it. Now everything is MP4. Due to patents and licenses, the Mozilla Foundation cannot implement a player for MP4 so they're trying to find a way to use the native environment to do it for them.

Throw in things like Apple not allowing apps that compete against what their default offerings, and you see the problem Mozilla faces. It just makes sense to find a way to leverage what Apple already offers while putting familiar Firefox features on top of it. That's why I suspect we'll see some kind of abstraction layer. Mozilla won't want to get rid of Gecko, but they'll also want whatever they do on iOS to be reusable.
>> No. 592
>>591
for these reasons and others, it should get a seperate namesake from FF. apple doesnt want to play ball and make it easy for FF to come over? then they shouldnt benefit from the reputation built behind FF.

Im thinking "Mozilla FireFuckapple". its a name they can really build on, and surely reuse (as you have aptly stated - will be desired).
>> No. 641
File 135056051682.jpg - (2.07KB , 118x126 , 1275366033351.jpg ) Thumbnail displayed, click image for full size.
641
>>592

Mozilla doesn't stand to gain anything by not offering the power of it's namesake to Apple. Fostering that kind of antagonistic relationship between software developers and hardware manufacturers is a sure-fire prescription for both companies to suffer for it.

Apple behaving like Apple about software development shouldn't encourage Mozilla to cut off it's nose to spite it's face. iOS is a huge market, and it would be foolish to burn bridges with Apple over something like this.
>> No. 642
>>641
>Apple behaving like Apple about software development shouldn't encourage Mozilla to cut off it's nose to spite it's face.
What would you recommend to make both sides feel content?


Delete post []
Password  
Report post
Reason  




Inter*Chan Imageboard Top List