Communist Chinese markets will soon be closed to foreign made chips
WTO provisions work strongly against that. With China's production and consumer markets (and 1.n billion consumers) about to join the international markets en masse, demand for processors (both in finished products and as components) will skyrocket. For various political reasons, China probably wants to serve that demand for CPUs internally rather than letting Taiwan or Malaysia do it. Having good native chip-fabs also provides R and D and industrial benefits.
There will likely be some IP-intensive government hardware coming down the pipe within the next five years, which a cool-running, military-hardened (slow but reliable) x86 processor will be useful for, especially one that can be readily adapted to integrate tightly with theembedded software applications of choice. Also, if they space-harden the core as they develop it now, they may gain an edge that way by beating out the P5 and P6-type stuff going up now from europe and the states.
Also, slower isn't necessarily a bad thing in military (or many other mission-critical) applications. An extra three or four nines of reliability is almost always worth a few hundred MHz when lives (and not frags or some database) are at stake.
"The so-called strange quark matter is so dense that a piece the size of a human cell would weigh a tonne."
The impact area of quark is probably somewhat smaller than a cell, the former being subatomic and all.
Also, "The so-called strange quark matter is so dense that a piece the size of a human cell would weigh a tonne." doesn't imply that the piece that they hypothesized passed through earth was the size of a human cell.
A fatal exception 0D has occurred at 0028:c0038f07 in VXD VMCPD(01) + 00002DB. The current time-line will be terminated.
* Press any key to terminate the current time-line. * Press CTRL+ALT+DEL again to restart the universe. You will lose any unsaved information in all existances.
Option 3: They develop their own "optimized" or "compatible" unfriendly linux kernel/lilo fork, add cruft to it, sign and release it (with oblique source). They could then claim that they're not anti-competetive, smear Linux a bit, and to a large extent maintain their cash flow by issuing "compatable" apps. This option also gives them the advantage of some protections via DMCA.
Circa 1993:
1) toll-free dial-in at 4800 on 7E1 to get local compuserve dial-in number
2) sign up for a new account, pay for using Visa/MC
3) access is granted
4) 'go epic'
5) Register Epic Pinball (and other great titles), billed to credit card, download SFX zip file, message sent to messaging account once transaction is successful.
I'm sure there are other compuserve/prodigy/etc examples that predate this (lexis-nexis comes to mind).
No, because a cigarette/matches/bic lighters don't generate enough heat to ignite Mg let alone your sorry karma-whoring "I can't be insightful so I'll impress everybody with my hum0r" ass...
Fuck marklar. I've known since marklar how to use marklar/marklar's properly, but I hereby propose dropping the marklar. There's no situation in which marklars use is ambiguous, and therefore the marklar contains no marklar - its marklar, a marklar marklar marklar from when marklar had no notion of marklar. Best case marklar move every marklar to marklar, 2nd best drop the marklar from our marklar instead of worshiping arbitrary marklar. Fuck marklar's.
I think that XNS has a chance of doing this type of thing better than any of the closed source alternatively like Passport.
Holy fsck is that ever ignorant!
Why are open-sourced foo always better than closed-sourced or company-owned foo? And why do most/.ers just accept that on faith? Sure, many great things have come out of open source, but that does not automatically qualify everything stamped with GPL/BSD/licence-du-jour or appears to have a transparent process as a Good Thing, just as not every thing published by the big-bad-company is a Bad Thing.
As it stands now, Passport exists, appears to be scalable, and works most of the time, which is a lot more than I can say for XNS. And yes, Passport has problems right now and will have problems in the future, as will XNS. It's a part of the development process which can't be avoided but at least Passport is out there now, being used, attacked, and debugged, before it or anything else becomes somewhat of a universal standard when real $$ is at stake.
And given the choice of who to fix an emergent security concern in their respective systems, would you trust the well-intentioned staff of XNS, who are either very knowledgable but potentially few and far between (cf recent slashdot and K5 outages), or somewhat knowledgable and found in abundance; or Passport, staffed 24x7 by an army of people who at least know what they are doing and are eventually liable to shareholders and business partners who have multi$billions to throw around (or not)?
XNS and anything else that comes along will necessarily have to learn from the mistakes made by Passport now, and I don't think that's a Bad Thing. As it stands right now, the afore-mentioned army of developers _who evolved the current system over 5+ years and must listen and respond to customer and partner concerns or lose business measured by six or seven zeros on a daily basis_ aren't getting it entirely right, so why would I think that an emergent cadre of excellent but not-entirely-devoted developers with comparatively zero funding can _build and maintain_ what amounts to a public infrastructure (something which doesn't lend itself well to being maintained by an entity, staffed by few enough people that they can all be killed in one incident, and without real-world liability for failure) to serve billions of people world-wide? I don't.
I've had similar problems with M13 and beyond on W98, NT4 and W2K where moz just decides that every URL points to the page set as home (http://google.com/), regardless of wether the link was clicked or typed, or whatever non-/index.html page is in the link.
Refreshing/reclicking/retyping/new windows will still show google's page with the URL http://slashdot.org/ (and yes, junkbuster and other proxies show requests for google.com regardless of what is displayed in the URL, even for non-existant domains.
As far as I can tell, the only way to fix this is to completely close moz and restart and hope that it decides to not make google.com and slashdot.org the same. (For watever reason, it's like there's a 2 in 3 chance that moz will not bother understanding anything but the home page, much like windows and blue screens.)
And then of course, there's the talkback thing randomly spiking processor usage to 99%, but that's probably something else.
This isn't an Outlook problem as much as it is a Win32/PEBCAK problem.
Here at (unnamed major university, which fortunately is in its non-busy season), I've recieved about 6 different copies of the thing in the last two hours (two form the IT department!!!) from people (faculty, other students, random, outside) using outlook, netscape messenger, pine, and eudora. A major problem are people who aren't clued about stripping attachments when replying/forwarding, and who are indoctrinated at an early age (students) to forward every stupid gif/flash animation they get.
No offense to the local list maintainers and users, but if "subject: unsubscribe events-l" gets through the major domo...
This doesn't sound quite right, since AFAIK there's no reason a CD player should skip over a TOC any more than a CD-ROM drive would, so I'm assuming they used multiple sessions and gave all but the first bogus TOCs since CD players only read the first session.
It's trivially easy to select which session to grab TOCs out of. It's a right-click in Win2K and I think it even existed in NT4, so no news here.
My best guess at the moment is that the protection has more to do with 'signal strength' (reflectivity) on the disc itself rather than any other kind of digital fsckery. A big difference between audio CD players and CD-ROM drives are the tolerences behind what does and does not get read as a 1 or a 0 on the disc (hence CD-ROMs are able to read CD-R's and CD-RWs which have about ~30 to 40 per cent of a pressed silver disc's reflectivity, while some audio players fsck up on writable media). Now, if they overlay two signals (pits), one at 100 per cent (picked up by both CD players and CD-ROMs) with another signal at 35 per cent or so (below whatever detection threshold of the audio players but above that of CD-ROM drives), the CD-ROM will misread the signal while the audio players read it normally.
Aint it cool? According to the article, Humans are actually coded OO style:-)
Uhm... No.
The snippet you cite there describes a bunch of copy+paste operations done on a block of code [DNA] (not necessarily something as sophisticated as a function though) as it is written with minor modifications [mutations] for each imperfect copy [slightly different gene]. It's almost like taking a small loop containing conditionals which depend on i and rolling it out so that i is hard-coded and each rolled-out loop contains only the conditional important to it. In both cases, the modified duplicates remain close together but for different reasons (If I have to change something in each instance of my rolled-out loop, I can scroll down to it vs The DNA sequence in/around the region of interest is conducive to this type of duplication).
The OO metaphor can be 'kind-of' observed in DNA or protein sequences which have alternative splicing. For instance, a protein kinase, which cuts a peptide [method], can recognise different sequences to cut at depending on what recognition factor gets spliced in at the time the protein is made. So a kinase can be initialized with the "cut-at" property equal to "valane-leucine" or equal to "phenylalanine-isoleucine" or whatever combination, depending on what sequence gets spliced in. Genes and proteins with alternative splicing are, however, very rare (we have not found many... yet).
While you are correct in that we have a lot more to discover about gene/protein interactions, I question your motives behind the cut-and-paste.
What aspects of discovering that we share (mostly) the same set of transcriptional regulators as jellyfish, mice, and apes do you find not useful? Noticing that a receptor related to feeling pain in humans is homologous with those found in pigs, which we have a drug for, must be a bad thing. How about the insights into anthropology gained by comparing the 40 or so publicly known partial sequences floating around, knowing more about humans must be bad.
Sure, we can't look at the geneome and spit out a cure for cancer in a week but efforts so far have been anything but useless (not to mention the tangental effect of developing new sequencing and computing technologies to handle all that data...)
Oh, and if you had read the article, you would notice that a significant portion of this newest round of discoveries concerns grouped genes with similar function, which is useful for development of drugs which can target entire metabolic pathways which can lead to disease, insted of individual components of that pathway.
"To prevent counterfeiting and laundering, all bills must be 'validated' by a bank every 90 days or the bills expire."
--> A bank doesn't like a certain type of customer and invents administrative hurdles to prevent validation, or 'accidentally' invalidates a bunch of notes they just issued.
--> Authorities ask banks to expire a bunch of stolen notes, but not before the criminal has traded them for goods.
--> Relations with Pottsolvania aren't great, let's invalidate all their US currency.
--> Authorities roam the streets "on the wrong side of the tracks" with bank note detectors to look for high concentrations of notes...
--> And best of all: Unless people carry note readers, they have no way of verifying authenticity or validity of notes. Once they've adopted the readers, the notes can be tracked at each transaction...
Slashdot Mirror
Communist Chinese markets will soon be closed to foreign made chips
WTO provisions work strongly against that. With China's production and consumer markets (and 1.n billion consumers) about to join the international markets en masse, demand for processors (both in finished products and as components) will skyrocket. For various political reasons, China probably wants to serve that demand for CPUs internally rather than letting Taiwan or Malaysia do it. Having good native chip-fabs also provides R and D and industrial benefits.
There will likely be some IP-intensive government hardware coming down the pipe within the next five years, which a cool-running, military-hardened (slow but reliable) x86 processor will be useful for, especially one that can be readily adapted to integrate tightly with theembedded software applications of choice. Also, if they space-harden the core as they develop it now, they may gain an edge that way by beating out the P5 and P6-type stuff going up now from europe and the states.
Also, slower isn't necessarily a bad thing in military (or many other mission-critical) applications. An extra three or four nines of reliability is almost always worth a few hundred MHz when lives (and not frags or some database) are at stake.
"The so-called strange quark matter is so dense that a piece the size of a human cell would weigh a tonne."
The impact area of quark is probably somewhat smaller than a cell, the former being subatomic and all.
Also, "The so-called strange quark matter is so dense that a piece the size of a human cell would weigh a tonne." doesn't imply that the piece that they hypothesized passed through earth was the size of a human cell.
Microsoft people have claimed in sworn testimony that it's impossible to remove IE from the OS, though.
Yes, testimony true of the then-current versions of Windows, not of software they had not yet written.
Show me a great tool with a shitty UI...
...and I'll show you a shitty tool.
Apache.
Waiting.
A fatal exception 0D has occurred at 0028:c0038f07 in VXD VMCPD(01) + 00002DB. The current time-line will be terminated.
* Press any key to terminate the current time-line.
* Press CTRL+ALT+DEL again to restart the universe. You will lose any unsaved information in all existances.
Option 3: They develop their own "optimized" or "compatible" unfriendly linux kernel/lilo fork, add cruft to it, sign and release it (with oblique source). They could then claim that they're not anti-competetive, smear Linux a bit, and to a large extent maintain their cash flow by issuing "compatable" apps. This option also gives them the advantage of some protections via DMCA.
you can get 15000 RPM scsi drives and only 7200 RPM IDE
Last time I checked, the rotational speed of the disk has little to do with what protocol is used to access it.
CD images aren't archived or indexed for searching by Google et al.
I *still* have to tell Win98 that I'd like to remove a PCMCIA device, so it can then *allow* me to remove it.
To allow cached transactions to complete, close interfaces and make voltage conditions safe.
Unless you want broken files, programs halting for lack of data and device damage.
/dev/random more like it. Stop posing.
/dev/null has the advantage of being largely compressable on the stack.
Data from
Circa 1993:
1) toll-free dial-in at 4800 on 7E1 to get local compuserve dial-in number
2) sign up for a new account, pay for using Visa/MC
3) access is granted
4) 'go epic'
5) Register Epic Pinball (and other great titles), billed to credit card, download SFX zip file, message sent to messaging account once transaction is successful.
I'm sure there are other compuserve/prodigy/etc examples that predate this (lexis-nexis comes to mind).
No, because a cigarette/matches/bic lighters don't generate enough heat to ignite Mg let alone your sorry karma-whoring "I can't be insightful so I'll impress everybody with my hum0r" ass...
Fscking lameness filter... Mirror: Now WITH pictures :-)
http://web.thock.com/cubefire.htm
Fscking lameness filter...
Mirror: sans pictures
http://web.thock.com/cubefire.htm
Fuck marklar. I've known since marklar how to use marklar/marklar's properly, but I hereby propose dropping the marklar. There's no situation in which marklars use is ambiguous, and therefore the marklar contains no marklar - its marklar, a marklar marklar marklar from when marklar had no notion of marklar. Best case marklar move every marklar to marklar, 2nd best drop the marklar from our marklar instead of worshiping arbitrary marklar. Fuck marklar's.
I think that XNS has a chance of doing this type of thing better than any of the closed source alternatively like Passport.
/.ers just accept that on faith? Sure, many great things have come out of open source, but that does not automatically qualify everything stamped with GPL/BSD/licence-du-jour or appears to have a transparent process as a Good Thing, just as not every thing published by the big-bad-company is a Bad Thing.
Holy fsck is that ever ignorant!
Why are open-sourced foo always better than closed-sourced or company-owned foo? And why do most
As it stands now, Passport exists, appears to be scalable, and works most of the time, which is a lot more than I can say for XNS. And yes, Passport has problems right now and will have problems in the future, as will XNS. It's a part of the development process which can't be avoided but at least Passport is out there now, being used, attacked, and debugged, before it or anything else becomes somewhat of a universal standard when real $$ is at stake.
And given the choice of who to fix an emergent security concern in their respective systems, would you trust the well-intentioned staff of XNS, who are either very knowledgable but potentially few and far between (cf recent slashdot and K5 outages), or somewhat knowledgable and found in abundance; or Passport, staffed 24x7 by an army of people who at least know what they are doing and are eventually liable to shareholders and business partners who have multi$billions to throw around (or not)?
XNS and anything else that comes along will necessarily have to learn from the mistakes made by Passport now, and I don't think that's a Bad Thing. As it stands right now, the afore-mentioned army of developers _who evolved the current system over 5+ years and must listen and respond to customer and partner concerns or lose business measured by six or seven zeros on a daily basis_ aren't getting it entirely right, so why would I think that an emergent cadre of excellent but not-entirely-devoted developers with comparatively zero funding can _build and maintain_ what amounts to a public infrastructure (something which doesn't lend itself well to being maintained by an entity, staffed by few enough people that they can all be killed in one incident, and without real-world liability for failure) to serve billions of people world-wide? I don't.
</rant>
I've had similar problems with M13 and beyond on W98, NT4 and W2K where moz just decides that every URL points to the page set as home (http://google.com/), regardless of wether the link was clicked or typed, or whatever non-/index.html page is in the link.
Refreshing/reclicking/retyping/new windows will still show google's page with the URL http://slashdot.org/ (and yes, junkbuster and other proxies show requests for google.com regardless of what is displayed in the URL, even for non-existant domains.
As far as I can tell, the only way to fix this is to completely close moz and restart and hope that it decides to not make google.com and slashdot.org the same. (For watever reason, it's like there's a 2 in 3 chance that moz will not bother understanding anything but the home page, much like windows and blue screens.)
And then of course, there's the talkback thing randomly spiking processor usage to 99%, but that's probably something else.
This isn't an Outlook problem as much as it is a Win32/PEBCAK problem.
Here at (unnamed major university, which fortunately is in its non-busy season), I've recieved about 6 different copies of the thing in the last two hours (two form the IT department!!!) from people (faculty, other students, random, outside) using outlook, netscape messenger, pine, and eudora. A major problem are people who aren't clued about stripping attachments when replying/forwarding, and who are indoctrinated at an early age (students) to forward every stupid gif/flash animation they get.
No offense to the local list maintainers and users, but if "subject: unsubscribe events-l" gets through the major domo...
This doesn't sound quite right, since AFAIK there's no reason a CD player should skip over a TOC any more than a CD-ROM drive would, so I'm assuming they used multiple sessions and gave all but the first bogus TOCs since CD players only read the first session.
It's trivially easy to select which session to grab TOCs out of. It's a right-click in Win2K and I think it even existed in NT4, so no news here.
My best guess at the moment is that the protection has more to do with 'signal strength' (reflectivity) on the disc itself rather than any other kind of digital fsckery. A big difference between audio CD players and CD-ROM drives are the tolerences behind what does and does not get read as a 1 or a 0 on the disc (hence CD-ROMs are able to read CD-R's and CD-RWs which have about ~30 to 40 per cent of a pressed silver disc's reflectivity, while some audio players fsck up on writable media). Now, if they overlay two signals (pits), one at 100 per cent (picked up by both CD players and CD-ROMs) with another signal at 35 per cent or so (below whatever detection threshold of the audio players but above that of CD-ROM drives), the CD-ROM will misread the signal while the audio players read it normally.
Aint it cool? According to the article, Humans are actually coded OO style :-)
Uhm... No.
The snippet you cite there describes a bunch of copy+paste operations done on a block of code [DNA] (not necessarily something as sophisticated as a function though) as it is written with minor modifications [mutations] for each imperfect copy [slightly different gene]. It's almost like taking a small loop containing conditionals which depend on i and rolling it out so that i is hard-coded and each rolled-out loop contains only the conditional important to it. In both cases, the modified duplicates remain close together but for different reasons (If I have to change something in each instance of my rolled-out loop, I can scroll down to it vs The DNA sequence in/around the region of interest is conducive to this type of duplication).
The OO metaphor can be 'kind-of' observed in DNA or protein sequences which have alternative splicing. For instance, a protein kinase, which cuts a peptide [method], can recognise different sequences to cut at depending on what recognition factor gets spliced in at the time the protein is made. So a kinase can be initialized with the "cut-at" property equal to "valane-leucine" or equal to "phenylalanine-isoleucine" or whatever combination, depending on what sequence gets spliced in. Genes and proteins with alternative splicing are, however, very rare (we have not found many... yet).
While you are correct in that we have a lot more to discover about gene/protein interactions, I question your motives behind the cut-and-paste.
What aspects of discovering that we share (mostly) the same set of transcriptional regulators as jellyfish, mice, and apes do you find not useful? Noticing that a receptor related to feeling pain in humans is homologous with those found in pigs, which we have a drug for, must be a bad thing. How about the insights into anthropology gained by comparing the 40 or so publicly known partial sequences floating around, knowing more about humans must be bad.
Sure, we can't look at the geneome and spit out a cure for cancer in a week but efforts so far have been anything but useless (not to mention the tangental effect of developing new sequencing and computing technologies to handle all that data...)
Oh, and if you had read the article, you would notice that a significant portion of this newest round of discoveries concerns grouped genes with similar function, which is useful for development of drugs which can target entire metabolic pathways which can lead to disease, insted of individual components of that pathway.
cf. Simpson, Homer; Flanders, Ned :-)
Power corrupts... absolute power is kinda neat!
:-)
Then WinXP is very neat
Imagine this:
"To prevent counterfeiting and laundering, all bills must be 'validated' by a bank every 90 days or the bills expire."
--> A bank doesn't like a certain type of customer and invents administrative hurdles to prevent validation, or 'accidentally' invalidates a bunch of notes they just issued.
--> Authorities ask banks to expire a bunch of stolen notes, but not before the criminal has traded them for goods.
--> Relations with Pottsolvania aren't great, let's invalidate all their US currency.
--> Authorities roam the streets "on the wrong side of the tracks" with bank note detectors to look for high concentrations of notes...
--> And best of all: Unless people carry note readers, they have no way of verifying authenticity or validity of notes. Once they've adopted the readers, the notes can be tracked at each transaction...