Recommended Posts

Link to comment
https://www.neowin.net/forum/topic/989780-meet-the-browser-firefox-next/
Share on other sites

Are we slim yet? No, once you drop legacy support and build for the future and not the past, then you will be slim.

Its for tracking memory usage , and dropping support for Xp (which aint legacy , it is still in use) would come in "are we modern yet" rather :p

Nice to see that once again Firefox is becoming primarily a Windows browser with Mac and Linux users supported by accident rather than actually deliberately designing for the platform. Promises of OpenGL accelerated layers in Firefox 5.0 and low and behold they've failed to deliver - why aren't I surprised.

Are we slim yet? No, once you drop legacy support and build for the future and not the past, then you will be slim.

Feel free to name ONE aspect of IE9 that is slimmer than Fx4.

Nice to see that once again Firefox is becoming primarily a Windows browser with Mac and Linux users supported by accident rather than actually deliberately designing for the platform. Promises of OpenGL accelerated layers in Firefox 5.0 and low and behold they've failed to deliver - why aren't I surprised.

I don't know about OS X, but to be honest, it's hard to deliberately design GPU acceleration for a platform (Linux) with such a high level of fragmentation and crappy graphics drivers.

A fast, slim browser. :)

erm , yeah ie9 is faster coz of dropping support for xp and not coz of some chakra (or dead code elimination :shiftyninja: ) , so yeah xp is the one to blame :)

attachment.cgi?id=525501

Some new stuff regrading the branches :D

  • Like 2
I don't know about OS X, but to be honest, it's hard to deliberately design GPU acceleration for a platform (Linux) with such a high level of fragmentation and crappy graphics drivers.

True, but there is no excuse when it comes to Mac OS X - a single OpenGL library to target at and even then they (Firefox developers) couldn't do it right.

erm , yeah ie9 is faster coz of dropping support for xp and not coz of some chakra (or dead code elimination :shiftyninja: ) , so yeah xp is the one to blame :)

attachment.cgi?id=525501

Some new stuff regrading the branches :D

They even made the nightly/beta builds look good. :wub: Does it work with channels now, just like Chrome?

  • Like 1

erm , yeah ie9 is faster coz of dropping support for xp and not coz of some chakra (or dead code elimination :shiftyninja: ) , so yeah xp is the one to blame :)

Maybe not XP so much, but supporting 2K is silly. There's dead code right there. XP won't be far behind.

But te new builds look nice :D

Maybe not XP so much, but supporting 2K is silly. There's dead code right there. XP won't be far behind.

But te new builds look nice :D

yeah they do! :D

but , 2k is legacy , i agree :p but not xp , people with 512mb ram are still out there , even i was 2 years back i guess, xp does need a faster browser , which microsoft fails to provide , not even that , 64bit versions of windows too need a fast browser which again microsoft fails to provide , i find them really incompetent , they created a browser for mere 2 versions of windows :|

Until they offer extensions updates for non-stable releases and fix their terrible project management at AMO, no.

extension compatibility will be bumped automatically with newer releases UNLESS they are found incompatible with certain feature , thats what i heard , so i dont think that will be a problem , and give addon makers some time, firefox 4.0 isn't even 1 month old

btw i have filed this bug , anyone interested to help me voice it to developers?

Nice to see that once again Firefox is becoming primarily a Windows browser with Mac and Linux users supported by accident rather than actually deliberately designing for the platform. Promises of OpenGL accelerated layers in Firefox 5.0 and low and behold they've failed to deliver - why aren't I surprised.

As I said in the last thread, Firefox supports OpenGL layers on OS X and has since last year (it's enabled by default in Firefox 4 and 5!)

They explicitly don't support it on 10.5 due to bugs in the underlying OS, those bugs have been fixed with 10.6(.2) though.

extension compatibility will be bumped automatically with newer releases UNLESS they are found incompatible with certain feature , thats what i heard , so i dont think that will be a problem

Right, so instead of a month for good add-ons to get approved, it'll take a month for bugged add-ons that crash the browser and break features to get blacklisted.

Personally I don't see that as an improvement, but meh.

and give addon makers some time, firefox 4.0 isn't even 1 month old

I'm sorry, but I'm not interested in empathizing with Mozilla and/or add-on developers. If it can't be ensured that the extensions I want be ready to use when the browser goes stable, that counts as a black mark against the product as far as I'm concerned.

Besides, the current problem isn't with add-on devs, it's mostly with Mozilla's horrible project management. Four weeks (and more) for an add-on to make it through the review queue? That's bloody ridiculous.

In the case of non-stable builds: again, no automatic extension updates unless specifically marked as compatible with Nightly/Aurora/Beta/whatever, which most extensions aren't. Until this changes, Firefox pre-release channels aren't for me.

A fast, slim browser. :)

Dropping XP support had nothing to do with making it fast or slim. The only reason why IE9 is good now is because Microsoft coded it properly. Microsoft could have easily released a version of the browser for XP, (though it wouldn't use the specific GPU accell APIs Microsoft touts since they're not there in XP), and it would be just as slim and fast as it is on Vista/7. Your code does not magically become better when you "remove support" for an earlier OS version. Good code is good code no matter where it runs, and XP is very well capable of running any program out there.

  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Lego Batman 2026 hahahaha. You thought I couldn't reply back???
    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      82
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!