Firefox
Friday, 21. November 2008, 15:47:50
I downloaded Firefox 3 today because I like the CSS developer tools that you can install with it. I use it to fix the CSS changes that the idiots at Opera insists on subjecting on us. I did fix the layout (mostly). But I can't fix the layout for logging in because I can't move background images, although the login box looks fine. It's just the rest of the blog that gets screwed up, but oh well. I'm hoping I can eventually move this blog somewhere new.
Hey, if you work at Opera, STOP CHANGING THE HTML TAG AND CSS NAMES!!! Jeez, is that too hard to do?
Anyways, what happened to Firefox? It takes like 5 to 10 seconds before even loading a page up. I only use it on my old test boxes, but still. There's no reason to be THAT slow. Has Firefox really turned into a big pile of garbage? What happened to it? It used to be so fast.
While I'm at it, anyone want the width of this blog to be larger? Or should I leave it the same?
Hey, if you work at Opera, STOP CHANGING THE HTML TAG AND CSS NAMES!!! Jeez, is that too hard to do?
Anyways, what happened to Firefox? It takes like 5 to 10 seconds before even loading a page up. I only use it on my old test boxes, but still. There's no reason to be THAT slow. Has Firefox really turned into a big pile of garbage? What happened to it? It used to be so fast.
While I'm at it, anyone want the width of this blog to be larger? Or should I leave it the same?
WIDGETIZE
Andres Rodriguez Guapacha # 21. November 2008, 16:03
I was also thinking in learning CSS to modify my Blog a bit, but... I was suddenly enlightened by the KISS principle (again)
And yes, firefox has become fully loaded... I only use it when I cannot use Opera because some dumb web developer thinks people only uses IE and Firefox.... or maybe he/she doesn't think at all... who knows the difference?
Vladas # 21. November 2008, 16:22
It seems they have some big problems with garbage collector, which seems working exclusively and not in separate thread. Furthermore, it is slow on resolving object references - probably they've changed static GC behaviour (simply counting referencies) to dynamic (rechecking refs against reality). Perhaps by this they hope to avoid cyclic reference problems (or referencies in closures - which was a real problem in IE) with such dynamic GC behaviour.
Probably they must have been consulted with Google Chrome developers for making things better...