Slashdot Mirror

← Back to Domains

Domain: slyerfox.com

Stories and comments across the archive that link to slyerfox.com.

Comments · 23

  1. 2 things the FOSS commies won't like about Vista by Anonymous Coward · · Score: 0 · on 20 Things You Won't Like About Vista

    1) within a day of it's release there'll be more vista desktops than linux
    2) within a week of it's release there'll be more IE7 users than Firefox

  2. Re:Definitely not 0 profit... by Anonymous Coward · · Score: 0 · on IE The Great Microsoft Blunder?

    lol .. only Firefox gets away with that kind of deception.

  3. Re:Meanwhile... by Anonymous Coward · · Score: 0 · on Microsoft Releases Critical IE Patch

    Ah, yes, the "it's a feature!" response to the Firefox memory leak. Hm, leak isn't quite the right word, since it makes it sound slow and gradual. I like "Firefox memory gaping hole" better.

    But anyway, here's a good rebuttal to the "it's a feature!" response relating to memory leaks. It's not a feature. It's a bug. Opera has the same feature, and manages not to leak massive amounts of memory.

  4. Web site devoted to Firefox dishonesty: by Futurepower(R) · · Score: 1 · on Firefox Extension Guide and More

    You said, "I've been seriously thinking of starting up a "FirefoxWatch" blog..."

    There is an entire web site devoted to Firefox dishonesty: Slyerfox.

  5. Firefox fans by Anonymous Coward · · Score: 0 · on Firefox Community, Sickly Out of Control

    It's hardly a secret that firefox fans suck ass ...

  6. 200 extensions ... or excuses by Anonymous Coward · · Score: -1, Flamebait · on Mozilla Announces Extend Firefox Contest Winners

    Dear Firefox user,

    In addition to our memory retention & releasing features, we're pleased to announce 200 updated excuses for why Firefox crashes and/or hogs memories.

    Introducing, Extend Firefox!

    Firefox need to pull their fat little fingers out of their asses and focus on improving their product, instead of perception or "features" of their product.

  7. Re:Heh, what kept you, MS? by Anonymous Coward · · Score: 0 · on Interview with Microsoft Exec on IE7 and RSS

    The fact reamins IE will never be as innovative as Firefox
    Firefox doesn't innovate. Most of the "Features" were derived from Opera or other browsers.

    The only real innovation is that Firefox has duped users into thinking buggy software is okay, and that the spam is cool.

  8. Re:Heh, what kept you, MS? by Anonymous Coward · · Score: 0 · on Interview with Microsoft Exec on IE7 and RSS

    The fact reamins IE will never be as innovative as Firefox
    Firefox doesn't innovate. Most of the "Features" were derived from Opera or other browsers.

    The only real innovation is that Firefox has duped users into thinking buggy software is okay, and that the spam is cool.

  9. Firefox by Anonymous Coward · · Score: 0 · on Interview with Microsoft Exec on IE7 and RSS

    Interestingly, over at Asa Dotzler's (full time Firefox troll) blog you have a thoroughly childish analysis of IE7 that first
    - claims credit for it all
    - identifies superior features or implementations
    - suggests Firefox get said features

    The only thing Firefox is (or was) is a wakeup call to MS. I'm glad it happened, but the Moz org needs to take a good hard look at themselves and stop thinking they're the second coming of Christ.

  10. Re:Seriously... Bugs =! "shortcuts"! by hkmwbz · · Score: 1 · on Firefox Memory Leak is a Feature
    Not only are you a troll, but a conspiracy theorist who takes a couple of bugs and generalizes from that.

    You need to take off your Firefox Fanboy Zombie costume and get a clue. But Firefox zealots spreading FUD about Opera and other browsers isn't exactly uncommon:

    http://www.slyerfox.com/

    People like you, who among other things spread FUD and lies about other browsers to move the focus away from major issues in Firefox, are the reason why the Firefox community has such a terrible reputation.

    You are making up excuses to cover up Firefox's shortcomings by pointing out a couple of bugs in Opera and using the sad and pathetic excuse that they are taking "shortcuts".

  11. A complete list of features... by Anonymous Coward · · Score: 0 · on Firefox Memory Leak is a Feature

    ...can be found quickly, using your favorite browser, by looking at this website:

    http://www.slyerfox.com/

    Enjoy.

  12. Re:Your usage pattern is different. by ben_1432 · · Score: 1 · on Firefox Memory Leak is a Feature

    Mozilla QA (Asa Dotzler)is a longer running joke than the memory leaks.

  13. Re:What I'd like Mozilla devs to do by Anonymous Coward · · Score: 0 · on Firefox Memory Leak is a Feature

    That sounds great in theory, but there's a couple of critical factors that'll stop it ever happening:
    - nobody would be blogging about "great new features" for 6 months
    - people may be blogging about the bugs & insecurities

    3/4 of Firefox is publicity, and Moz making the *much needed* decision to just stop further dev till they get their issues sorted would be seen as them admitting their browser's not (anywhere near) what it's hyped up to be.

    Also it'd leave the craploads of SpreadFirefox tards with nothing to do, or talk about. You wouldn't want to silence that generation (born in the 90's) would you? ;)

  14. Nice excuse by Anonymous Coward · · Score: 0 · on Firefox Memory Leak is a Feature

    Shame it took 4 years to come up with this ripper of an excuse.

    It doesn't explain why a browser doing nothing overnight can chew an extra couple hundred meg of memory either.

  15. Why does Opera work well, and not Firefox? by Futurepower(R) · · Score: 4, Informative · on Firefox Memory Leak is a Feature
    More clues:

    • Opera has none of these problems. So, the quote from the Mozillazine blog shown below, although it is typical, is not supported by the facts.

    • Whatever causes the CPU hogging bug is definitely associated with extreme memory use. No doubt there are leaks, but this is not a leak, since it is not necessarily associated with greater use of Firefox.

    • Users often report that just leaving Firefox open overnight causes CPU hogging and extreme memory use.

    • The problems are the same in Mozilla browser.

    • It's good to test Firefox with a laptop in a quiet environment. When you hear the laptop fan begin to run while there is no activity, you know Firefox has begun to suck CPU cycles.

    • Putting a computer into standby or hibernation often makes the CPU hogging bug much worse. That's why Firefox users sometimes just leave their computers on.

    • When a computer takes a long, long time to start from standby, you know Firefox is taking CPU cycles. What about coming out of standby makes Firefox unstable? No other program has that problem.

    Quote from the blog linked in this Slashdot story About the Firefox "memory leak": "A lot of people complain about the Firefox "memory leak(s)". All versions of Firefox no doubt leak memory - it is a common problem with software this complicated."

    No other program in common use is so buggy. The problems in Firefox are not "common".

    Another quote from the linked Mozillazine blog: "What I think many people are talking about however with Firefox 1.5 is not really a memory leak at all. It is in fact a feature."

    That's not what the technical magazines, newsletters, web sites entirely devoted to Firefox problems, and even the mainstream media say. They say it is a serious problem.

    Mozilla developers have been denying that there is a serious problem for more than 3 years. It seems that it would be less work to fix the problem than to undertake a cottage industry of trying to convince people they aren't having problems. Mozilla developers have been impeding characterization by marking Bugzilla bug reports of these problems invalid.

    However, it is clear that it would take a serious scientific investigation; this is not an easy bug to characterize.
  16. Maybe Sun should keep it? by Anonymous Coward · · Score: 4, Insightful · on Sun Urged to Give Up OpenOffice Control

    Mozilla, for all the support it has, still hasn't achieved any of their goals. 4 years later it's still essentially NS code, and it's plagued by code nobody likes, and bugs both inherited and introduced.

    With Sun at least you've got one company at the wheel so to speak.

  17. Re:Bittorrent and Firefox by Anonymous Coward · · Score: 0 · on Opera 9 with Widgets and BitTorrent Now Available

    RTFA. This isn't about Firefox. Why do Firefox users always have to inject Firefox questions & answers where they're not wanted?

    Why do FF users have so much time for commenting anyway? They've got a super cool browser and all those extensions to play with.

    http://www.slyerfox.com/fans.aspx
    "How do you spot a Firefox fan? An answer appears to a question nobody asked."

  18. Firefox is not the enemy by Anonymous Coward · · Score: 1, Funny · on Another Look At Mozilla's BugFix Rate

    It's important to remember that the enemy in TFA is Microsoft, not Firefox. It doesn't matter that Firefox has long-running problems that people have complained about for years. Firefox is Good. Microsoft is Bad. Remember that next time you want to complain about Firefox chewing a couple hundred megabytes of memory.

    Firefox's leniant users
    either your computer or what you're doing is the problem. Sorry. It doesn't matter if everything else works fine either. It is not Firefox.

  19. Difficult bugs simply aren't fixed. by Futurepower(R) · · Score: 3, Interesting · on Another Look At Mozilla's BugFix Rate
    It does seem that security bugs in Mozilla and Firefox are fixed promptly.

    However, other bugs simply aren't fixed. For about 3 years many, many people have reported the CPU hogging bug which is unique to Firefox and Mozilla browsers. For a small example of the reports of problems see Firefox is the most unstable program in common use.

    Now the problems are beginning to be reported in technical magazines, newsletters, bloggers, and even the mainstream media.

    Under the conditions mentioned in the bug reports, I'm not able to make the CPU hogging bug fail; it is always there. I've tried Linux, Windows XP SP2, and Windows 98 SE. I've tried Intel and Via chipset motherboards. For about 3 years, in all versions, the CPU and memory hogging bug has always been there. Firefox version 1.5.0.1 is worse than Firefox version 1.5, and those versions are worse than earlier ones. This is with a clean profile and no extensions except DOM Inspector, which is a menu choice on the installation program.

    In 3 years, I've never had any evidence that any Firefox or Mozilla developer has reproduced the conditions that cause the problem.

    The problem with Firefox and Mozilla developers not fixing difficult bugs seems to be a social one, not primarily a technical one. The developers keep asking for the problem to be made easier, but it appears to me that there is already plenty of evidence that would allow further investigation.

    Perhaps the developers do not understand that there is a class of bugs that can only be found using the methods of scientific research. Many people like programming, but only people who accept the biggest challenges truly have programming in their hearts and minds:

    Three biggest challenges of programming

    Here are programming's three biggest challenges. Coding is relatively easy. It is these challenges which separate a true professional from an average programmer:
    1. Being a scientist -- Often the most difficult programming is easier than the most difficult debugging. Often debugging requires creative scientific thinking. First, it is necessary to gather information. Second, make a theory that fits the facts. Third, design an experiment that tests the theory. Fourth, perform that experiment and analyze the results. Fifth, using the information that was learned, design a new theory, and repeat the steps above. The information that has been provided about Firefox instability is plenty to begin making theories.
    2. Skill in social interaction -- Often the social interaction necessary to understanding what is needed and wanted is more difficult than any coding challenge. Social skills can be learned, and are part of being a good programmer.
    3. Designing the user interface -- Only someone who has habits of caring for others can have the necessary detailed insight and creativity to discover how to do everything possible for the user.

    Instead there are excuses:

    Mozilla Top 12 Excuses

    Top 12 things Firefox and Mozilla developers say about those who report difficult bugs, collected during the last 3 years:

    1. Maybe this bug is fixed in the nightly build.
    2. Yes, this bug exists, but other things are more important.
    3. No one has posted a TalkBack report. [If they had read the bug report, they would know that there is never a TalkBack report, because the bug crashes TalkBack, too, or a TalkBack report is not generated.]
    4. If you would just give us more information, we would fix this bug.
    5. This bug report is a composite of other bugs, so this bug report is invalid. [The other bugs aren't specified.]
    6. You are using Firefox in a way that would cras
  20. Re:Firefox: Most unstable program in common use = by Anonymous Coward · · Score: 0 · on A History of Firefox

    If your Firefox is buggy, it's you at blame. Not Firefox. Either you or your extensions, but never the fox!

    It's one of the most amazing features of Firefox that the user is to blame for all problems, not the browser.

    I'm a bit disappointed to see that the history of Firefox didn't go into how their priorities have dramatically changed over the years. Their priority is being in the news, not being the best.

    A cheesy blog post being /.ed just emphasises that.

  21. Re:Firefox: Most unstable program in common use = by Anonymous Coward · · Score: 0 · on A History of Firefox

    If your Firefox is buggy, it's you at blame. Not Firefox. Either you or your extensions, but never the fox!

    It's one of the most amazing features of Firefox that the user is to blame for all problems, not the browser.

    I'm a bit disappointed to see that the history of Firefox didn't go into how their priorities have dramatically changed over the years. Their priority is being in the news, not being the best.

    A cheesy blog post being /.ed just emphasises that.

  22. More interesting, the future of Firefox by Anonymous Coward · · Score: 0 · on A History of Firefox

    Unless there are some radical changes this year in Firefox, I think next year we'll be using past tense on it.

    From TFA:
    Netscape made two mistakes. They did not publish enough product management information to enable the community to help them achieve their goals. They did not even consistently communicate what these goals were.

    Publishing crap to the community is 99% of what Firefox does. Publishing quality code and accompanying documentation is (rounded up to) 1%.

    Interesting that they considered C#/.NET, if they had they would have had to rewrite all the code instead of search/replace netscape with mozilla.

    From TFA:
    Many new contributors are finding the project and new ways to help out.
    Dear Google,
    How many millions will you pay to be our homepage this year?
    Love Mozilla

    Ignoring the Mozilla propaganda division, ask yourself these questions about the history of Firefox:
    - why have so many memory leaks passed QA for 4 years running
    - why aren't extensions run in a protected sandbox
    - why is spreading Firefox more important than fixing it?

    Firefox hype is pointless, and I think with IE7 and Opera9 coming out this year we'll see people start to realise Firefox is nothing more than a tricked up Netscape, with new problems.

  23. Re:Before you start bitch about Firefox memory lea by Anonymous Coward · · Score: -1, Flamebait · on Understanding Memory Usage On Linux

    progress made and being made.

    Coooooooooool. 4 years for some progress to be made. By 2008 when a bottom of the line Dell ships with 2gb of ram, Firefox should run like a charm.

    You have to wonder why the memory leaks have slipped through 4 years of quality assurance and versions? Right? Oh wait, no. It's forgivable because of the logo/creed/whatever.

    http://www.slyerfox.com/problems.aspx