Recommended Posts

Rumour has it that Electrolysis isn't going to be fully enabled in 4.0 - from what I have read full tab process isolation isn't come until Firefox 5.0 :(

Why are they deliberately catrasting Firefox? it would have been the one big feature that would have relly pulled it ahead of Safari for me but since they've scrapped full Electrolysis, the release is rather crappy IMHO.

Rumour has it that Electrolysis isn't going to be fully enabled in 4.0 - from what I have read full tab process isolation isn't come until Firefox 5.0 :(

Why are they deliberately catrasting Firefox? it would have been the one big feature that would have relly pulled it ahead of Safari for me but since they've scrapped full Electrolysis, the release is rather crappy IMHO.

That makes it seem like Mozilla are now rushing to get firefox 4.0 released, there's no need to rush IMO... they should really keep at it and so what if they miss the deadline for release, we can wait that little bit longer.

Rumour has it that Electrolysis isn't going to be fully enabled in 4.0 - from what I have read full tab process isolation isn't come until Firefox 5.0 :(

Why are they deliberately catrasting Firefox? it would have been the one big feature that would have relly pulled it ahead of Safari for me but since they've scrapped full Electrolysis, the release is rather crappy IMHO.

so we would had that same as Firefox 3.6.6 (OOPP)

i thought they would had moved to the next step by now :/

so what we well have then for FF4

New UI + D2D/DW + revamped JS engine + new addon manager

and that if D2D ever make it or it could easily drag to Firefox 4.5

so we would had that same as Firefox 3.6.6 (OOPP)

i thought they would had moved to the next step by now :/

so what we well have then for FF4

New UI + D2D/DW + revamped JS engine + new addon manager

and that if D2D ever make it or it could easily drag to Firefox 4.5

Count yourself lucky that you get Direct2D/DirectWrite, Mac users get absolutely nothing. Once again us Mac users are treated like the b-astard red-headed step child of the family whom the Mozilla developers love to hate.

Its been how long since Firefox 1.0 has shipped and it still runs like crap on Mac OS X. Why don't they just give up because it is clear to me that Mozilla developers are scum who don't give a crap about any other platform but Windows.

Count yourself lucky that you get Direct2D/DirectWrite, Mac users get absolutely nothing. Once again us Mac users are treated like the b-astard red-headed step child of the family whom the Mozilla developers love to hate.

Its been how long since Firefox 1.0 has shipped and it still runs like crap on Mac OS X. Why don't they just give up because it is clear to me that Mozilla developers are scum who don't give a crap about any other platform but Windows.

Which is surprising as most of them seem to be using Macs as their primary computers.

Which is surprising as most of them seem to be using Macs as their primary computers.

Then explain why it runs so utterly crap on Mac OS X - if the above were true then wouldn't it stand to reason that it should run well on Mac OS X?

Count yourself lucky that you get Direct2D/DirectWrite, Mac users get absolutely nothing. Once again us Mac users are treated like the b-astard red-headed step child of the family whom the Mozilla developers love to hate.

Its been how long since Firefox 1.0 has shipped and it still runs like crap on Mac OS X. Why don't they just give up because it is clear to me that Mozilla developers are scum who don't give a crap about any other platform but Windows.

D2D/DirectWrite are Microsoft Windows only API's, how do you expect Mozilla to implement those in a browser on an OS that doesn't have the API's?

Not Mozilla's problem...

Count yourself lucky that you get Direct2D/DirectWrite, Mac users get absolutely nothing. Once again us Mac users are treated like the b-astard red-headed step child of the family whom the Mozilla developers love to hate.

Its been how long since Firefox 1.0 has shipped and it still runs like crap on Mac OS X. Why don't they just give up because it is clear to me that Mozilla developers are scum who don't give a crap about any other platform but Windows.

OS X is the only platform getting out of process hardware accelerated composited plugins, It's definitely not being ignored like you continuously say.

Electrolysis is mainly for mobile Firefox at the moment, after it's working on that they'll work on having the desktop version have it.

D2D/DirectWrite are Microsoft Windows only API's, how do you expect Mozilla to implement those in a browser on an OS that doesn't have the API's?

Not Mozilla's problem...

Where did I state that I wanted Direct2D/DirectWrite? how about reading the post instead of coming to stupid conclusions. I used the issue of Direct2D/DirectWrite as an example of Mozilla putting alot of effort into their Windows version but nothing when it comes to Mac OS X.

OS X is the only platform getting out of process hardware accelerated composited plugins, It's definitely not being ignored like you continuously say.

Electrolysis is mainly for mobile Firefox at the moment, after it's working on that they'll work on having the desktop version have it.

Which is entirely useless for someone like me expecting (after the Firefox programmers promised) that'll arrive in Firefox 4.0. By the time full electrolysis does arrive Webkit2 will be stabilised and shipping - thus making it totally useless to my needs. Firefox had a window of opportunity for me and because of their pathetic incompetence that window is closing fast.

Rumour has it that Electrolysis isn't going to be fully enabled in 4.0 - from what I have read full tab process isolation isn't come until Firefox 5.0 :(

Why are they deliberately catrasting Firefox? it would have been the one big feature that would have relly pulled it ahead of Safari for me but since they've scrapped full Electrolysis, the release is rather crappy IMHO.

Or they could make the browser stable so you don't need tab islolation, it's not a very useful feature really. and it makes the task manager horribly messy. isolating plugins, yes, isolation every tab, no.

I think they're aiming for a tab per domain (so 4 neowin tabs = 1 neowin process), And they're also aiming to run Jetpacks (newer HTML+CSS+JS based extensions) out of process.

But there are more important issues for the desktop release (being able to push every tab but the active one out of memory doesn't mean much on a PC, but it means a whole bunch on an Android phone, etc.)

I think they're aiming for a tab per domain (so 4 neowin tabs = 1 neowin process), And they're also aiming to run Jetpacks (newer HTML+CSS+JS based extensions) out of process.

But there are more important issues for the desktop release (being able to push every tab but the active one out of memory doesn't mean much on a PC, but it means a whole bunch on an Android phone, etc.)

I thought jetpack was discontinued?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.