Oh, about the same part that says that a mechanic can drop $1200 into a wrench set, or that a glassblower can invest $1200 into a borner and venting setup.
Bu here is the issue: if an int = 64 bits, then according to the rules of C, a long must also be 64 bits. If that happens, then there is NO WAY TO DEFINE A 32 BIT VALUE.
You mean like a short? Or a wchar? or a char? Or maybe, er, by making a new type? or using the POSIX types? or a compiler specific extension? Hey, how about bitfields? Or reads over a thinner bus? Um, what about DMAs with read width? Or, I know, how about truncating opcodes? Hey, I know, there's always operator new, or overloading global new, or compositing still smaller types, or unions. Oh, wait, there's also going to be library support from any sane platform. Also, compilers for platforms which introduce base types that aren't in the C standard generally offer access to those base types; witness the varying reactions to Intel's 80-bit float.
See, 64-bit-base-ints are nothing new. If you'd crawl out of your MSVS cave, you'd realize that these things were solved in the 80s.
Also, that long doesn't have to be 64 bits - it could, and probably would be - larger.
And that is important for some types of programming (drivers, embedded, etc.)
Boy, I do embedded for a living. Maybe you should realize that the standard list of types is only the minimum list of types available, not the total list.
It would require some kind of compiler specific hack.
Hardware support base types are as much of a hack as support for a segmented memory model.
The problem here is like that of the Win2K issue, we are now crossing into the realm where the designers of the language (and the people that wrote programs in that language) did not think we would go.
Bullshit. The language was carefully designed for base type ignorance. They worked in an era where bytes were commonly 7,8,9 bits. Moreover, there were 64 bit machines back then just like there are now. Please start speaking out of the left side of your ass; the right side is getting overused.
Maybe you forget that the Playstation 2 is a 128-bit machine and has been running C and C++ compilers without issues for years. Maybe you forget that the crays for which valarray was developed are generally 256bit machines, and have been running C for decades. Maybe you forgot Seymour Cray's comparison of the ease of adapting the C language to preposterous sizes to the degree by which Fortran could optimize.
Maybe what you don't understand is that the MFC and ATL were not designed for >32bits, and that that's not C or C++'s fault. The STL works fine in 64bit, 256bit, 1024bit. There're no problems. How's CString looking under CE to you? Want a thin character?
The whole thing breaks down after 32 bits because an int can't be larger than a long. The model only has worked so far because there have been basically two sizes of int in wide use as we moved from 8 to 16 to 32 bits (8-bit compilers use int=16 bits).
Weren't you the one talking about embedded just a minute ago? Do you not know what fixed point is? Have you never heard of a wchar, or posix types?
Here's an example, not the only possible one, of a valid progression of the powers of two using standard types.
char=8, wchar=16, short=32, int=64, long=128, long long=256 (yes, there's a long long.)
That gives machine support base types for ^4 the size you're whining about without new base types or using any of the half dozen standards for handling this setup already.
Remember comp? double? extended?
Otherwise the value of long has be redefined to 64 bits instead of the 32 bits it always was
Long hasn't always been 32 bits. For example, on the Honeywell 6000, a contemporary machine when C was created and one of the original reasons for C's portability, to build the Unix kernel on wildly varying machines, it was 36 bits. On the Casio Wizard, it was 28 bits. There are a number of non-power-of-two base size systems in use up and until the mid 1980s, when silico
Yup. So grateful that they've been killing American solders at a rate of roughly 1 per day since GWB's "Mission Accomplished" photo-op. Interesting way these Iraqis show their gratitude...
Ah yes, because in cities with millions of people, having one of tens of thousands of occupying soldiers attacked two or three times a day clearly shows that the whole populace is up in arms. I mean, if they all hated it, they probably would have attacked more than... oh, wait.
See, this is the problem. It's a war torn nation. Formerly rich families are destitute, but still proud. There's starvation. Infrastructure is ruined. Therefore, tempers are high. This isn't even New York barfight level anger, if only one person is dying a day. Soccer mobs actually do more damage.
In the meantime, we've got well fed well paid well clothed well apointed white people, a few of whom are genuinely racist, a number of whom are going to be drunk or occasionally high, saying things they shouldn't, doing things they shouldn't. Many things which are normal to us are morally, religiously and legally abominable to them - such as being drunk.
Furthermore, there's the small branch of Iraqis which profited under Saddam. They're almost certainly mightily pissed.
Oh, and right, there's all the political mumbo jumbo going on in the area; a number of these are actually funded by (insert random dictator x) whose vested interest in making the foreign powers seem evil to maintain domestic control has a particularly fruitful avenue while tampering with one of the first major mations to revert to rule by the people in the area in decades.
I think it's a show of incredible control that in a ruined once prosperous city of millions which has been crippled first by dictatorship and next by sanction and resultant economic collapse a set of ill-behaved foreigners which have been propogandized to be about to do this very thing haven't been murdered in droves.
There hasn't been a single street mob. No lynchings. No organized revolt. No underground. We can't say that about any three adjacent states in our country's history. Doesn't it strike you as odd that these people seem about as riled up as a Saint Patrick's Day parade? Yeah, maybe Rumsfeld took everyone out of baghdad and made those human celebrations - WHICH YOU COULD SEE MOVING ON TERRASERVER - with a giant 1920s style dancing cast. Good thing they didn't fake it in Utah; FOX would have found it and done a special.
Jackass.
But. Hating Saddam isn't the same as loving the US. Most Iraqis are doubtless overjoyed that Saddam's government has been toppled, that doesn't mean they like a US occupation of their country either.
I'm sure a great many Germans were none too happy about the French occupation of Berlin, either. Nevertheless, when you escape Mumm-Ra only to fall into the hands of Ratar-O, you know you've traded up in the world.
Look, I'm not standing up for our coup government. But W isn't nearly as capably evil as Saddam is, and Cheniwell is basically a Hanna Barbera bumbling ne'er-do-well. Their kind of antics are things like charging double for gasoline and misplacing girders at the cost of the US taxpayer, not cutting off limbs for wayward glances. If I were king, cheney would indeed be against the wall, but there are a helluvalot of people that would go first.
Note to secret service: the above is literate exaggeration. Look up the dictionary entry for sarcasm, and proceed to investigate every facet of my life. Hint: it's a music reference.
On a broader note, I object to the "we're doing it for the poor downtroden people" chest-thumping coming from the Bush government because it is a horrible lie.
A villiage sits at the base of a valley. One year, the winter is bad, and damages the soil holding back a river; the surveyors suggest it will break through in a few years, and that though it can be shored up, a dam is needed.
Hey, Saddam was a bad guy, no doubt about it. But we should have never stopped looking for Osama. By pulling our best troops off that hunt, we let him get away. Brilliant move, guys.
Yeah, and we got Saddamn Fucking Hussein.
This is like being angry that we let a burglar go to catch a rapist. Osama is not anywhere nearly the problem Saddam is. Open a history book that goes back more than three years.
The real problem is how difficult it is to define whether a product has become ubiquitous. For a lesson in how difficult that is, refer to CompuServe's superficially compelling arguments about the dominance of JPEG that allowed them to fool a judge into thinking the resurfacing of the LZ patents was okay. Sometimes a patent really can't be judged in time, and sometimes a company gets into commercialization beforehand knowing fully well that it'll have to stop; see the issue with the chemical that made wacky wall walkers, and Klutz Press.
A 64-bit platform is a platform which has been attacked by marketroids. The C Standard says nothing about the sizes of any of the base types in comparison to any of the various sizes a 64-bit platform might choose to support, rather referring only to comparisons: char may not be longer than int, short may not be longer than int, long may not be shorter than int, et cetera.
Granted, many C compilers choose to ignore the advice of the standard, which is to implement int as the fastest integer type for native math, and implement it as a 32-bit because buttheads like you can't get through your thick skulls not to use raw types. But good compilers, and also good programmers, don't suffer such silly strictures.
Yeah. That's instant caulking gel. If you've ever worked on your bathroom, you know you can store far more propellant in there if it's caulking gel than any other substance on earth.
Three of the original caulking tubes from the prototype dozen are still giving off effluent. Why do you think New Jersey looks like that?
So, in conclusion, the Cylons, sick twisted bastards that they are, are willing to leave giant streams of polycarbon chains littering the galaxy in their quest to wipe us out.
Personally, I'd like to see a series of TV movies rather than a weekly series. I think this would work better as an occasional treat, hitting the highlights of the journey, rather than trying to tell 22 stories a year.
Given the sarcastic tone in which it's done, Matt Groening seems to be the exception to this rule, especially given that there are only three characters which use slang, each at varying levels of archaicness.
It was implied, when during the brief conference of various models of Cylon, one remarked that humans would always seek revenge. This is to me something of an irony, considering.
Moving to a default patching system is both a bad idea and impractical.
Not only does it raise the risk for a single flaw to cause catastrophe, but it raises the value of a single attack, makes a cross-platform attack feasable, and lowers the cost of attacking any select group of systems. Homogeneity is security disaster.
It's impractical because many systems work in fundamentally different fashions, and would have different needs for a patching system. I can't guess whether you mean all Linuxes, all Unices, or all OSes, because you're defensively vague with "on a larger scale", and if you mean all Linuxes this might maybe be feasable (I don't know the gamut of linux weirdness; I have no idea what Gentoo really does under the hood, for example,) but even for all Unices, things like QNX have demands that make this absolutely unacceptable.
Besides, diversity encourages competition and innovation. If we had One Huge System (tm), it would be excessively difficult to test new ideas. We do not at the moment have a patch distribution system which will just automagically handle a whole LAN, AFAIK; such a thing might never get off the ground if we all lived in the same yellow submarine. (If we do have such a thing, just pick some patch innovation that we don't have yet and substitute; the example isn't the important thing.)
I firmly believe in The Unix Way: small, interlockable pieces representing concrete ideas, which one can string together to achieve goals. You and I might prefer different patching mechanisms; The Unix Way provides for us to choose as we see fit. You might prefer to trust an authority and automatically get patched immediately; I might paranoiacally want the patch downloaded but not instituted until I verified, so that I had time to call the company IS guy and check. Or whatever.
I also believe that The Unix Way is why a platform with such ragged support and meager software library still completely owns the business world despite a decade of effort from the world's largest software-centered marketing company. If you may build your server from pieces, you may control characteristics of it which can be vital for new serving paradigms. This Is Important. (r) Do Not Break It For Convenience, Damnit. (c)(sm)
not an add on that you know to (1) know about
Uh, I don't even have a Linux box, and I found it with a quick google search. Perhaps you should visit to theseinformative links.
You know, an enterprising attacker could just pull the trust network down. Someone with sufficient skill could very easily just work on Debian for five or six months, get trusted, and embed a subtle bug into a remote point.
I mean, we can't find the unintentional ones. What makes you think we could find one chosen for its obscurity?
Fact: Spent fuelrods from reactors are a major enviromental problem.
Quite true. In fact, there is no power generation method without some impact. Construction of windmills' cement basings releases tremendous amounts of carbon dioxide, and destroys a fair amount of stone. Solar panels change the amount of heat hitting the ground, and take up a huge amount of area.
Our current common generation methods, coal and oil, release tremendous amounts of radioactive waste into the air both in mining and burning, as well as hundreds of other known carcinogens, carbon mon- and dioxide, soot, and general evil.
Spent fuel rods from reactors are a major problem, and not nearly as bad as the current major problems we ignore, which are burning holes in the upper layers of our atmosphere, and whose after effects are so thick that in some cities like LA and Mexico City are literally visible.
Moving from a 95% solution to a 98% solution is a good thing. Dig a hole in some granite mountain and dump them down there, or in some salt mine, or something. 'S a *lot* better than smearing it all over the air, and at least in 300 years when we get a better idea, we can go in, round it up, and change it.
NES: Sega Master System had better graphics by far, but NES games were better.
This is a point of difficulty during argument. What US gamers call the Sega Master Ssytem is in fact the Mark 3 base. Whereas it is true that the Mark 3 is superior to the NES, it didn't exist until 1986. Most pages will say that the Master System was released before the NES in Japan; that's the SG-1000, and it is not superior to the NES. The SMS Americans know and love postdates the NES by two years.
Game Boy: Lynx/Game Gear had much better graphics, but GB games were better.
The GameBoy was released in early 1989. The GameGear didn't show up until late 1991 - a two and a half year difference. The Lynx apparently only postdates the GameBoy by a few months, which is a surrise to me; you've got me there. I was under the misimpression that it too was later on.
Nintendo 64: Could've had amazing graphics, but Nintendo didn't help the developers enough.
Whereas I certainly agree (and point out that a lot of the problem was storage space for textures), the germane bit of the discussion was about the hardware.
I love Nintendo just as much as anyone else, but take those rose-colored glasses off.
Well, you've got me on the Lynx. The rest of this could use some reminders about the way history really went. I'll take off my rose colored glasses when you put on your research hat.
Actually, this isn't accurate. GBA puts everything into a linear address space. It has two primary blocks of user ram: IWRAM, 32k, starting at 0x03000000, and EWRAM, 256k, starting at 0x0200000. There is room to expand *both* to 16meg. The BIOS and System ROMS (0m), IO registers (4m), Palettes (5m), video ram(6m) and OAM (7m) each have similar available ranges. 1m is completely unused.
Better still, the top 4 bits of the address bus are completely unused (10m-FFm).
There's a *tremendous* amount of space for new RAM, new storage, new devices, et cetera. If N upgrades, there's more than 16m of room to work with.:D
Oh, that's like calling GM a niche player. Nintendo has the highest selling game system in the world, and the second highest selling television console not only in the world but in each major sector.
Also, "foo and foo-like are standard" is a silly thing to say. If foo is standard, foo-likes don't exist. Besides, the GC *does* use a dvd-like standard; it's very close to a mini-dvd.
As far as sony having realized the advantages of hard drives, erm, no, they haven't. Their baseline model doesn't come with a hard drive, and it is difficult to get the hard drive expansion. The high-end model, which is expected to cost more than triple what the baseline model does, is a PVR; the only reason there's a hard drive in there is that the PVR needs it.
Top-end video and audio capability? Can you name a Nintendo system that has ever been released that hasn't been the best graphics or sound of its day? Hint: there's only one, and that's because N dropped the ball on the GameCube. The reason you probably think of the PlayStation as having higher quality graphics hardware than the N64, which it doesn't, is that by comparison it had preposterous storage space, allowing it to do things like play prerendered movies.
Should Nintendo wish to continue, they should continue what they've been doing for over two decades. They've weathered corporate sabotage by Sony quite well, and maintain a lead over a company which has intentionally flushed over a billion dollars down the toilet trying to get well known. Sony has a huge advantage in that it is already a manufacturing giant, giving them margin leads that Nintendo can't compete with.
I suggest that you stop karma whoring and research a bit. They maintain a substantial position in the marketplace, and are gaining share while the other two players are losing it. There isn't a justifiable statemet anywhere in your comment. How you got 5, insightful is beyond me.
That's why the cube used them from the beginning - building up to the same hardware being used in a portable.
Though this is certainly a nice after effect. actually, this is not why the GC uses small discs. At the time, there was quite a bit of hemming and hawwing about how N wasn't going to move to discs for the portable, but rather wait for something SD/MemoryStick-ish.
The reason Nintendo abstained from CDs was loading time. The management of Nintendo at the time believed that the increase in cost and decrease in game volume would be offset by the ten to twenty seconds that they at the time believed that games would require as loading time fairly frequently; apparently, they believed that a situation like Resident Evil's would be the norm, and I find it disappointingly common in early (and occasionally even modern) PlayStation games.
As things progressed and as Nintendo's error became apparent, they tried to prepare external CD drve after external CD drive, only to be met with fundamental price problems that came from supporting multiple storage formats. Nintendo saw the CD as an albatross, though, and it wasn't until Sega successfully pushed the GD that Nintendo began to believe that a proprietary format was realistic.
Once they did, however, the load time issue because their primary focus. In order to reduce both seek time and to increase disc resilience to high speed, they came to the decision that a minidisc format, which has significantly less angular momentum, would be the best way to go. Besides, it offered a very strong protection against piracy, as nobody could make their discs without specialized hardware.
I do hope that they carry the disc format to the new portable machine; that would allow enterprising developers to write cross-platform software, something that currently *none* of the portable manufacturers offer (and really, a game which was intended for portability but which offered editors and maintenance tools on the less cramed home system seems ideal to me.)
Whereas I hope this happens, I really don't think that was the original reasoning.
Slashdot Mirror
Ahem.
Maximillian > John Travolta in stilts.
Oh, about the same part that says that a mechanic can drop $1200 into a wrench set, or that a glassblower can invest $1200 into a borner and venting setup.
I like how I got flamebait moderated. (sigh)
Us digital artists would already like to have Tablet PCs.
So get a job and buy one. It's not like they're DARPA controlled.
Is they include the word sidetalkin', i'm jumping ship.
Bu here is the issue: if an int = 64 bits, then according to the rules of C, a long must also be 64 bits. If that happens, then there is NO WAY TO DEFINE A 32 BIT VALUE.
You mean like a short? Or a wchar? or a char? Or maybe, er, by making a new type? or using the POSIX types? or a compiler specific extension? Hey, how about bitfields? Or reads over a thinner bus? Um, what about DMAs with read width? Or, I know, how about truncating opcodes? Hey, I know, there's always operator new, or overloading global new, or compositing still smaller types, or unions. Oh, wait, there's also going to be library support from any sane platform. Also, compilers for platforms which introduce base types that aren't in the C standard generally offer access to those base types; witness the varying reactions to Intel's 80-bit float.
See, 64-bit-base-ints are nothing new. If you'd crawl out of your MSVS cave, you'd realize that these things were solved in the 80s.
Also, that long doesn't have to be 64 bits - it could, and probably would be - larger.
And that is important for some types of programming (drivers, embedded, etc.)
Boy, I do embedded for a living. Maybe you should realize that the standard list of types is only the minimum list of types available, not the total list.
It would require some kind of compiler specific hack.
Hardware support base types are as much of a hack as support for a segmented memory model.
The problem here is like that of the Win2K issue, we are now crossing into the realm where the designers of the language (and the people that wrote programs in that language) did not think we would go.
Bullshit. The language was carefully designed for base type ignorance. They worked in an era where bytes were commonly 7,8,9 bits. Moreover, there were 64 bit machines back then just like there are now. Please start speaking out of the left side of your ass; the right side is getting overused.
Maybe you forget that the Playstation 2 is a 128-bit machine and has been running C and C++ compilers without issues for years. Maybe you forget that the crays for which valarray was developed are generally 256bit machines, and have been running C for decades. Maybe you forgot Seymour Cray's comparison of the ease of adapting the C language to preposterous sizes to the degree by which Fortran could optimize.
Maybe what you don't understand is that the MFC and ATL were not designed for >32bits, and that that's not C or C++'s fault. The STL works fine in 64bit, 256bit, 1024bit. There're no problems. How's CString looking under CE to you? Want a thin character?
The whole thing breaks down after 32 bits because an int can't be larger than a long. The model only has worked so far because there have been basically two sizes of int in wide use as we moved from 8 to 16 to 32 bits (8-bit compilers use int=16 bits).
Weren't you the one talking about embedded just a minute ago? Do you not know what fixed point is? Have you never heard of a wchar, or posix types?
Here's an example, not the only possible one, of a valid progression of the powers of two using standard types.
char=8, wchar=16, short=32, int=64, long=128, long long=256 (yes, there's a long long.)
That gives machine support base types for ^4 the size you're whining about without new base types or using any of the half dozen standards for handling this setup already.
Remember comp? double? extended?
Otherwise the value of long has be redefined to 64 bits instead of the 32 bits it always was
Long hasn't always been 32 bits. For example, on the Honeywell 6000, a contemporary machine when C was created and one of the original reasons for C's portability, to build the Unix kernel on wildly varying machines, it was 36 bits. On the Casio Wizard, it was 28 bits. There are a number of non-power-of-two base size systems in use up and until the mid 1980s, when silico
Yup. So grateful that they've been killing American solders at a rate of roughly 1 per day since GWB's "Mission Accomplished" photo-op. Interesting way these Iraqis show their gratitude...
... oh, wait.
Ah yes, because in cities with millions of people, having one of tens of thousands of occupying soldiers attacked two or three times a day clearly shows that the whole populace is up in arms. I mean, if they all hated it, they probably would have attacked more than
See, this is the problem. It's a war torn nation. Formerly rich families are destitute, but still proud. There's starvation. Infrastructure is ruined. Therefore, tempers are high. This isn't even New York barfight level anger, if only one person is dying a day. Soccer mobs actually do more damage.
In the meantime, we've got well fed well paid well clothed well apointed white people, a few of whom are genuinely racist, a number of whom are going to be drunk or occasionally high, saying things they shouldn't, doing things they shouldn't. Many things which are normal to us are morally, religiously and legally abominable to them - such as being drunk.
Furthermore, there's the small branch of Iraqis which profited under Saddam. They're almost certainly mightily pissed.
Oh, and right, there's all the political mumbo jumbo going on in the area; a number of these are actually funded by (insert random dictator x) whose vested interest in making the foreign powers seem evil to maintain domestic control has a particularly fruitful avenue while tampering with one of the first major mations to revert to rule by the people in the area in decades.
I think it's a show of incredible control that in a ruined once prosperous city of millions which has been crippled first by dictatorship and next by sanction and resultant economic collapse a set of ill-behaved foreigners which have been propogandized to be about to do this very thing haven't been murdered in droves.
There hasn't been a single street mob. No lynchings. No organized revolt. No underground. We can't say that about any three adjacent states in our country's history. Doesn't it strike you as odd that these people seem about as riled up as a Saint Patrick's Day parade? Yeah, maybe Rumsfeld took everyone out of baghdad and made those human celebrations - WHICH YOU COULD SEE MOVING ON TERRASERVER - with a giant 1920s style dancing cast. Good thing they didn't fake it in Utah; FOX would have found it and done a special.
Jackass.
But. Hating Saddam isn't the same as loving the US. Most Iraqis are doubtless overjoyed that Saddam's government has been toppled, that doesn't mean they like a US occupation of their country either.
I'm sure a great many Germans were none too happy about the French occupation of Berlin, either. Nevertheless, when you escape Mumm-Ra only to fall into the hands of Ratar-O, you know you've traded up in the world.
Look, I'm not standing up for our coup government. But W isn't nearly as capably evil as Saddam is, and Cheniwell is basically a Hanna Barbera bumbling ne'er-do-well. Their kind of antics are things like charging double for gasoline and misplacing girders at the cost of the US taxpayer, not cutting off limbs for wayward glances. If I were king, cheney would indeed be against the wall, but there are a helluvalot of people that would go first.
Note to secret service: the above is literate exaggeration. Look up the dictionary entry for sarcasm, and proceed to investigate every facet of my life. Hint: it's a music reference.
On a broader note, I object to the "we're doing it for the poor downtroden people" chest-thumping coming from the Bush government because it is a horrible lie.
A villiage sits at the base of a valley. One year, the winter is bad, and damages the soil holding back a river; the surveyors suggest it will break through in a few years, and that though it can be shored up, a dam is needed.
The pr
Hey, Saddam was a bad guy, no doubt about it. But we should have never stopped looking for Osama. By pulling our best troops off that hunt, we let him get away. Brilliant move, guys.
Yeah, and we got Saddamn Fucking Hussein.
This is like being angry that we let a burglar go to catch a rapist. Osama is not anywhere nearly the problem Saddam is. Open a history book that goes back more than three years.
It's called "Submarining a patent." Read Title III.
The real problem is how difficult it is to define whether a product has become ubiquitous. For a lesson in how difficult that is, refer to CompuServe's superficially compelling arguments about the dominance of JPEG that allowed them to fool a judge into thinking the resurfacing of the LZ patents was okay. Sometimes a patent really can't be judged in time, and sometimes a company gets into commercialization beforehand knowing fully well that it'll have to stop; see the issue with the chemical that made wacky wall walkers, and Klutz Press.
Insightfully wrong.
A 64-bit platform is a platform which has been attacked by marketroids. The C Standard says nothing about the sizes of any of the base types in comparison to any of the various sizes a 64-bit platform might choose to support, rather referring only to comparisons: char may not be longer than int, short may not be longer than int, long may not be shorter than int, et cetera.
Granted, many C compilers choose to ignore the advice of the standard, which is to implement int as the fastest integer type for native math, and implement it as a 32-bit because buttheads like you can't get through your thick skulls not to use raw types. But good compilers, and also good programmers, don't suffer such silly strictures.
vu8 * clueBat = "rtfm";
Yeah, well, uh, maybe, um, they're ... foam rubber powered.
Yeah. That's instant caulking gel. If you've ever worked on your bathroom, you know you can store far more propellant in there if it's caulking gel than any other substance on earth.
Three of the original caulking tubes from the prototype dozen are still giving off effluent. Why do you think New Jersey looks like that?
So, in conclusion, the Cylons, sick twisted bastards that they are, are willing to leave giant streams of polycarbon chains littering the galaxy in their quest to wipe us out.
Bastards have got to be stopped.
Personally, I'd like to see a series of TV movies rather than a weekly series. I think this would work better as an occasional treat, hitting the highlights of the journey, rather than trying to tell 22 stories a year.
Someone doesn't remember Hercules, does he?
Fluh.
Given the sarcastic tone in which it's done, Matt Groening seems to be the exception to this rule, especially given that there are only three characters which use slang, each at varying levels of archaicness.
It was implied, when during the brief conference of various models of Cylon, one remarked that humans would always seek revenge. This is to me something of an irony, considering.
s/Jodie Foster/Shirley MacLaine/
(That is, only one of them believed it off-set.)
Oh. Well, that's probably a good idea.
Moving to a default patching system is both a bad idea and impractical.
Not only does it raise the risk for a single flaw to cause catastrophe, but it raises the value of a single attack, makes a cross-platform attack feasable, and lowers the cost of attacking any select group of systems. Homogeneity is security disaster.
It's impractical because many systems work in fundamentally different fashions, and would have different needs for a patching system. I can't guess whether you mean all Linuxes, all Unices, or all OSes, because you're defensively vague with "on a larger scale", and if you mean all Linuxes this might maybe be feasable (I don't know the gamut of linux weirdness; I have no idea what Gentoo really does under the hood, for example,) but even for all Unices, things like QNX have demands that make this absolutely unacceptable.
Besides, diversity encourages competition and innovation. If we had One Huge System (tm), it would be excessively difficult to test new ideas. We do not at the moment have a patch distribution system which will just automagically handle a whole LAN, AFAIK; such a thing might never get off the ground if we all lived in the same yellow submarine. (If we do have such a thing, just pick some patch innovation that we don't have yet and substitute; the example isn't the important thing.)
I firmly believe in The Unix Way: small, interlockable pieces representing concrete ideas, which one can string together to achieve goals. You and I might prefer different patching mechanisms; The Unix Way provides for us to choose as we see fit. You might prefer to trust an authority and automatically get patched immediately; I might paranoiacally want the patch downloaded but not instituted until I verified, so that I had time to call the company IS guy and check. Or whatever.
I also believe that The Unix Way is why a platform with such ragged support and meager software library still completely owns the business world despite a decade of effort from the world's largest software-centered marketing company. If you may build your server from pieces, you may control characteristics of it which can be vital for new serving paradigms. This Is Important. (r) Do Not Break It For Convenience, Damnit. (c)(sm)
not an add on that you know to (1) know about
Uh, I don't even have a Linux box, and I found it with a quick google search. Perhaps you should visit to these informative
links.
You know, an enterprising attacker could just pull the trust network down. Someone with sufficient skill could very easily just work on Debian for five or six months, get trusted, and embed a subtle bug into a remote point.
I mean, we can't find the unintentional ones. What makes you think we could find one chosen for its obscurity?
Good idea or should we wait for a few more server compromises before we think about securing software repositories?
Yes, yes, because this doesn't already exist.
Oh, wait. apt-check-sigs, since 1998. I'm glad you're in the watchtower, Sam Spade.
Does anyone else see it as ironic that the name of the man which founded the company suing our heart's labor is named Ransom Love?
Fact: Spent fuelrods from reactors are a major enviromental problem.
Quite true. In fact, there is no power generation method without some impact. Construction of windmills' cement basings releases tremendous amounts of carbon dioxide, and destroys a fair amount of stone. Solar panels change the amount of heat hitting the ground, and take up a huge amount of area.
Our current common generation methods, coal and oil, release tremendous amounts of radioactive waste into the air both in mining and burning, as well as hundreds of other known carcinogens, carbon mon- and dioxide, soot, and general evil.
Spent fuel rods from reactors are a major problem, and not nearly as bad as the current major problems we ignore, which are burning holes in the upper layers of our atmosphere, and whose after effects are so thick that in some cities like LA and Mexico City are literally visible.
Moving from a 95% solution to a 98% solution is a good thing. Dig a hole in some granite mountain and dump them down there, or in some salt mine, or something. 'S a *lot* better than smearing it all over the air, and at least in 300 years when we get a better idea, we can go in, round it up, and change it.
CONTAINMENT IS GOOD.
NES: Sega Master System had better graphics by far, but NES games were better.
This is a point of difficulty during argument. What US gamers call the Sega Master Ssytem is in fact the Mark 3 base. Whereas it is true that the Mark 3 is superior to the NES, it didn't exist until 1986. Most pages will say that the Master System was released before the NES in Japan; that's the SG-1000, and it is not superior to the NES. The SMS Americans know and love postdates the NES by two years.
Game Boy: Lynx/Game Gear had much better graphics, but GB games were better.
The GameBoy was released in early 1989. The GameGear didn't show up until late 1991 - a two and a half year difference. The Lynx apparently only postdates the GameBoy by a few months, which is a surrise to me; you've got me there. I was under the misimpression that it too was later on.
Nintendo 64: Could've had amazing graphics, but Nintendo didn't help the developers enough.
Whereas I certainly agree (and point out that a lot of the problem was storage space for textures), the germane bit of the discussion was about the hardware.
I love Nintendo just as much as anyone else, but take those rose-colored glasses off.
Well, you've got me on the Lynx. The rest of this could use some reminders about the way history really went. I'll take off my rose colored glasses when you put on your research hat.
Heh. At least it's not WorkBoy 2.
Actually, this isn't accurate. GBA puts everything into a linear address space. It has two primary blocks of user ram: IWRAM, 32k, starting at 0x03000000, and EWRAM, 256k, starting at 0x0200000. There is room to expand *both* to 16meg. The BIOS and System ROMS (0m), IO registers (4m), Palettes (5m), video ram(6m) and OAM (7m) each have similar available ranges. 1m is completely unused.
:D
Better still, the top 4 bits of the address bus are completely unused (10m-FFm).
There's a *tremendous* amount of space for new RAM, new storage, new devices, et cetera. If N upgrades, there's more than 16m of room to work with.
Oh, that's like calling GM a niche player. Nintendo has the highest selling game system in the world, and the second highest selling television console not only in the world but in each major sector.
Also, "foo and foo-like are standard" is a silly thing to say. If foo is standard, foo-likes don't exist. Besides, the GC *does* use a dvd-like standard; it's very close to a mini-dvd.
As far as sony having realized the advantages of hard drives, erm, no, they haven't. Their baseline model doesn't come with a hard drive, and it is difficult to get the hard drive expansion. The high-end model, which is expected to cost more than triple what the baseline model does, is a PVR; the only reason there's a hard drive in there is that the PVR needs it.
Top-end video and audio capability? Can you name a Nintendo system that has ever been released that hasn't been the best graphics or sound of its day? Hint: there's only one, and that's because N dropped the ball on the GameCube. The reason you probably think of the PlayStation as having higher quality graphics hardware than the N64, which it doesn't, is that by comparison it had preposterous storage space, allowing it to do things like play prerendered movies.
Should Nintendo wish to continue, they should continue what they've been doing for over two decades. They've weathered corporate sabotage by Sony quite well, and maintain a lead over a company which has intentionally flushed over a billion dollars down the toilet trying to get well known. Sony has a huge advantage in that it is already a manufacturing giant, giving them margin leads that Nintendo can't compete with.
I suggest that you stop karma whoring and research a bit. They maintain a substantial position in the marketplace, and are gaining share while the other two players are losing it. There isn't a justifiable statemet anywhere in your comment. How you got 5, insightful is beyond me.
(-4, Ludicrous Under Scrutiny)
That's why the cube used them from the beginning - building up to the same hardware being used in a portable.
Though this is certainly a nice after effect. actually, this is not why the GC uses small discs. At the time, there was quite a bit of hemming and hawwing about how N wasn't going to move to discs for the portable, but rather wait for something SD/MemoryStick-ish.
The reason Nintendo abstained from CDs was loading time. The management of Nintendo at the time believed that the increase in cost and decrease in game volume would be offset by the ten to twenty seconds that they at the time believed that games would require as loading time fairly frequently; apparently, they believed that a situation like Resident Evil's would be the norm, and I find it disappointingly common in early (and occasionally even modern) PlayStation games.
As things progressed and as Nintendo's error became apparent, they tried to prepare external CD drve after external CD drive, only to be met with fundamental price problems that came from supporting multiple storage formats. Nintendo saw the CD as an albatross, though, and it wasn't until Sega successfully pushed the GD that Nintendo began to believe that a proprietary format was realistic.
Once they did, however, the load time issue because their primary focus. In order to reduce both seek time and to increase disc resilience to high speed, they came to the decision that a minidisc format, which has significantly less angular momentum, would be the best way to go. Besides, it offered a very strong protection against piracy, as nobody could make their discs without specialized hardware.
I do hope that they carry the disc format to the new portable machine; that would allow enterprising developers to write cross-platform software, something that currently *none* of the portable manufacturers offer (and really, a game which was intended for portability but which offered editors and maintenance tools on the less cramed home system seems ideal to me.)
Whereas I hope this happens, I really don't think that was the original reasoning.