I wonder if this is in part due to MoFo being involved in open source - people have been complaining before (I believe rightly) that the decision making process over there is too opaque and we just get a final judgement handed down. Now that they try to open up, they end up giving kinda vague and confusing information. (Still feels opaque though, maybe that's just me)
Essentially, this just seems to be a bunch of blog posts / usenet postings / etc. (okay, there's one page at mozilla.org, so I guess that's official).
Or maybe they just suck at management. But then, good management = decisions at a single place = more opaque for random contributors.
Strange, Mozilla invokes guy in rubber suit defending mock Tokyo for me.
And for your last point - that's like saying Microsoft or Lotus, Red Hat, Novell - most company names don't necessarily make sense. What the heck is Macdonald's anyway? Some convience store like Mac's? And I guess Haliburton must be a hotel chain, or some sort of fish-selling place.
Actually, I recognize 5 of the 10 names at the bottom of the open letter from Mozilla related stuff, and I'm just a guy that watches from the sidelines. And the guy that wrote the letter (bz) is like some super-developer or something - he seems to touch the Mozilla tree all over the place (in a good way), is responsive and gets lots of stuff done. He's also expressed the desire to keep the suite before, so I'm not exactly surprised to see him being part of the effort.
I'm guessing the lack of interest before the offical "we're killing Seamonkey" announcement is because there seemed to have been no reason to step up while the situation was in limbo - backend stuff (shared w/ Firefox &c) was being done, there really wan't that much need to change the frontend drastically. Other than porting XPFE to the new toolkit I guess - not sure why they weren't majorly working on that beyond "sync blah with toolkit blah" bugs. Totally unfounded guess would be NIH.
(As I noted - I'm just a random bystander; heck, I don't even hang out on their IRC server)
Interestingly, it seems that the default theme has a slight edge on the left side that isn't a tab, so double left clicking on the left edge works. WinXP, XP's theming is off. There's also a tiny strip above non-active tabs (also pretty much impossible to get to).
Definately not as easy as the new tab button though; it's so small that it only really works when the window is maximized (Fitt's law).
I agree that Rose is a pain. (Caveat: student here, so maybe we just suck)
We tried to draw some class diagrams, sequence diagrams, etc. After struggling with Rational Rose, we found it easier to just do things semi-manually in Visio, rather than use the built-in capabilities of Rational Rose. Havn't tried using the code generation / reverse engineering capabilities of Rose though. In generally, I just find its UI to be annoying, even if its output isn't necessarily so. Not to mention that there was no obvious way of printing out the diagrams (I ended up taking screenshots and printing that).
If you use MS Visual Studio: If you can, try to use the older versions of Rose if you must. The new one (XDE) integrates with VS, and it completely drags VS down.
Kinda scary though, when you realize that the toolkit peer (i.e., people that can review) that is most likely to review patches is not paid. And, from what he blogged, has slight health problems that probably mean he should step away for a while.
IIRC, he's also thinking of a startup. See his blog (Google Feeling Lucky on his name), Feb 11 2005, third paragraph. I'm also guessing school is probably also a part of it:)
In the case of Mozilla, Secunia regularly regurgitates the offical Mozilla.org advisories (as is this case). Pretty much the time flow goes like:
vulnerabilities discovered; reported to mozilla.org
they sit for a while
eventually fixed and go into the next release
after a few days, mozilla.org opens up the security bugs fixed in that release and posts advisories
Secunia sees them and posts info on same advisories
people see Secunia with Mozilla vulnerabilities
And I know Secunia didn't come up with the list because
they link to mozilla.org (except in one case, where they linked to iDefense) as original advisories
"Please note: The information, which this Secunia Advisory is based upon, comes from third party unless stated otherwise. Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others."
I recognize names from the list - Phil Ringnalda is the Chatzilla guy, and Doug Turner is Minimo. So they already work on Mozilla a lot. That, and I'm in the list (probably undeserved).
The problem is that there's Mozilla (Gecko, platform) and Mozilla (Seamonkey, suite); Mozilla by itself is pretty much ambiguous.
The suite numbers seem to be following the platform numbers quite consistently (probably because way back there was only the suite, so they just had one set of numbers).
It probably doesn't help though if the summary uses both interpretations...
Because Mozilla doesn't have a bittorrent client?:)
Not to mention that the software updater doesn't know to update yet - they havn't turned on software update in fear of overloading the server. See here, if you havn't seen it already from all the other comments here.
Firefox uses Mozilla's cookie system - it has a cookies.txt file that holds all cookies, as opposed to IE's one text file per cookie.
Also, as I said above - I told Ad-aware to explicitly scan my Firefox profile directory, where my cookies are, and it didn't find the things it would for IE. So it seems to not understand Firefox cookies at all. Hence, whether it's the whole disk wouldn't matter.
And is Ad-aware scanning Firefox cookies? It doesn't seemt to be doing that for me.
In particular, it saw an 2o7.net cookie for IE but not Firefox (I explicitly told it to just scan my Firefox profile). I would expect more in Firefox because I rarely even use IE now...
Re:Too bad it still doesn't fix the RAM problem
on
Firefox 1.0.1 Released
·
· Score: 2, Interesting
Firefox 1.1 (/Mozilla 1.8) should be better - they very recently fixed a bug where (some?) closed tabs, with whatever content on it, got leaked. Not in 1.0.1 / Mozilla 1.7.6 because they're afraid of sticking too many changes into a security release and breaking stuff.
Bug 283063 if you want to check and know how (to prevent all of/. killing Mozilla's bug database).
Or if you had Firefox 1.0.1 / Mozilla 1.7.6 (or higher); those aren't actually out yet. They're supposed to be out RSN (apparently shooting for this week or next).
Of course, that's only what I got from reading/. and the Mozilla-related blogs; could be wrong.
Pfft... I've had it grow to ~1GB and die (because the system was unable to let Firefox allocate more memory, so Firefox crashed).
I think it's an image reference leak - about:cache?device=memory would show that a bunch of files are in use (even though that's the only tab open). If you open a new window and close the old one though, it seems to be sane again for a bit.
But the source code doesn't actually have an open license, does it? In fact, from the license before getting the toolbar:
b. YOU MAY NOT: (i) decompile, reverse engineer, disassemble, modify, rent, lease, loan, distribute, or create derivative works (as defined by the U.S. Copyright Act) or improvements (as defined by U.S. patent law) from the Yahoo! Software or any portion thereof.
So reading the source code would mean you have violated the EULA... I wonder if this will impact your ability to work on similar extensions (since you would have been, essentially, "contaminated"...)
The part about putting the Yahoo code into a chip/firmware is confusing though...
Probably depends on Windows version - on 2k/XP at least, Notepad is a Unicode app and can handle non-ASCII characters; not the case in 9x.
Use the command prompt; by default that wouldn't be able to handle the right characters and should show up as '?'. Actually, I think the default raster font for that just doesn't have the character.
That assume people even read any of it. It seems like we should assume that they don't... Kinda sad, really.
Agreed.
I wonder if this is in part due to MoFo being involved in open source - people have been complaining before (I believe rightly) that the decision making process over there is too opaque and we just get a final judgement handed down. Now that they try to open up, they end up giving kinda vague and confusing information. (Still feels opaque though, maybe that's just me)
Essentially, this just seems to be a bunch of blog posts / usenet postings / etc. (okay, there's one page at mozilla.org, so I guess that's official).
Or maybe they just suck at management. But then, good management = decisions at a single place = more opaque for random contributors.
Strange, Mozilla invokes guy in rubber suit defending mock Tokyo for me.
And for your last point - that's like saying Microsoft or Lotus, Red Hat, Novell - most company names don't necessarily make sense. What the heck is Macdonald's anyway? Some convience store like Mac's? And I guess Haliburton must be a hotel chain, or some sort of fish-selling place.
Actually, I recognize 5 of the 10 names at the bottom of the open letter from Mozilla related stuff, and I'm just a guy that watches from the sidelines. And the guy that wrote the letter (bz) is like some super-developer or something - he seems to touch the Mozilla tree all over the place (in a good way), is responsive and gets lots of stuff done. He's also expressed the desire to keep the suite before, so I'm not exactly surprised to see him being part of the effort.
I'm guessing the lack of interest before the offical "we're killing Seamonkey" announcement is because there seemed to have been no reason to step up while the situation was in limbo - backend stuff (shared w/ Firefox &c) was being done, there really wan't that much need to change the frontend drastically. Other than porting XPFE to the new toolkit I guess - not sure why they weren't majorly working on that beyond "sync blah with toolkit blah" bugs. Totally unfounded guess would be NIH.
(As I noted - I'm just a random bystander; heck, I don't even hang out on their IRC server)
Interestingly, it seems that the default theme has a slight edge on the left side that isn't a tab, so double left clicking on the left edge works. WinXP, XP's theming is off. There's also a tiny strip above non-active tabs (also pretty much impossible to get to).
Definately not as easy as the new tab button though; it's so small that it only really works when the window is maximized (Fitt's law).
For sidebars, Firefox approximates this - bookmark the page, then go to Bookmarks Manager, context-click, Properties, and check "open in sidebar".
Not quite the same as Mozilla's sidebar, but it's closer.
I agree that Rose is a pain. (Caveat: student here, so maybe we just suck)
We tried to draw some class diagrams, sequence diagrams, etc. After struggling with Rational Rose, we found it easier to just do things semi-manually in Visio, rather than use the built-in capabilities of Rational Rose. Havn't tried using the code generation / reverse engineering capabilities of Rose though. In generally, I just find its UI to be annoying, even if its output isn't necessarily so. Not to mention that there was no obvious way of printing out the diagrams (I ended up taking screenshots and printing that).
If you use MS Visual Studio: If you can, try to use the older versions of Rose if you must. The new one (XDE) integrates with VS, and it completely drags VS down.
Good thing then that MoFo isn't paying him :)
Kinda scary though, when you realize that the toolkit peer (i.e., people that can review) that is most likely to review patches is not paid. And, from what he blogged, has slight health problems that probably mean he should step away for a while.
IIRC, he's also thinking of a startup. See his blog (Google Feeling Lucky on his name), Feb 11 2005, third paragraph. I'm also guessing school is probably also a part of it :)
(Who are the six that mconnor mentioned anyway?)
And I know Secunia didn't come up with the list because
The problem is that there's Mozilla (Gecko, platform) and Mozilla (Seamonkey, suite); Mozilla by itself is pretty much ambiguous.
The suite numbers seem to be following the platform numbers quite consistently (probably because way back there was only the suite, so they just had one set of numbers).
It probably doesn't help though if the summary uses both interpretations...
Because Mozilla doesn't have a bittorrent client? :)
Not to mention that the software updater doesn't know to update yet - they havn't turned on software update in fear of overloading the server. See here, if you havn't seen it already from all the other comments here.
Ad-Aware SE Personal, 1.05, did the auto-update.
WinXP (not like that matters)
Maybe it's because I have Personal?
Wow.. :)
Where did you get the setup from? Just asking because the image has references to 2004-09-10 (Seamonkey 1.7.3 branch?)
Since Firefox 1.0 was ~1.7.5, that would mean it's a pre-1.0 installer... Maybe try re-downloading it? Or from a different mirror?
Firefox uses Mozilla's cookie system - it has a cookies.txt file that holds all cookies, as opposed to IE's one text file per cookie.
Also, as I said above - I told Ad-aware to explicitly scan my Firefox profile directory, where my cookies are, and it didn't find the things it would for IE. So it seems to not understand Firefox cookies at all. Hence, whether it's the whole disk wouldn't matter.
Of those 500, how many are cookies?
And is Ad-aware scanning Firefox cookies? It doesn't seemt to be doing that for me.
In particular, it saw an 2o7.net cookie for IE but not Firefox (I explicitly told it to just scan my Firefox profile). I would expect more in Firefox because I rarely even use IE now...
Firefox 1.1 (/Mozilla 1.8) should be better - they very recently fixed a bug where (some?) closed tabs, with whatever content on it, got leaked. Not in 1.0.1 / Mozilla 1.7.6 because they're afraid of sticking too many changes into a security release and breaking stuff.
/. killing Mozilla's bug database).
Bug 283063 if you want to check and know how (to prevent all of
Since you're linking to the en-US version anyway...
BitTorrent links in case the servers really go to crap. (Theirs, not mine)
That would work until restarting the browser.
/. and the Mozilla-related blogs; could be wrong.
Or if you had Firefox 1.0.1 / Mozilla 1.7.6 (or higher); those aren't actually out yet. They're supposed to be out RSN (apparently shooting for this week or next).
Of course, that's only what I got from reading
Yes they have. Or at least somebody working for MoFo has.
Pfft... I've had it grow to ~1GB and die (because the system was unable to let Firefox allocate more memory, so Firefox crashed).
I think it's an image reference leak - about:cache?device=memory would show that a bunch of files are in use (even though that's the only tab open). If you open a new window and close the old one though, it seems to be sane again for a bit.
So reading the source code would mean you have violated the EULA... I wonder if this will impact your ability to work on similar extensions (since you would have been, essentially, "contaminated"...)
The part about putting the Yahoo code into a chip/firmware is confusing though...
I havn't used it, but this is meant to emulate that.
Probably depends on Windows version - on 2k/XP at least, Notepad is a Unicode app and can handle non-ASCII characters; not the case in 9x.
Use the command prompt; by default that wouldn't be able to handle the right characters and should show up as '?'. Actually, I think the default raster font for that just doesn't have the character.
Well, there is a blocking-aviary1.0.1 flag, so it looks like there will be a 1.0.1. There's about 12 bugs with it set.
I have no info on the timeframe though.