Wed Nov 19 2008 18:49:50 EST from Bryon Roche@uncnsrdWindows Firefox does *not* use MFC. I feel fairly confident in saying this. I am fairly certain, once you find the lowest-layer of their own graphics objects, they're using straight Win32 system calls to handle the controls, if not outright rendering everything themselves.
hrm.. I draw a blank, thinking on that info. I'm going to assume you're on ffox 3. Does the windows ffox3 use gtk, or MFC? It's so much harder to diagnose memory leaks there.
It uses Gecko. And its own peculiar COM-like thing. It has this amazing abstract layer for handling GUI elements in a cross-platform fashion.
if wmfire isn't cute enough...
Tue Nov 18 2008 20:09:19 EST from Ford II@uncnsrdFord, Yeah, I'm having a similar issue with ff3 on xp. Too bad, too, used to be a good stable alternative to IE. And yeah, the scrolling tabs are nice. ;-)
Anybody else having this problem: firefox is rapidly turning to a big piece of shit.
It's gotten to the point where it's only a few hours before it's eating over a gig of memory and spikes the cpu for 3-4 seconds every minute or so. Insanely annoying.
Five for each finger, and another one for the palm itself.
these had 5 keys per finger instantly reachable, but like fingerworks, they're out of business now.
In the time of everybody buying logitech piece of plastic crap, theres no place for sophisticated keyboards anymore...
Ah, and while we're at it: STOP BETA!
You know, it'd be nice to Stop Beta, but it won't ever happen.
The consumers are to blame.
My company used to carefully examine their software and hardware before release. Everything was always perfect before it went out the door. And, consequently, other companies beat us to something called 'mindshare'. As a consequence, we had the better product, but nobody knew about us, and wouldn't buy the product, because they were familiar with the competitor.
So, today, we rush things out the door and fix it later. Because, unfortunately, it sells better.
It's so stupid, but there's nothing for it until consumer culture changes.
So here's the official definition -- it depends on the platform.
Mainframe applications: a six to twelve month period when professional testers exercise a program under real-world loads with production data, documenting the results.
Desktop applications: the first successful compile.
Web applications: when a cool codename has been picked and t-shirts printed, and some vague notions of what the program will do have been tossed around.
Er, not entirely agreeing with the desktop application definition there, although it's close.
For desktop applications, the application transitions from alpha to beta generally at the point when QA indicates that the application's primary purpose is fulfilled under ideal circumstances, with mostly no negative testing, and no odd conditions.
But, yeah, it often feels like 'when it successfully compiles'.