Recommended Posts

Is it only me that when some images have some time of error, they simple don't show up?

That is a bit anoying since when we are seing some websites there is nothing that can tell us that should be there one image that is not working fine :s

Cheers

I had a problem like that, my router was causing it. Does it happen on every browser or just firefox ?

Scrolling really sucks in Firefox on Mac OS X. Instead of being smooth it jerks around when using a Magic Mouse or Magic Trackpad. In general Firefox' animations are awkward and nowhere near as smooth as throughout the rest of the OS and its applications, or completely missing. Yet another reason why using customs interface APIs instead of the native ones is a really bad idea.

Scrolling really sucks in Firefox on Mac OS X. Instead of being smooth it jerks around when using a Magic Mouse or Magic Trackpad. In general Firefox' animations are awkward and nowhere near as smooth as throughout the rest of the OS and its applications, or completely missing. Yet another reason why using customs interface APIs instead of the native ones is a really bad idea.

Not my experience. My Alu MacBook has perfect scrolling on nearly all sites I visit.

Not my experience. My Alu MacBook has perfect scrolling on nearly all sites I visit.

Compared to Safari, Finder, Mail, iCal etc. Firefox' scrolling is really jerky with inertia enabled. Firefox only scrolls smoothly when holding down my fingers without letting go when I move around. But when I give a flick with two fingers to scroll and inertia kicks in scrolling starts to stutter.

They really changed the about:config strings to make it almost unrecognizable for some settings compared to FF3.

I was trying to change the default search for the address bar to Bing by searching for the keyword.url as I used to, but now it is browser.search.defaultsearchengine.

Compared to Safari, Finder, Mail, iCal etc. Firefox' scrolling is really jerky with inertia enabled. Firefox only scrolls smoothly when holding down my fingers without letting go when I move around. But when I give a flick with two fingers to scroll and inertia kicks in scrolling starts to stutter.

I don't have any of that.

Needs a new option: "Are We Relevant Yet?"

Mozilla really needs to step up their game if they don't want to be left in the dust. FF4 is a joke at this point.

How exactly is it a joke?... Sure it's slow on development process... but it's still better then Chrome IMO. Firefox for me was lacking a bit in speed with Firefox 3. With Firefox 4 the speed has picked up a lot and is now the clear winner for me. Chrome is missing quite a few features I just cannot live without.

And what exacyly is the joke?Can you be more specific???

I don't know about you,but the only joke i see is your post Educated Idiot.Firefox is faster,has betterUI and a lot more options and addons than chrome(this is my personal opinion).For me on sunspider or kraken benchmark or in real life browsing FF 4 is better than chrome in any way.As Kaoxt said development is not as fast as we would like, but after FF4 they are going in a faster release cycle so this will not be a problem anymore.

Needs a new option: "Are We Relevant Yet?"

Mozilla really needs to step up their game if they don't want to be left in the dust. FF4 is a joke at this point.

To be honest I think 4.0 is a GREAT update. I considered using Chrome but ended up going back to FF4 :/ I might give Safari 5.1 another shot in Lion but we'll see... I'm not holding my breath

How exactly is it a joke?... Sure it's slow on development process... but it's still better then Chrome IMO. Firefox for me was lacking a bit in speed with Firefox 3. With Firefox 4 the speed has picked up a lot and is now the clear winner for me. Chrome is missing quite a few features I just cannot live without.

The current dev build in chrome is bit laggy for me, which is why I decided to finally go ahead and test out FF4b12 (originally was planning to wait until rtm since I had not need). Having used FF3 in the past, it certainly is a great improvement in performance, features, and customization (perhaps biggest key point here) and I am impressed despite their slow development. But overall, speed and performance is the most important for me, which is where Chrome excels (at least for the time being). FF4 feels very bloated at times and gets a bit laggy, partly because of the large initial memory load despite having 6GB of ram. It still lacks some of the innovative features that makes chrome so great, like the ability to manually add search engines, which is something I find essential for fast/convenient browsing. I will be back to using chrome by next week following this little experiment, but I still have faith that the mozilla team can make FF more competitive by the end of the year.

To be honest I think 4.0 is a GREAT update. I considered using Chrome but ended up going back to FF4 :/ I might give Safari 5.1 another shot in Lion but we'll see... I'm not holding my breath

I am one of the few people that actually likes Safari on Windows (the browser itself, not the crap it comes with). It has always been fast (as fast as earlier builds of Chrome, even) and looks decent enough to use full-time. In fact, I can't remember a single crash. I have, however, managed to crash Chrome a couple times, but that's another story.

Anyway, what I meant to say is the development of FF4 is a joke: one delay after another, 12 billion betas, engineers leapfrogging one-another, and so on. Mozilla itself isn't like it use to be, and I'm not even referring to Google's financial support. I don't know what happened to them, but I'm guessing the world passed them by while they were screwing around. That's the thing about the tech world (especially on the software side): you miss one month and it'll take years to catch up.

The browser itself is pretty reliable--It doesn't crash (much), websites render cleanly and I can't live without some extensions (i.e. Adblock+). However, it takes forever and a day for it to start up, and it takes even longer to get it working right. I think I spend more time tweaking and customizing the damn thing than I do using it, and that's a problem. I can't live with a slow, ugly browser.

I rag on Mozilla a lot because I am extremely dissapointed in them. I use to consider them one of the greatest companies on the web at one point, but now it seems like each department has its own agenda. It's just sad that they've lost focus and they're pulling in different directions.

Since people keep claiming Firefox 4 is taking so long, I decided to actually go and look up the time between versions.

1.0 to 1.5: 1 year, 20 days

1.5 to 2.0: 10 months, 25 days

2.0 to 3.0: 1 year, 7 months, 24 days

3.0 to 3.5: 1 year, 13 days

3.5 to 3.6: 6 months, 22 days

3.6 to 4.0 (now): 1 year, 1 month, 9 days

So yeah, the time between 3.6 and 4.0 isn't that bad, and isn't even as long as the time between 2.0 to 3.0.

People said the same things about 3.0 as they're saying about 4.0 (Taking too long, too many beats, irrelevant, etc.). And funnily enough 3.0 was also the release that set the world record for downloads :laugh:

How exactly is it a joke?... Sure it's slow on development process... but it's still better then Chrome IMO.

How FF development process is better than Chrome's? Google at least doesn't tease users with features they can't add in time and doesn't move release date forever ...

Needs a new option: "Are We Relevant Yet?"

Mozilla really needs to step up their game if they don't want to be left in the dust. FF4 is a joke at this point.

Its not joke , Mozilla had been very "open" with their public and that's how it has been , yeah i accept the development was very slow , but i can bear that if they deliver a very stable product (considering even nightlies are very very stable)

I remember when the first beta came , their wiki page said "w00t!" , that's mozilla and i love them this way :D

Since people keep claiming Firefox 4 is taking so long, I decided to actually go and look up the time between versions.

1.0 to 1.5: 1 year, 20 days

1.5 to 2.0: 10 months, 25 days

2.0 to 3.0: 1 year, 7 months, 24 days

3.0 to 3.5: 1 year, 13 days

3.5 to 3.6: 6 months, 22 days

3.6 to 4.0 (now): 1 year, 1 month, 9 days

So yeah, the time between 3.6 and 4.0 isn't that bad, and isn't even as long as the time between 2.0 to 3.0.

People said the same things about 3.0 as they're saying about 4.0 (Taking too long, too many beats, irrelevant, etc.). And funnily enough 3.0 was also the release that set the world record for downloads :laugh:

Several reasons why we claim it is too slow and is still a relevant argument:

-Chrome has been blazing along for the past year gaining a huge lead on performance while FF was lagging behind. This put extra pressure on Mozilla to push out a new release to at least maintain the gap, which they have taken too long relative to the pace of Chrome. The function of "long" is purely to the present rather than the past.

-At the time when FF3.0 launched, Chrome was still under development and was still a couple months away from launch. FF was considered the best browser available at the time until Chrome came along and changed the philosophy of web browsing. It forced people to decide which was more important to them: faster page load times and less system resource use for a basic browsing, yet highly responsive experience, or a decently fast and tons of addons for a more robust browsing experiences. This led to the major divide we see in the thread. Diehard FF fans said they could not live without their addons, while others like myself were willing to sacrifice addons to have the fastest web performance.

Also, it is one thing to download a browser, another to actually use it as default browser. I would not be surprised if FF manages to set another record with the FF4 launch, but the number of people who will actually use it every day is certain to be far below the number of downloads and installs.

Since people keep claiming Firefox 4 is taking so long, I decided to actually go and look up the time between versions.

1.0 to 1.5: 1 year, 20 days

1.5 to 2.0: 10 months, 25 days

2.0 to 3.0: 1 year, 7 months, 24 days

3.0 to 3.5: 1 year, 13 days

3.5 to 3.6: 6 months, 22 days

3.6 to 4.0 (now): 1 year, 1 month, 9 days

So yeah, the time between 3.6 and 4.0 isn't that bad, and isn't even as long as the time between 2.0 to 3.0.

People said the same things about 3.0 as they're saying about 4.0 (Taking too long, too many beats, irrelevant, etc.). And funnily enough 3.0 was also the release that set the world record for downloads :laugh:

Awesome find , also one must consider that Firefox 4 compared to Firefox 3.6 is AGGEESSS AHEEADD and the time taken seems less to me sometimes , its just that they failed to deliver products at the time they promised (or rather targeted in wiki notes and we took it as promise) , that's what made us feel they are slow , if they had said Firefox 4 would come next year Q1 , no one would have said development is slow

The current dev build in chrome is bit laggy for me, which is why I decided to finally go ahead and test out FF4b12 (originally was planning to wait until rtm since I had not need). Having used FF3 in the past, it certainly is a great improvement in performance, features, and customization (perhaps biggest key point here) and I am impressed despite their slow development. But overall, speed and performance is the most important for me, which is where Chrome excels (at least for the time being). FF4 feels very bloated at times and gets a bit laggy, partly because of the large initial memory load despite having 6GB of ram. It still lacks some of the innovative features that makes chrome so great, like the ability to manually add search engines, which is something I find essential for fast/convenient browsing. I will be back to using chrome by next week following this little experiment, but I still have faith that the mozilla team can make FF more competitive by the end of the year.

Firefox 4 (since preb13 builds) uses much much less memory than chrome , what innovation did chrome do? They went to the market , picked up fastest browser engine , added some features from each browser and tada! We have chrome ready to be served ! Even now with the latest version (11 i guess) they used tracermonkey like method , which again is an "innovation" by mozilla "used" by Chrome. Its just the omnibar , tabs on top and slight other changes which i accept , are innovative.

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

    • No registered users viewing this page.
  • Posts

    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!