A lot of data retention is because of legal requirements.
Well, it's for lots of requirements really. Pretty much wherever information can be useful for more than real-time decision making, you'll see archiving.
Nothing new in this story. Peter Quinn made a much more interesting case when he spoke of Sovereignty in the context of citizen's own rights of access to their historical records, and the onus on governments to preserve that data in a format that belongs to the people (i.e., a non-proprietary format).
The summary misses one of the best bits -- the project will try to get rid of the Global Interpreter Lock that interferes so much with multithreading.
Thanks for that. I was about to say, that the main issue for me is the GIL, not interpreter performance. Improvement of both is good, of course, but the GIL can be a show-stopper much more easily.
if they feel pain? Cattle defiantly do, we still eat them.. As, I'm sure, a wide variety of other food stuffs feels pain as well..
Maybe not, but it would be nice if we "intelligent" human beings could at least find the guts to admit that our prey are suffering. I mean, seriously... how cheap can we get, hiding behind an excuse like, "Oh, it's OK, they don't even feel it."
It wasn't a great example. Amiga's didn't really suffer from DLL hell though, because the cultural expectation for both app developers and library writers, as well as the library loader calls in the OS, all encouraged fully backwards compatible library use. Also, amigas had a GREAT volume label system, where instead of asking for a particular directory or disk, you could ask for a symbolic place, or even a symbolic name that represented many places. So you could easily rearrange search paths, move apps to another drive, etc.
There were some issues, but mostly, admining AmigaOS was GREAT. Unfortunately hardware wasn't so abstract, so upgrading the processor or graphics was more difficult. Not surprisingly, given the era, of course.
PS: None of the Amiga games/demos used the OS for anything. They either ignored it or dumped it to gain some extra RAM.
Wrong, some did. But the fact that AmigaOS was revered despite the Amiga not being a business machine, and despite many games not using the OS, should only serve to highlight how good it was for the (relatively) few who really experienced it.
This sounds inherently stupid. How many people send an e-mail, just to think: "oh no!" 2 - 4 seconds later.
Probably more than you imagine. But, yeah, I agree, nonetheless, that it's a stupid idea. Forgotten attachment detection? Lifesaver. This? Silly, and unlikely to help anyone. I suspect anyone who COULD use it will either: a) not know about such things anyway; or b) want to take back an email within five seconds so infrequently that it takes more than five seconds to remember it's available.
Which makes me idly wonder what the real purpose could be, if not to really help people. Reduce load on servers somehow? 5-second filtering, kind of like the seconds of delay on so-called "live tv" used to prevent cursing etc.? Hmm.
With 384GB RAM, get a good UPS and generator and run your entire system in RAM.
I pretty much do exactly that now, with 6GB, including the odd virtual machine. Vista/XP x64 wouldn't even drive my hardware with that config, much less run well, but Ubuntu and Debian have performed beautifully, using most of the RAM as disk cache. Sure, I can't store the entire drive in there, and 3D animation or NLE video would soon put it to shame, but it easily handles my everyday working set, which includes stuff like Eclipse.
Hmm. My main complaint was the time yum takes to install even a small package. Last time I tried yum, it was HORRIBLY slow compared to apt-get. However, I just read that it's been improved since fedora 3 with caching. Pretty sure I tried it AFTER fedora three (probably way after), but I'm currently downloading the latest FC to try it again.
Aside from that, there is a much better packaging CULTURE in debian -- way more packages, and albeit that I can't provide stats on this, I seemed to notice many more package bugs when using yum/rpm than with debian packages. A big issue was simply the lack of easy software availability on RPM systems... once I get a debian system up and running to the point where it has a network connection and apt, I'm pretty much sorted, no matter what else I want to install.
That said, I'll give it another shot and see if things have improved. I'm not optimistic though, given my many past bad experiences with rpm distros.
p.s.: Seems we both got into linux at a similar time:) Slackware was one of my first stops too. I tried Yggdrasil first, but if I remember right, I didn't stick with that for too long. I don't remember much about it, except that I think that's where I discovered MGR. Slackware at least made an impression, before I discovered Debian:)
Ever think that perhaps the people are doing something to cause the autoimmune disorder?
That's irrelevant. Whatever factors lead to the autoimmune disorder, the fact is that the host's immune system attacks the host. That's a bug, even if there is an outside agent maliciously causing the bug to manifest.
Distrowatch stats aren't relevant. Nobody in their right mind chooses between, say, Fedora and Ubuntu on the basis of their package management system - because it makes no difference to the usability of the operating system.
You've said this twice now. What are you basing it on? Your own lack of knowledge about how good other package management systems can be? I've tried tons of distros over the years, and I always end up going back to debian-based distros due to the far superior package management system.
My experience, and the experience of everyone I've talked to who's really used and compared the two systems, tells me otherwise. The top distro stats on distrowatch also tell me which way people are leaning. Time will tell; no point arguing about it now if you're not convinced yet, but I think most people have seen the writing on the wall for a long time now.
I'll add the next step in the logic though: obviously if Canonical do the desktop better, they also get the server market, or at least, debian-like distros (quite probably Debian itself) will. Good riddance to the RPM format, I say. Redhat should have swallowed their pride and adopted the superior format years ago, and we'd all have been a lot further forward now.
Every time they see "!=" they interpret is as "bang equals". That sounds like definitely equals, doesn't it? Like, dude, those are so equal it's not even funny, equal.
You obviously haven't worked there for a while. Lately, they've recoded many of these bang statements with symbolic names and less confusing operators, to more accurately convey their meaning. All such checks now read:
It starts, yes, but in the most inefficient way possible.
IBM's approach is the much better one, imho. Emulating wetware won't get us very far, except to clone a wetware brain. Since we haven't yet worked out the proper, safe, reliable, healthy way to raise our children, creating a human brain clone with potentially much more intelligence and almost certainly all the same flaws is not a good thing.
If IBM are working on a higher-level, trying to build a system where we can see the associations in terms of "A frequently_sees B" "B helps A" and "A respects B" therefore "A likes B" is much more useful. With that kind of high-level emulation, we can actually see how things are working, tweak them, customise them, extract datasets, etc. We could programmatically have one of these brains loading a scenario, fast-forwarding to evaluate all known possible events and outcomes, and predicting the future, since it would essentially be doing that on a smaller scale anyway, to make decisions. We could do this with the neuron-based wetware emulation too, but only really if we asked it to, and it wanted to comply.
When we can reliably read and control a simulation of a human wetware, we'll be a few days from reading and controlling a real human wetware brain, so I'd much rather see the alternate scenario play out.
Yes, I understood what he was saying, I just don't agree that it follows. Saying that people CAN eat meat and vegetables, therefore they MUST eat both is the most basic fallacy out there. It's a redundant system, not a mutually requisitive system. Regardless of that system, our brains are ALSO part of our human nature, so any way we decide to live (using our human brains) is certainly within the set of human nature. Next he'll be claiming that it's not "natural" for humans to cook their meat.
Now, if he'd made his argument based on some interesting philosophy that can't be easily disproven, such as that the average man is simply happier when he has a good thick steak between his teeth, then the post might have had something to say about "human nature".
Slashdot Mirror
And that's the point. You're being honest about it, others aren't, and it's just infantile.
There, fixed that for you.
Well, it's for lots of requirements really. Pretty much wherever information can be useful for more than real-time decision making, you'll see archiving.
Nothing new in this story. Peter Quinn made a much more interesting case when he spoke of Sovereignty in the context of citizen's own rights of access to their historical records, and the onus on governments to preserve that data in a format that belongs to the people (i.e., a non-proprietary format).
Exactly. More ISPs need to do this. I would SO sign up with these guys, if I lived in Oz.
Thanks for that. I was about to say, that the main issue for me is the GIL, not interpreter performance. Improvement of both is good, of course, but the GIL can be a show-stopper much more easily.
Maybe not, but it would be nice if we "intelligent" human beings could at least find the guts to admit that our prey are suffering. I mean, seriously... how cheap can we get, hiding behind an excuse like, "Oh, it's OK, they don't even feel it."
It wasn't a great example. Amiga's didn't really suffer from DLL hell though, because the cultural expectation for both app developers and library writers, as well as the library loader calls in the OS, all encouraged fully backwards compatible library use. Also, amigas had a GREAT volume label system, where instead of asking for a particular directory or disk, you could ask for a symbolic place, or even a symbolic name that represented many places. So you could easily rearrange search paths, move apps to another drive, etc.
There were some issues, but mostly, admining AmigaOS was GREAT. Unfortunately hardware wasn't so abstract, so upgrading the processor or graphics was more difficult. Not surprisingly, given the era, of course.
Wrong, some did. But the fact that AmigaOS was revered despite the Amiga not being a business machine, and despite many games not using the OS, should only serve to highlight how good it was for the (relatively) few who really experienced it.
MORE THAN ONE powercord? Lordie lordie. How will Rand ever stop the Wheel of Time now?
Probably more than you imagine. But, yeah, I agree, nonetheless, that it's a stupid idea. Forgotten attachment detection? Lifesaver. This? Silly, and unlikely to help anyone. I suspect anyone who COULD use it will either: a) not know about such things anyway; or b) want to take back an email within five seconds so infrequently that it takes more than five seconds to remember it's available.
Which makes me idly wonder what the real purpose could be, if not to really help people. Reduce load on servers somehow? 5-second filtering, kind of like the seconds of delay on so-called "live tv" used to prevent cursing etc.? Hmm.
I think you meant to quote Carrey's other performance:
Charlie: "Why does my ass hurt?"
I pretty much do exactly that now, with 6GB, including the odd virtual machine. Vista/XP x64 wouldn't even drive my hardware with that config, much less run well, but Ubuntu and Debian have performed beautifully, using most of the RAM as disk cache. Sure, I can't store the entire drive in there, and 3D animation or NLE video would soon put it to shame, but it easily handles my everyday working set, which includes stuff like Eclipse.
Hmm. My main complaint was the time yum takes to install even a small package. Last time I tried yum, it was HORRIBLY slow compared to apt-get. However, I just read that it's been improved since fedora 3 with caching. Pretty sure I tried it AFTER fedora three (probably way after), but I'm currently downloading the latest FC to try it again.
Aside from that, there is a much better packaging CULTURE in debian -- way more packages, and albeit that I can't provide stats on this, I seemed to notice many more package bugs when using yum/rpm than with debian packages. A big issue was simply the lack of easy software availability on RPM systems... once I get a debian system up and running to the point where it has a network connection and apt, I'm pretty much sorted, no matter what else I want to install.
That said, I'll give it another shot and see if things have improved. I'm not optimistic though, given my many past bad experiences with rpm distros.
p.s.: Seems we both got into linux at a similar time :) Slackware was one of my first stops too. I tried Yggdrasil first, but if I remember right, I didn't stick with that for too long. I don't remember much about it, except that I think that's where I discovered MGR. Slackware at least made an impression, before I discovered Debian :)
Is THAT what they're pushing as minimum spec for Windows now?
That's irrelevant. Whatever factors lead to the autoimmune disorder, the fact is that the host's immune system attacks the host. That's a bug, even if there is an outside agent maliciously causing the bug to manifest.
You've said this twice now. What are you basing it on? Your own lack of knowledge about how good other package management systems can be? I've tried tons of distros over the years, and I always end up going back to debian-based distros due to the far superior package management system.
My experience, and the experience of everyone I've talked to who's really used and compared the two systems, tells me otherwise. The top distro stats on distrowatch also tell me which way people are leaning. Time will tell; no point arguing about it now if you're not convinced yet, but I think most people have seen the writing on the wall for a long time now.
Anyone using The Pirate Bay while they're being tried in court is asking for trouble.
More like they've been staring into space, and just woke up.
Thanks. Saved me having to say it.
I'll add the next step in the logic though: obviously if Canonical do the desktop better, they also get the server market, or at least, debian-like distros (quite probably Debian itself) will. Good riddance to the RPM format, I say. Redhat should have swallowed their pride and adopted the superior format years ago, and we'd all have been a lot further forward now.
You obviously haven't worked there for a while. Lately, they've recoded many of these bang statements with symbolic names and less confusing operators, to more accurately convey their meaning. All such checks now read:
if ( state == not_even_funny ) {
continue;
}
Hmm. Seems IBM aren't doing it on a higher-level, just in software rather than hardware. There are more interesting projects out there.
It starts, yes, but in the most inefficient way possible.
IBM's approach is the much better one, imho. Emulating wetware won't get us very far, except to clone a wetware brain. Since we haven't yet worked out the proper, safe, reliable, healthy way to raise our children, creating a human brain clone with potentially much more intelligence and almost certainly all the same flaws is not a good thing.
If IBM are working on a higher-level, trying to build a system where we can see the associations in terms of "A frequently_sees B" "B helps A" and "A respects B" therefore "A likes B" is much more useful. With that kind of high-level emulation, we can actually see how things are working, tweak them, customise them, extract datasets, etc. We could programmatically have one of these brains loading a scenario, fast-forwarding to evaluate all known possible events and outcomes, and predicting the future, since it would essentially be doing that on a smaller scale anyway, to make decisions. We could do this with the neuron-based wetware emulation too, but only really if we asked it to, and it wanted to comply.
When we can reliably read and control a simulation of a human wetware, we'll be a few days from reading and controlling a real human wetware brain, so I'd much rather see the alternate scenario play out.
Yes, I understood what he was saying, I just don't agree that it follows. Saying that people CAN eat meat and vegetables, therefore they MUST eat both is the most basic fallacy out there. It's a redundant system, not a mutually requisitive system. Regardless of that system, our brains are ALSO part of our human nature, so any way we decide to live (using our human brains) is certainly within the set of human nature. Next he'll be claiming that it's not "natural" for humans to cook their meat.
Now, if he'd made his argument based on some interesting philosophy that can't be easily disproven, such as that the average man is simply happier when he has a good thick steak between his teeth, then the post might have had something to say about "human nature".
Rubbish. I don't categorize things as supernatural. Sorry.