[X] My Assistant

Because you like poop.

I think I've a fucking man cold again. If I suddenly stop posting, you all know what got me.

GRID?

Did the missus let you use her arsehole as a cunt? Y'now, 'cause of the whole birthday thing.

On a related note: The idea of bug catching and gift giving is hilarious.

Just found out what grid is...

More of an ass man, myself.

Word...

Because you like poop.

...diggity.

Love me some anus, too.

Chrome is slow. :/

I know so many people that hopped on the Chrome bandwagon because it's a Google product. I mean, never mind the fact that it's the exact same code base and a slightly modified and renamed GECKO engine which Firefox uses but with a customized Safari GUI. I mean, I use a Safari type GUI with my Firefox and don't load my extensions with garbage that eats up cache such as Stumble, typically my extensions have a preference of fetching offline data with Foxytunes or they show me stuff that I'd have to open up a window to view so whatever processes it's doing is happening anyway with Download Statusbar. Heck, I have maybe 3 tabs at most at a single time. The big thing that Chrome has over Firefox (at the moment) is that each tab is an individual process, so you can cut out of one tab without dumping the whole sandbox.

ADDENDUM: Basically, anything you get that you can overload with extensions on a crummy computer will get slow fast, especially if you have a ton of tabs open. Which is why the browser one chooses isn't important, it's the ways the end user customizes it.

This post has been edited by radixius: Jan 4 2011, 19:31

I have no idea. I was going on recommendations from others. Admittedly, that process rarely works out for me.

Actually, firefox has very poor garbage collection, which leads to a problem with memory leak (i.e.: forgetting to delete dynamic objects after use). Chrome doesn't have that. That means that leaving firefox on for one day will consume most of your RAM, while Chrome will not.

Chrome's problem is that not all pages load correctly (which can be a huge pain in the ass). Safari feels clunky due to its fetching mechanism - it also has poor security. And Opera, though faster than any of the others (albeit only noticeably for mobile devices, or in slower connections), suffers from poor security as well as the same problems chrome suffers from.

Chrome's problem is that not all pages load correctly (which can be a huge pain in the ass). Safari feels clunky due to its fetching mechanism - it also has poor security. And Opera, though faster than any of the others (albeit only noticeably for mobile devices, or in slower connections), suffers from poor security as well as the same problems chrome suffers from.

Opera just got extensions. Goodbye to that quickness, dawgs.

Actually, firefox has very poor garbage collection, which leads to a problem with memory leak (i.e.: forgetting to delete dynamic objects after use). Chrome doesn't have that. That means that leaving firefox on for one day will consume most of your RAM, while Chrome will not.

Is this why flash breaks after a few days of having firefox up? Seamonkey's flash tends to break if you leave a page using it up for a few days, but usually works again once you close all tabs with flash in them (refresh works fine for a single flash tab).

Is this why flash breaks after a few days of having firefox up? Seamonkey's flash tends to break if you leave a page using it up for a few days, but usually works again once you close all tabs with flash in them (refresh works fine for a single flash tab).

Yes. Especially on youtube. But then again, flash has several bugs on its own that cause it to be a horrible memory hog. It's almost on par with java for the list of worse written virtual machines of all time.

In conclusion(this is aimed at everyone), if you're one of those programmers who forgets to free up memory (it's one fucking line of code, damn you), I hate you. I also hate you if you use recursion when a normal "while" will suffice (another of the worst memory hogs of all time).

Weird, if I leave grooveshark up in seamonkey but have it paused it doesn't bug out when I restart it. If I leave it at the end of the playlist, it will.

Weird, if I leave grooveshark up in seamonkey but have it paused it doesn't bug out when I restart it. If I leave it at the end of the playlist, it will.

Grooveshark is html5, not flash. It used to be flash. Now it's not. It's much harder to save sessions in html5, as saving requires events, unlike flash.

EDIT: This is turning into tech chat :<

This post has been edited by noahbody: Jan 5 2011, 09:21

These days, any conversation with Marvin tends to turn into one of those.

In conclusion(this is aimed at everyone), if you're one of those programmers who forgets to free up memory (it's one fucking line of code, damn you), I hate you. I also hate you if you use recursion when a normal "while" will suffice (another of the worst memory hogs of all time).

I fyou're one of those programmers who think garbage collection is a good idea, as opposed to deleting everything exactly when you know you won't need it anymore, I hate you. I think we only have garbage collection because of morons who couldn't learn how to manage memory properly.

I fyou're one of those programmers who think garbage collection is a good idea, as opposed to deleting everything exactly when you know you won't need it anymore, I hate you. I think we only have garbage collection because of morons who couldn't learn how to manage memory properly.

Garbage collection makes me rage (the instant, not the manual kind, as "delete variable;" is also called garbage collection). I will reiterate: it's one line of code. int penis is not in use anymore? delete penis; That is not hard, people. And everyone who says: "Oh, but Java does it all for me!" Not it fucking doesn't. Its garbage collection algorithm isn't fail-proof, and in some cases it makes it worse. Also, Java uses just-in-time compilation, meaning that the fact that you're not deleting the damn variables is making your program slower.

AND AGAIN I CANNOT STRESS THIS ENOUGH: If you're not using Trees (Binary, B, B+, etc), DO NOT FUCKING USE RECURSION. There are very few instances outside of trees where a recursion can't be solved with whiles/fors/loops. Sometimes it's going to look ugly, but if you're writing code, you're doing it to be functional, not pretty. Pretty is secondary.

This post has been edited by noahbody: Jan 5 2011, 21:32

*insert nerd speak to fit in*