The agitation was to the point that where if someone heard it for a sustained long time they could seriously go insane or even try to kill themselves. It was bad. The sense of relief I felt when the noise was turned off was quite profound.
That's basically how I feel about CNN in airport departure lounges.
My parents moved to a house where the neighbor had a still-living-at-home loser 20s son who kept blasting reggae music. On my first return from college, I got out a couple of my favorite industrial music CDs and cranked up the amplifier. That was it, no more reggae.
Same thing worked at college against inconsiderate nearby students. In particular, Cabaret Voltaire's remix of "Sensoria" sounds great at high volume, and will drown out almost anything. If that fails, Lou Reed's "Metal Machine Music" can clear buildings. I generally prefer headphone listening, but if someone starts a hifi war, by god I'll finish it.
But on the other hand, it's only a matter of time before americans will ban both childbirth and nursing, as they expose children to breasts and female genitalia.
Right, but my point is that's not leaking memory--the memory is still being tracked, and may eventually be freed by the program. It's just being a memory hog. It's a different problem to a real memory leak as found in C/C++/Objective-C, which is when the last pointer to some allocated memory is thrown away without deallocating the memory. That's a real leak, because the program can never free the memory.
By your definition (objects in memory that cannot affect any future computation), you can have garbage in programs that don't even allocate memory, for example if there's dead code or library bloat. Does "Hello World" have a memory leak? It certainly has a lot of garbage when it's linked with libc, and maybe the academic literature would agree that it has a memory leak, but I think you'd confuse a lot of people if you used that definition in the real world.
I don't think memory hogging = memory leaking, and whether something can affect future computation is not always definable. I mean, what about if Amazon's shopping cart system is keeping my cart contents in memory?
Well, I'm old school in the sense that I wrote Z80 machine code back in the late 70s by hand-assembling it. But on the other hand, these days I wouldn't touch a programming language that didn't have automatic memory management, unless I had a really, really compelling need to do so. I wonder what that would make me?
Actually, I'm a strong believer in dynamic typing, so that probably makes me Evil in the eyes of Java zealots.
And the 2nd biggest con is that a lot of developers can't believe you can have memory leaks in a GC-based language, won't look for them until you rub their nose in them, and don't really know how to find them when they look.
I've always thought that the use of the term "memory leak" to describe resource management problems in Java is a really poor choice, as it's quite a different problem from a memory leak in (say) C.
Keeping memory allocated and referenced for longer than you need it isn't really a leak, to my mind. It's just bad programming. To me, a memory leak is when you lose the pointers to a piece of allocated memory, so the code is no longer able to deallocate it.
In other words, your developers might give a better answer if you ask "Are there objects you keep around longer than necessary?", rather than "Are there memory leaks?"
The sets didn't include step-by-step instructions for making any of these things. AAMOF, I don't remember any instruction sheets at all.
Not only did most sets come with instruction sheets as far back as 1964 or so, there were also books of additional instructions for making more stuff. By 1966 there were over 50 sets, including the LEGO train system. By 1970 they had gears and cogs, the forerunner to TECHNIC.
So I think either you're in your 50s or older, or your memory is faulty. Or you did like Ralph Wiggum and ate the instructions.
What would I do about it? Make a brick out of a Nintendo Game boy advance, where you can program it and plug it in without a computer. Make the user interface easier for first timers.
They did something like that. I have the set, which I bought because the full RCX required Windows. It has a blue CPU brick rather than a yellow one, and there's an add-on infra-red remote available.
It was discontinued fairly quickly, so I'm guessing it didn't sell well.
Part of the problem was probably that the brick's functionality was fairly limited, and the upgrade path was to buy the full $200 Mindstorms kit.
I think a better approach, as you say, would be to have an RCX programming cartridge for a GBA. Tying Mindstorms to a Windows PC is a bad marketing move; I'm guessing most parents don't want the floor around the PC to be covered with LEGO.
Or maybe I'm just bitter that I blew threw 3 PS2s in 3 years.
Jeez, what were you doing with them? My first one lasted until last year, and I only got rid of it then because I was moving and wanted a slimline model with progressive scan.
The moment when she begins to grasp that a health care waiting list is a concept alien to most sick Americans...
Having any healthcare coverage whatsoever is a concept alien to the majority of Americans.
I'm assuming the Canadian lady could get private medical treatment in Canada, if she had the money, just like in the UK. Since she's waiting, she presumably doesn't have the money--so in America, she'd be fucked.
VIA C3 processor. Socket 370, up to 1GHz. Runs on 11W of electricity. If you get a VIA motherboard, you'll probably find that everything has open source Linux drivers. (I know the EPIA M-series do.)
Now, anyone know of a socket 370 motherboard that'll take 4 or more SATA drives?
Slashdot Mirror
And presumably tithes are theft too, right?
That's basically how I feel about CNN in airport departure lounges.
My parents moved to a house where the neighbor had a still-living-at-home loser 20s son who kept blasting reggae music. On my first return from college, I got out a couple of my favorite industrial music CDs and cranked up the amplifier. That was it, no more reggae.
Same thing worked at college against inconsiderate nearby students. In particular, Cabaret Voltaire's remix of "Sensoria" sounds great at high volume, and will drown out almost anything. If that fails, Lou Reed's "Metal Machine Music" can clear buildings. I generally prefer headphone listening, but if someone starts a hifi war, by god I'll finish it.
And then look up "Daily Mail" and "moral panic".
One more reason to get rid of CRTs.
I just got rid of the last glass tube in our house, and it's a wonderful improvement.
(In mid 30s, still capable of hearing TV whine.)
Here in Texas, a woman was arrested for "child porn" for being photographed breastfeeding her baby.
Granted, the charge was later dropped, but...
Right, but my point is that's not leaking memory--the memory is still being tracked, and may eventually be freed by the program. It's just being a memory hog. It's a different problem to a real memory leak as found in C/C++/Objective-C, which is when the last pointer to some allocated memory is thrown away without deallocating the memory. That's a real leak, because the program can never free the memory.
By your definition (objects in memory that cannot affect any future computation), you can have garbage in programs that don't even allocate memory, for example if there's dead code or library bloat. Does "Hello World" have a memory leak? It certainly has a lot of garbage when it's linked with libc, and maybe the academic literature would agree that it has a memory leak, but I think you'd confuse a lot of people if you used that definition in the real world.
I don't think memory hogging = memory leaking, and whether something can affect future computation is not always definable. I mean, what about if Amazon's shopping cart system is keeping my cart contents in memory?
Well, I'm old school in the sense that I wrote Z80 machine code back in the late 70s by hand-assembling it. But on the other hand, these days I wouldn't touch a programming language that didn't have automatic memory management, unless I had a really, really compelling need to do so. I wonder what that would make me?
Actually, I'm a strong believer in dynamic typing, so that probably makes me Evil in the eyes of Java zealots.
A much better solution would be to make them non-transferable.
This isn't news. This is an announcement that there's going to be some news in 2006. What a waste of space.
I've always thought that the use of the term "memory leak" to describe resource management problems in Java is a really poor choice, as it's quite a different problem from a memory leak in (say) C.
Keeping memory allocated and referenced for longer than you need it isn't really a leak, to my mind. It's just bad programming. To me, a memory leak is when you lose the pointers to a piece of allocated memory, so the code is no longer able to deallocate it.
In other words, your developers might give a better answer if you ask "Are there objects you keep around longer than necessary?", rather than "Are there memory leaks?"
Or maybe I'm the only one.
Not only did most sets come with instruction sheets as far back as 1964 or so, there were also books of additional instructions for making more stuff. By 1966 there were over 50 sets, including the LEGO train system. By 1970 they had gears and cogs, the forerunner to TECHNIC.
So I think either you're in your 50s or older, or your memory is faulty. Or you did like Ralph Wiggum and ate the instructions.
They did something like that. I have the set, which I bought because the full RCX required Windows. It has a blue CPU brick rather than a yellow one, and there's an add-on infra-red remote available.
It was discontinued fairly quickly, so I'm guessing it didn't sell well.
Part of the problem was probably that the brick's functionality was fairly limited, and the upgrade path was to buy the full $200 Mindstorms kit.
I think a better approach, as you say, would be to have an RCX programming cartridge for a GBA. Tying Mindstorms to a Windows PC is a bad marketing move; I'm guessing most parents don't want the floor around the PC to be covered with LEGO.
There's no need to use a JDBC/ODBC bridge. DB2 has a Type IV JDBC driver.
Not gonna happen. They need to make you click through the EULA. (Or at least, they believe they do.)
My passion is whining about PDFs rather than configuring my browser to download them instead of displaying them inline.
Jeez, what were you doing with them? My first one lasted until last year, and I only got rid of it then because I was moving and wanted a slimline model with progressive scan.
For a good exploration of this scenario, read His Master's Voice by Stanislaw Lem.
Having any healthcare coverage whatsoever is a concept alien to the majority of Americans.
I'm assuming the Canadian lady could get private medical treatment in Canada, if she had the money, just like in the UK. Since she's waiting, she presumably doesn't have the money--so in America, she'd be fucked.
There are a lot more Socket 370 motherboards than Pentium-M motherboards.
Plus, why pay Intel prices?
VIA C3 processor. Socket 370, up to 1GHz. Runs on 11W of electricity. If you get a VIA motherboard, you'll probably find that everything has open source Linux drivers. (I know the EPIA M-series do.)
Now, anyone know of a socket 370 motherboard that'll take 4 or more SATA drives?
The really wonderful thing about MEPIS is that you can use the entire Debian software repository safely, unlike Ubuntu.
I see no statement on the Rosetta@Home web site about who owns any results of the research, whether it will be patented, and so on.
Folding@Home at least say that they are a nonprofit and will not profit from selling or licensing their research.
Hey, some people have been screaming for it. Not my place to speculate why.