Depends on how you define a "leak.".NET (and i think java???) waits until an allocation request fails before it collects any garbage. As a result, long-running.NET apps tend to fill all availiable memory and swap before stabilizing their memory usage. (i'm thinking of SharpDevelop in particular, there aren't many other large.NET apps out there)
And I don't have to remind anyone who uses Windows, the OS doesn't behave well at all when its main memory and swap are filled. So in my opinion, having long-running managed apps makes for a much worse interactive user experience.
tangentially, remember that longhorn is planning to move many more shell programs to managed code...
Re:amazing programing in 256k, and no serious bugs
on
Apollo 12 at 35
·
· Score: 3, Informative
What's REALLY incredible is that that 2K of memory was hand-soldered! Forget programming bugs, I'd worry more about short circuits! craziness.
Listen up feckers, this isn't a patent for `sudo (8)!' Another poster said it was a patent for "runas" but that's not true either. If you read it carefully, it's for an administrative _process_, not a _program_ like sudo. So this means that there is a single system-wide "security process" that you request to perform restricted actions for you.
It's a slight destinction, I agree, but that's the whole point of patents. You only patent a specific way of doing things, any slight change in the implementation is a different (patentable) innovation! So we should patent the FUCK out of sudo(8) and chmod(1) and all the rest of them.
Tangentially, we can all agree that the implementation this patent covers is a piece of shit. One long-lived process responsible for all authentication? Can you imagine the attack surface it's exposing?
The only reason to learn Fortran today is to work with old code. The old code is invariably written in F77, since it is without a doubt from the 70s itself.
there is no good reason to develop a new application on fortran today.
well, except for massively parrallel calcuations using parallel optimizing compilers.
but write it in F77 anyway, it's all you need.
if you really need dynamic memory or pointers, write it in C. it's faster, easier to optimize with plain gcc, and also from the 70s.
or just buy freaking matlab or mathmatica or something.
have you ever used a $658 dell? i'm not sure what they did, but i think the memory, video and hard drive are all coming through a layer of cheesecloth in the north bridger. *electric* cheesecloth, mind you.
combine the shitty architecture with the omnipresent windows XP, and you have a really really slow and frustrating computer to use. when you start an app the whole UI will lock for 3-4 seconds at a time, no repaints, no mouse movments, no nothing.
the three or four times you ever need to do something processor-intensive, sure it might finish fast (if the dataset is small enough to fit in L2 cache, of course). other than that you're screwed.
the new G5 systems have incredible bandwidth. incredible. combine that with the BSD scheduler and cache management, and i bet even Panther will seem fast.
like you said, if it seems fast, it is fast. and dell's sure ain't.
people need to stop and fucking think for like a second. of _course_ they're not human. spider-man is a genetically mutated metahuman, wolverine's a cyborg augment, etc...
my favorite quote:
"Here's a guy who changes his clothes in a phone booth and flies through the air," says Mr. Cooper. "Does that mean he's now an animal?"
no you moron, it means he's a SPACE ALIEN.
his kryptonian biological makeup was enhanced by the light from earth's yellow sun, remember?
batman and robin, on the other hand, are just a couple of best buds who wear capes.
this ain't religion people, it's law. just read the damn books and the answer is fairly obvious.
Why is this person asking slashdot? For an answer. Google may be great but there's a lot of garbage out there. I'm sure the poster was hoping someone could help him out by sharing some personal experience.
It's a great compliment to the community that people can ask a question assuming there will be an informed, helpful response. The knee-jerk "google it" reaction that is so common these days is tearing apart this vital facet of the community.
this whole/. thing is about community, people. let's be helpful if we can. and remember, there's no such thing as a stupid question, just unhelpful answers.
Wrong. Electric motors and internal combustion engines are rated for power differently. "Petrol" engines are rated for peak power delivery, whereas electrics are rated for something like their 80% duty cycle power. Anyway, the rating for an electric motor is much closer to the average power delivered over all speeds than that for a gasoline engine.
Plus, the two types of locomotive devices have different power curves. Electrics deliver peak power at standstill (when it's noticeable) while gas engines have to wait until redline. Electic motors generally have more torque, too.
In short, the performance claims are quite reasonable.
A modular, fuel-cell vehicle will certainly be easier to manufacture and better for the environment, but the resulting cars will drive like slop.
The main problem here is that the "skateboard" technique of manufacturing is really a throwback to the good ol' "body on frame" method of car design. Just like your great-granddad's Ford Model T from 1903, the body is a separate unit from the driveline and suspension. As a result, stiffness will be much, much, much lower than the cars of today, and ride quality will be wobbly and uncomfortable.
But wait, you ask. Won't the new "drive by wire" stuff help this? In a word, no. The truth here is that the only stressed structural member will be the flat "skateboard" and no electronics can do anything about that. Modern cars use a "unibody" design where the entire passenger cabin, including walls and roof, contribute stiffness. This is the reason that a modern shitbox (like a Kia) drives so much better than an antique shitbox like that Model T. GM's plan will only serve to give us postmodern shitboxes.
Don't get me wrong, I'm not down on tech. I think that electric motors will be the way of the future. They're lighter and more efficient than internal combustion engines (ICEs). They develop their peak power and torque from standstill instead of at redline. They can run at road speed, so there's no need for a pesky transmission.
If GM really wants to set the world on fire, they need to make their assembly lines modular and not the cars. I forsee a world where they can pump out custom spaceframe chassis for fuel-cell powered vehicles using four-wheel direct electric drive. If they were really smart, they'd work on driving the costs of composites down so we get carbon-fiber monocoque street cars with bullet-proof kevlar saftey cells.
But this is GM we're talking about. They brought you the new Impala. Oooh, and don't forget the Aztek. Yay.
man, if i'd only known about this i would have rescheduled my trip!
seriously, ireland is an awesome place for this... the best hiking and beer you'll ever find, plus friendly friendly people.
p.s. the accent is really good out west... they say they talk so fast 'cause there's so much to say! be sure to ask for directions before going anywhere, well worth it.
There is an insightful analysis of the legal decision at penny arcade, written by one "Atticus XI - Lawyer of Doom." Many lucid points raised on the side of those who are good and just.
"Forget all you heard about.NET." This is a good quote. So let's for a moment forget about the superfluous features of C# and the.NET Framework, like machine-independance. What does it get you in the end? Faster application development.
I think that Miguel and the whole GNOME community is tired of being "second-best" in the desktop environment competition with KDE. The simple fact is that (not unlike Win32) plain old C and GTK+ are complex, error-prone development environments that no one will much miss. In fact if you look at GTK+, much of the GNOME team's time has been spent trying to copy object-oriented design features that are intrinsically availiable in other languages.
KDE has a secret weapon in its usage of C++ and QT; the true object-oriented approach is simply better and faster for large projects. If you haven't programmed, you won't realize that QT is basically "Java Swing for C++." The KDE project pushed out their next-generation desktop months ahead of the GNOME boys and they're not looking back now.
I say, hurrah to the GNOME team if they do finally pick a new, better, faster development environment. However, I am worried that instead of relying on proven, existing, free (as in GPL) technology like g++ or QT3 they will waste entirely too much time reimplementing the basics.
As usual. Did I say that? Don't want to sound biased!
|-) <----- geordi.
Re:OK, let's kill soldiers instead.
on
The Drone War
·
· Score: 2, Interesting
The idea here is that any sort of war is immoral. Sending mechanical surrogates to kill people without consequences only encourages more death.
a word about the lack of understanding of basic GUI concepts:
when i was in grade school, my grandpa got a macintosh, and it was soooo much cooler than my PS/2 model 25 (trying to get you guys set in the timeline.)
Anyway, the mac came with this audio tape tutorial that explained what these "icons," "windows," and "menus" were, and how to "click" "double-click" and "drag" to interact with them. It even had fun games where you had to pull a mouse through a maze and swat flies and things.
Anyway, I think that current GUIs assume that everyone has basic proficiency with these skillsets when many many people do not. There needs to be a basic "how to mouse" tutorial shipped with every OS that fires up on the first boot (and is availiable easily later).
With this, I could show my mom where the "ON" switch is (it's right on the front, it's sooo easy these days) and let her learn to use the comp for 20 minutes before i show her how to type a letter.
C'mon, that's a toyota supra with a bigass 6-cylinder turbo engine in it, not a little 4-cylinder rice-burning "hon-duh."
and i think it was an impala SS if i'm not mistaken.
anyway, if you watched it, the SS blew a cylinder and that's why it didn't eat the toyota for lunch. in drag racing and processors there's no place for finesse.
the athlon is a brute of a chip, a brute that can be cranked to higher speeds than anyone imagined, and that's why it beats the "high-revving" (rice-burning?) P4s. good thing it doesn't have to run in the twisties like a road racer...
I was just thinking in the shower this morning, wouldn't it be cool to have a SCUMM interpreter? Then we can make high-quality adventure games and all that. Opensource is bad-ass dude. Wish and ye shall receive. (Return in kind of course)
There is a much easier way to use ssh-agent. Rather than starting the server from the first bash shell and then checking if it's running for every other shell, it's possible to simply say "ssh-agent [program]" and then that program and any of its children will know about the private key cache.
For example, on my system I added another login choice to KDM called "kde2-ssh". I created a corresponding shell script cleverly called "kde2-ssh" that contains only "exec ssh-agent/usr/X11R6/bin/kde2". You could use any window manager you like. (attention all sprockets: the "exec" is there so you don't waste a process)
After the window manager starts you simply run "ssh-add" once and every program started by X will know about ssh-agent. Pretty dope, huh?
Oh yeah, if you run ssh-add from a script (i.e. wherever there is no stdin) it will pop up a nice X dialog box for your password. Extra tasty crispy dope, i'd say. I put a call to ssh-add in my handy KDE "Autostart" folder so now i'm the envy of all my friends. yes, all two of them.
Serial ATA is designed to be hardware-compatible with current ATA. One can assume that the spec will account for 48-bit addressing. In the meantime, remember that widening the address space on a parallel bus will increase costs; more wires, more costs.
New, huge drives can be built with nary a concern over the serial or parallel-ness of the interface.
This pisses me off, that the SDMI expects consumers to be happy buying so-called "perfect" digital copies of music that in fact have known, intentional defects in sound quality introduced as access control methods.
I'm especially taking issue with "Technology C". From Felten's paper on the attack:
By taking the difference of samp1c.wav and samp2c.wav, bursts of narrowband signal are observed... centered around 1350 Hz.... [W]e passed the signal through a bandstop filter centered around 1350Hz. Our submissions were confirmed by SDMI oracle as successful.
Think about this for a second! They simply removed audio information and then the sound sample was accepted as genuine. This means that the audio information they removed was never there to begin with. Argh.
Oh, and kids... 1350 Hz is not some whacky frequency that only bats can hear. It's somewhere around E above high C, which is a perfectly fine note, when you think about it. I mean, I play trumpet, I love listening to trumpet music. Cutting out 1350 Hz will effect everyone from Maynard Ferguson to Miles Davis (well maybe not Miles Davis.;-)
Your assertion that the gameboy was an inferior design than the gamegear is not entirely correct. Remember, hardware power, graphics and sound and the like are only one portion of the design parameters of a portable unit. Recall that the sega gamegear was TWICE as big as a game boy. My brothers actually had both of the systems. Which came with us on the car trips? Not the game gear with it's carrying case (complete with shoulder strap). Game Boy was a superior product to game gear because the design compromises made at the hardware level enabled big gains in the usability level.
How does this apply to dreamcast/ps|2? We must remember that hardware is only half of the equation. For example, which is more important to the gaming audience, DVD playback or 4-player games? Will US audienes be put off by the lack of quality launch titles (due to sony's extreme hubris when dictation development environment, i might add)?
My prediction: Dreamcast fades because sony is a bunch of bitches. But nintendo kicks everyone's ass next year with the gamecube, which offers a nirvana of power, form factor and ease of development.
Slashdot Mirror
Depends on how you define a "leak." .NET (and i think java???) waits until an allocation request fails before it collects any garbage. As a result, long-running .NET apps tend to fill all availiable memory and swap before stabilizing their memory usage. (i'm thinking of SharpDevelop in particular, there aren't many other large .NET apps out there)
And I don't have to remind anyone who uses Windows, the OS doesn't behave well at all when its main memory and swap are filled. So in my opinion, having long-running managed apps makes for a much worse interactive user experience.
tangentially, remember that longhorn is planning to move many more shell programs to managed code...
What's REALLY incredible is that that 2K of memory was hand-soldered! Forget programming bugs, I'd worry more about short circuits! craziness.
Listen up feckers, this isn't a patent for `sudo (8)!' Another poster said it was a patent for "runas" but that's not true either. If you read it carefully, it's for an administrative _process_, not a _program_ like sudo. So this means that there is a single system-wide "security process" that you request to perform restricted actions for you.
It's a slight destinction, I agree, but that's the whole point of patents. You only patent a specific way of doing things, any slight change in the implementation is a different (patentable) innovation! So we should patent the FUCK out of sudo(8) and chmod(1) and all the rest of them.
Tangentially, we can all agree that the implementation this patent covers is a piece of shit. One long-lived process responsible for all authentication? Can you imagine the attack surface it's exposing?
The only reason to learn Fortran today is to work with old code. The old code is invariably written in F77, since it is without a doubt from the 70s itself.
there is no good reason to develop a new application on fortran today.
well, except for massively parrallel calcuations using parallel optimizing compilers.
but write it in F77 anyway, it's all you need.
if you really need dynamic memory or pointers, write it in C. it's faster, easier to optimize with plain gcc, and also from the 70s.
or just buy freaking matlab or mathmatica or something.
have you ever used a $658 dell? i'm not sure what they did, but i think the memory, video and hard drive are all coming through a layer of cheesecloth in the north bridger. *electric* cheesecloth, mind you.
combine the shitty architecture with the omnipresent windows XP, and you have a really really slow and frustrating computer to use. when you start an app the whole UI will lock for 3-4 seconds at a time, no repaints, no mouse movments, no nothing.
the three or four times you ever need to do something processor-intensive, sure it might finish fast (if the dataset is small enough to fit in L2 cache, of course). other than that you're screwed.
the new G5 systems have incredible bandwidth. incredible. combine that with the BSD scheduler and cache management, and i bet even Panther will seem fast.
like you said, if it seems fast, it is fast. and dell's sure ain't.
Every new release of windows runs slower than the one before. Looks to me like MS is trying to stay ahead of the curve.
people need to stop and fucking think for like a second. of _course_ they're not human. spider-man is a genetically mutated metahuman, wolverine's a cyborg augment, etc...
my favorite quote:
"Here's a guy who changes his clothes in a phone booth and flies through the air," says Mr. Cooper. "Does that mean he's now an animal?"
no you moron, it means he's a SPACE ALIEN.
his kryptonian biological makeup was enhanced by the light from earth's yellow sun, remember?
batman and robin, on the other hand, are just a couple of best buds who wear capes.
this ain't religion people, it's law. just read the damn books and the answer is fairly obvious.
Why is this person asking slashdot? For an answer. Google may be great but there's a lot of garbage out there. I'm sure the poster was hoping someone could help him out by sharing some personal experience.
It's a great compliment to the community that people can ask a question assuming there will be an informed, helpful response. The knee-jerk "google it" reaction that is so common these days is tearing apart this vital facet of the community.
this whole /. thing is about community, people. let's be helpful if we can. and remember, there's no such thing as a stupid question, just unhelpful answers.
The movie is so excellent because it uses many of the novel's speeches word-for-word. i am almost certain that appears in the book.
Wrong. Electric motors and internal combustion engines are rated for power differently. "Petrol" engines are rated for peak power delivery, whereas electrics are rated for something like their 80% duty cycle power. Anyway, the rating for an electric motor is much closer to the average power delivered over all speeds than that for a gasoline engine.
Plus, the two types of locomotive devices have different power curves. Electrics deliver peak power at standstill (when it's noticeable) while gas engines have to wait until redline. Electic motors generally have more torque, too.
In short, the performance claims are quite reasonable.
A modular, fuel-cell vehicle will certainly be easier to manufacture and better for the environment, but the resulting cars will drive like slop.
The main problem here is that the "skateboard" technique of manufacturing is really a throwback to the good ol' "body on frame" method of car design. Just like your great-granddad's Ford Model T from 1903, the body is a separate unit from the driveline and suspension. As a result, stiffness will be much, much, much lower than the cars of today, and ride quality will be wobbly and uncomfortable.
But wait, you ask. Won't the new "drive by wire" stuff help this? In a word, no. The truth here is that the only stressed structural member will be the flat "skateboard" and no electronics can do anything about that. Modern cars use a "unibody" design where the entire passenger cabin, including walls and roof, contribute stiffness. This is the reason that a modern shitbox (like a Kia) drives so much better than an antique shitbox like that Model T. GM's plan will only serve to give us postmodern shitboxes.
Don't get me wrong, I'm not down on tech. I think that electric motors will be the way of the future. They're lighter and more efficient than internal combustion engines (ICEs). They develop their peak power and torque from standstill instead of at redline. They can run at road speed, so there's no need for a pesky transmission.
If GM really wants to set the world on fire, they need to make their assembly lines modular and not the cars. I forsee a world where they can pump out custom spaceframe chassis for fuel-cell powered vehicles using four-wheel direct electric drive. If they were really smart, they'd work on driving the costs of composites down so we get carbon-fiber monocoque street cars with bullet-proof kevlar saftey cells.
But this is GM we're talking about. They brought you the new Impala. Oooh, and don't forget the Aztek. Yay.
man, if i'd only known about this i would have rescheduled my trip!
seriously, ireland is an awesome place for this... the best hiking and beer you'll ever find, plus friendly friendly people.
p.s. the accent is really good out west... they say they talk so fast 'cause there's so much to say! be sure to ask for directions before going anywhere, well worth it.
There is an insightful analysis of the legal decision at penny arcade, written by one "Atticus XI - Lawyer of Doom." Many lucid points raised on the side of those who are good and just.
"Forget all you heard about .NET." This is a good quote. So let's for a moment forget about the superfluous features of C# and the .NET Framework, like machine-independance. What does it get you in the end? Faster application development.
I think that Miguel and the whole GNOME community is tired of being "second-best" in the desktop environment competition with KDE. The simple fact is that (not unlike Win32) plain old C and GTK+ are complex, error-prone development environments that no one will much miss. In fact if you look at GTK+, much of the GNOME team's time has been spent trying to copy object-oriented design features that are intrinsically availiable in other languages.
KDE has a secret weapon in its usage of C++ and QT; the true object-oriented approach is simply better and faster for large projects. If you haven't programmed, you won't realize that QT is basically "Java Swing for C++." The KDE project pushed out their next-generation desktop months ahead of the GNOME boys and they're not looking back now.
I say, hurrah to the GNOME team if they do finally pick a new, better, faster development environment. However, I am worried that instead of relying on proven, existing, free (as in GPL) technology like g++ or QT3 they will waste entirely too much time reimplementing the basics.
As usual. Did I say that? Don't want to sound biased!
|-) <----- geordi.
The idea here is that any sort of war is immoral. Sending mechanical surrogates to kill people without consequences only encourages more death.
a word about the lack of understanding of basic GUI concepts:
when i was in grade school, my grandpa got a macintosh, and it was soooo much cooler than my PS/2 model 25 (trying to get you guys set in the timeline.)
Anyway, the mac came with this audio tape tutorial that explained what these "icons," "windows," and "menus" were, and how to "click" "double-click" and "drag" to interact with them. It even had fun games where you had to pull a mouse through a maze and swat flies and things.
Anyway, I think that current GUIs assume that everyone has basic proficiency with these skillsets when many many people do not. There needs to be a basic "how to mouse" tutorial shipped with every OS that fires up on the first boot (and is availiable easily later).
With this, I could show my mom where the "ON" switch is (it's right on the front, it's sooo easy these days) and let her learn to use the comp for 20 minutes before i show her how to type a letter.
C'mon, that's a toyota supra with a bigass 6-cylinder turbo engine in it, not a little 4-cylinder rice-burning "hon-duh."
and i think it was an impala SS if i'm not mistaken.
anyway, if you watched it, the SS blew a cylinder and that's why it didn't eat the toyota for lunch. in drag racing and processors there's no place for finesse.
the athlon is a brute of a chip, a brute that can be cranked to higher speeds than anyone imagined, and that's why it beats the "high-revving" (rice-burning?) P4s. good thing it doesn't have to run in the twisties like a road racer...
I was just thinking in the shower this morning, wouldn't it be cool to have a SCUMM interpreter? Then we can make high-quality adventure games and all that. Opensource is bad-ass dude. Wish and ye shall receive. (Return in kind of course)
There is a much easier way to use ssh-agent. Rather than starting the server from the first bash shell and then checking if it's running for every other shell, it's possible to simply say "ssh-agent [program]" and then that program and any of its children will know about the private key cache.
/usr/X11R6/bin/kde2". You could use any window manager you like. (attention all sprockets: the "exec" is there so you don't waste a process)
For example, on my system I added another login choice to KDM called "kde2-ssh". I created a corresponding shell script cleverly called "kde2-ssh" that contains only "exec ssh-agent
After the window manager starts you simply run "ssh-add" once and every program started by X will know about ssh-agent. Pretty dope, huh?
Oh yeah, if you run ssh-add from a script (i.e. wherever there is no stdin) it will pop up a nice X dialog box for your password. Extra tasty crispy dope, i'd say. I put a call to ssh-add in my handy KDE "Autostart" folder so now i'm the envy of all my friends. yes, all two of them.
g'night kids!
Sometimes you just have to let those hard-to-reach chips go.
--dante
Oh god yes! The question is, do you remember the episode where he reviewed "Jurassic Park 3?"
Quote from the critic's Jurassic Park 3: "You can't trap a raptor in a closet! They're too smart!
Quote from the real JP3: "They [raptors] were too smart. They were smarter than dolphins. They were smarter than primates..."
Oh god, sometimes i think the world can't get any more obscenely surreal.
Then it fucking bowls me over with it.
G'night!
Serial ATA is designed to be hardware-compatible with current ATA. One can assume that the spec will account for 48-bit addressing. In the meantime, remember that widening the address space on a parallel bus will increase costs; more wires, more costs.
New, huge drives can be built with nary a concern over the serial or parallel-ness of the interface.
This pisses me off, that the SDMI expects consumers to be happy buying so-called "perfect" digital copies of music that in fact have known, intentional defects in sound quality introduced as access control methods.
I'm especially taking issue with "Technology C". From Felten's paper on the attack:
Think about this for a second! They simply removed audio information and then the sound sample was accepted as genuine. This means that the audio information they removed was never there to begin with. Argh.
Oh, and kids... 1350 Hz is not some whacky frequency that only bats can hear. It's somewhere around E above high C, which is a perfectly fine note, when you think about it. I mean, I play trumpet, I love listening to trumpet music. Cutting out 1350 Hz will effect everyone from Maynard Ferguson to Miles Davis (well maybe not Miles Davis. ;-)
Well that's enough of that. Time to get dressed.
the Caldera Linux Technology Preview (and presumably their eventual new version of OpenLinux) use GRUB instead of LILO.
it's dope.
outie.
Your assertion that the gameboy was an inferior design than the gamegear is not entirely correct. Remember, hardware power, graphics and sound and the like are only one portion of the design parameters of a portable unit. Recall that the sega gamegear was TWICE as big as a game boy. My brothers actually had both of the systems. Which came with us on the car trips? Not the game gear with it's carrying case (complete with shoulder strap). Game Boy was a superior product to game gear because the design compromises made at the hardware level enabled big gains in the usability level.
How does this apply to dreamcast/ps|2? We must remember that hardware is only half of the equation. For example, which is more important to the gaming audience, DVD playback or 4-player games? Will US audienes be put off by the lack of quality launch titles (due to sony's extreme hubris when dictation development environment, i might add)?
My prediction: Dreamcast fades because sony is a bunch of bitches. But nintendo kicks everyone's ass next year with the gamecube, which offers a nirvana of power, form factor and ease of development.