Slashdot Mirror

Ah yes, Mises who famously said that not even God can do central planning. I see your Mises and raise you Turing completeness.

If you're going to read one of them, read Hayek, not Mises.

Well, if you're looking for a romp through mathematics, how can we leave out the sad tale of Pretty Little Polynomial and Curly Pi?

How strange. Hayek claims that a decentralized algorithm can do things a centralized algorithm can't. With all other computers or systems, the opposite is true. P outranks NC in complexity theory (unless P == NC, which is an open question like P == NP, but one suspects both are inequalities ). Mises goes further and claims that not even God could simulate the market. That is, it's not an issue of information. Curiouser and curiouser!

See also this: Is Economic Planning Hypercomputational?

(And if it's impossible for an ordinary algorithm to find the optimum, but the market finds the optimum, how can we know that that is the true optimum? We have no simulation that will work, after all.)

Some of this was tried in the Haskell community, with relatively unimpressive results---a lot of algorithms are mostly sequential, even in a parallel language, and the speedups, especially after futures/whatever overhead, aren't amazing, especially past 2 cores or so.

That's my understanding of why most current research is on adding primitives that let the programmer specify parallel algorithms at the source level, such as Parallel Haskell's par and seq primitives.

Basically the automatic reordering the compiler can do doesn't really suffice, at least with any method anyone's figured out so far; to get anything close to a 64x speedup with 64 cores, you really do need the programmer to write parallel algorithms explicitly.

I'm not talking about functional programming. Functional programming is great, and has a lot going for it, but solving concurrent programming issues is not one of those things. Functional programming deals with concurrency issues by simply avoiding them. For problems that have no state and can be coded purely functionally this is fine, but for a large number of problems you end up either tainting the purity of your functions, or wrapping things up in monads which end up having the same concurrency issues all over again. It does have the benefit that you can isolate the state, and code that doesn't need it is fine, but it doesn't solve the issue of concurrent programming.

Not every monad is the IO monad or a state monad; having functional code wrapped up in a monad doesn't inherently force sequential evaluation and one of the great strengths of purely functional languages like Haskell is the guarantee that you won't have side-effects -- thus any function call, anywhere at all, can be executed in its own thread without any worry about blocks or volatile memory.

The IO monad is admittedly a black box, but in practice very little of a well coded Haskell program is wrapped up in the IO monad.

Referential transparency means parallelization and memoization, two of the most promising optimisation techniques moving forward. While it is certainly possible to write very fast parallelizable imperative code, the complexity quickly becomes untenable precisely because imperative programming is so tied to sequencing and makes the often completely unnecessary assumption that one statement must follow another. Because Haskell and its derivatives make the opposite assumption -- that order doesn't matter and that functions should be executed if and only if their values are needed to move computation forward -- one ends up with programs where the compiler knows exactly what can be parallelized and what cannot be. Language extensions like those found in the Glasgow Parallel Haskell project further increase parallelization potential by introducing some explicit parallelization and barrier keywords.

Of course, one is still left with the language-agnostic problem of developers writing crappy algorithms that can't easily be parallelized when one a parallelizable one would do the trick. But it's often a trade-off: for example, easily paralleizable functional algorithms are often slower than their non-parallelizable imperative counterparts in a single-core world.

Some of my colleagues (e.g., Vittorio Cristini) have been modeling the potential benefits of nanoparticle drug delivery for a couple of years now. As has been known for some time (e.g., see papers from R.K. Jain), the blood vessels that grow to supply tumors with nutrients (the tumor-induced neo-vasculature) are different than regular, non-pathological vessels. They tend to be more tortuous and leaky, with larger holes than regular vessels.

This is where the nanoparticles come in: one can design nanoparticles that encapsulate cancer drugs in particles that are too large to exit normal blood vessels but can pass through the leakier, tumor-induced blood vessels. This naturally targets cancerous tissues.

However, there are other issues to consider. Due to the high pressure inside tumors (due to the rapid proliferation of cells within a confined area, among other factors), along with the leaky vessels, blood flow can be very poor inside a tumor, and so while the drug may be targeted toward and delivered to the tumor, it may not actually penetrate very far into the tumor. Some great work has been done by Steven McDougall, Sandy Anderson, and Mark Chaplain in this area. In particular, look at their DATIA (dynamic adaptive tumour-induced angiogenesis) papers.

One way around this (suggested by R.K. Jain and Vittorio Cristini, among others) is to use targeted anti-angiogenic therapy to prune out the worse blood vessels and improve flow within the tumors, thereby also improving drug delivery and penetration.

Lastly, on the therapeutic aspect of blocking up tumor blood vessels with the nanoparticles, the work we've done (see this paper, which will appear in the Journal of Theoretical Biology soon), indiscriminately cutting off the nutrient supply to a tumor can increase tumor invasiveness by increasing morphological (shape) instability. (See some of the animations here.) So ironically, while more tumor cells may be killed, those that remain may spread farther and initiate new tumors. Given that hypoxic tumor cells are more likely to be resilient to further treatment (e.g., hypoxic breast cancer cells), this is a problem worth keeping in mind when planning anti-angiogenic therapy.

If you're interested in these topics, please do check out the paper above. (You can also download it at my website without any special memberships.) Even if you don't like it, we have a lot of references you may find handy. -- Paul

So, while the mathematical model of growth might represent some predictive value, it certainly will not effectively model new developments, such as the above, when they are found.

There's still plenty of value to be found in higher-scale models. (e.g., how the tumor as a whole interacts with the microenvironment, how proliferation-induced pressure turns off the vasculature and prevents drug delivery, how oxygen and glucose delivery throughout the tumor and the microenvironment affects the patterning of hypoxic and necrotic cells, which, in turn, affects angiogenesis and matrix degradation) Cancer is a multiscale problem, with interaction between all the scales. Focusing on one scale alone (molecular or tissue-scale) likely will not solve the entire problem.

In fact, developing a good tissue-scale model is a natural step toward creating a multiscale model, where molecular- and cell-scale dynamics affect the growth parameters that govern tissue-scale behavior. (Similarly to how the behavior of individual molecules leads to things that can be averaged at larger scales, like heat, viscosity, etc.) First, you fix the parameters and neglect the small-scale dynamics to figure out the large-scale behavior. Then, you model the small-scale dynamics and learn how to couple them to the previously-fixed parameters.

On a tangent, I also worked with "Sandy" Anderson in a different U.S.-Scottish collaboration. He's a really great guy, as well as Mark Chaplain and Steven McDougall. And Sandy is a pretty incredible cook! :-) -- Paul

Back in 1986, it amazed me that home computers like the Atari 800 could do 16 colour graphics, while the IBM PC could only do four colours from a fixed palette.

EGA was a slight improvement, but it wasn't until VGA came along with multisync monitors that the fun really began. And there were all those wacky coprocessor cards that tried to bypass the CPU (some image processing cards had four transputers or a i860 for signal processing (Microway Quadputer/Number Smasher 860), Other had a TMS34020 for graphics or a builtin Ethernet controller so that images could be downloaded directly into video memory). And 8 Megabytes of video memory was considered generous.

What happened to those expert systems that seemed so promising in the 70s and 80s? I don't believe a doctor can weigh up the range of symptoms that a patient might have, and the even bigger range of symptoms that a patient doesn't have, more reliably than a machine, in order to make an assessment of the probability of the patient having any particular disease. MYCIN is one that comes to mind but there were others. I was under the impression that they had performed better than doctors in tests.

Other groups working on optical interconnects: (incomplete list)

Heriot Watt

Cornell University

IBM Zurich

Delft

UIUC

Intel

Stanford

There are software engineer positions in the UK, but they are only interested in foreign workers or entry level graduates it seems - here's a job advert.

Yeah, we have a similar problem here in the United States too. My understanding of the scam is, some company find a foreign worker they'd like to import on an H1-B visa, but first they have to advertise the job, so they do so, and the ad features a mind-numbingly long list of nitpicky requirements that happen to exactly match the H1-B applicant, and when no one can match those criteria, they get to import their guest worker.

I had the same experience with job interviews a couple of years ago; "what can do you do that graduates can't do?"

Gee, I dunno, how about your ability to apply experience and spot problems before they start, instead of stupidly running right off the cliff? The problem is the managers too don't have enough insight to avoid running right off the cliff.

"Undoubtably you could do the work of three graduates if not more, but given the economic situation, we have to take on as many graduates as possible"

Uh...er...huh? I don't even begin to understand that. Are you more expensive than 3 graduate students put together? Or is there a London in Japan these days? :-)

Employers are advised by financial analysts not to allow any one person to gain a monopoly of knowledge within the company, and to avoid this situation by taking on a constant stream of graduates, or rotate staff between departments.

WHAT?!?! How about avoiding the situation with proper documentation and proper technical oversight??? Oh yeah, that would require brains and skill. Can't have that.

You should consider studying for a Masters degree. These days, for any kind of architect position, you need a Masters degree if not a Ph.D.

Get a higher degree in a subject where there already aren't any jobs? You sure about that? I'd love to get my Ph.D. in Computer Science, but don't see the point.

Are you about 50 miles north of Los Angeles? :-)

Was 200 miles North of London, but now 300 miles working at university. Nearly landed my dream job, only to have a certain console manufacturer decide they wanted the most qualified graduate to work on AI). There are software engineer positions in the UK, but they are only interested in foreign workers or entry level graduates it seems - here's a job advert.

I had the same experience with job interviews a couple of years ago; "what can do you do that graduates can't do?" or
"Undoubtably you could do the work of three graduates if not more, but given the economic situation, we have to take on as many graduates as possible".

Employers are advised by financial analysts not to allow any one person to gain a monopoly of knowledge within the company, and to avoid this
situation by taking on a constant stream of graduates, or rotate staff between departments.

You should consider studying for a Masters degree. These days, for any kind of architect position, you need a Masters degree if not a Ph.D.

Not so. My girlfriend is working on this. They have managed to send keys at large data-rates over conventional networks up to a distance of several tens of kilometers. In fibre networks, this distance approaches the pitch of the amplifiers.

You are right about not being able to amplify the signal though.

I'm puzzled as to why Legos hold such fascination for slashdotters, in light of that.

Maybe because the most advanced lego models (for anyone who was a teenager back in the 1980's at least) consisted of one or more moving systems (the 8860 car consisted of a rack and pinion steering mechanism, gear box, differential gear and suspension system. If you managed to get a copy of the 8888 advanced model guide, you could also build a Lego robot dog, Lego printer, and the most advanced purely mechanical (ie. no electronics) Lego model, the Programmable Crane"

Once you learnt the basics of how various things worked, you started combining these to make even more complex models (eg. robot arms).

The patience and creative thinking required to make these models naturally extended itself to home computer programming, and eventually to a career in the computer industry.

I'm puzzled as to why Legos hold such fascination for slashdotters, in light of that.

Maybe because the most advanced lego models (for anyone who was a teenager back in the 1980's at least) consisted of one or more moving systems (the 8860 car consisted of a rack and pinion steering mechanism, gear box, differential gear and suspension system. If you managed to get a copy of the 8888 advanced model guide, you could also build a Lego robot dog, Lego printer, and the most advanced purely mechanical (ie. no electronics) Lego model, the Programmable Crane"

Once you learnt the basics of how various things worked, you started combining these to make even more complex models (eg. robot arms).

The patience and creative thinking required to make these models naturally extended itself to home computer programming, and eventually to a career in the computer industry.

I'm puzzled as to why Legos hold such fascination for slashdotters, in light of that.

Maybe because the most advanced lego models (for anyone who was a teenager back in the 1980's at least) consisted of one or more moving systems (the 8860 car consisted of a rack and pinion steering mechanism, gear box, differential gear and suspension system. If you managed to get a copy of the 8888 advanced model guide, you could also build a Lego robot dog, Lego printer, and the most advanced purely mechanical (ie. no electronics) Lego model, the Programmable Crane"

Once you learnt the basics of how various things worked, you started combining these to make even more complex models (eg. robot arms).

The patience and creative thinking required to make these models naturally extended itself to home computer programming, and eventually to a career in the computer industry.

I'm puzzled as to why Legos hold such fascination for slashdotters, in light of that.

Maybe because the most advanced lego models (for anyone who was a teenager back in the 1980's at least) consisted of one or more moving systems (the 8860 car consisted of a rack and pinion steering mechanism, gear box, differential gear and suspension system. If you managed to get a copy of the 8888 advanced model guide, you could also build a Lego robot dog, Lego printer, and the most advanced purely mechanical (ie. no electronics) Lego model, the Programmable Crane"

Once you learnt the basics of how various things worked, you started combining these to make even more complex models (eg. robot arms).

The patience and creative thinking required to make these models naturally extended itself to home computer programming, and eventually to a career in the computer industry.

I always thought a Von Neuman machine was just a computer where the data and the instructions to be executed were stored in some temporary storage medium, like RAM...

Link

Wow! Was that the self-assembled version, or the kit version? I've seen the adverts for the ZX81

Here are some adverts from that era

Applications for games and applications.

It's amazing they managed to get a flight simulator (if a bit blocky) running.

The $149 computer

The $99.95 computer

Here are some adverts from that era

Applications for games and applications.

It's amazing they managed to get a flight simulator (if a bit blocky) running.

The $149 computer

The $99.95 computer

Here are some adverts from that era

Applications for games and applications.

It's amazing they managed to get a flight simulator (if a bit blocky) running.

The $149 computer

The $99.95 computer

Games could allow more than two players. Perhaps even enough to play a full game of soccer or football! (The picture showed a "dome" with controls in a ring around it.)

There are networked arcade racing games. While they may not have been that popular at $0.50 for 1 minute, they are much more playable for a kid's birthday party, where the cost is included for a whole afternoon's entertainment.

Games will be able to be played over great distances! (The picture showed a chess board with a wireless antenna on it.)

You can play a chess game with another person using your mobile phone.

Games will be so much more realistic! (Shows a handheld game with a full scene of a motor bike jumping a dirt ramp.)

The latest handheld games are going to be able to do this.

For anyone who's interested, I've scanned in some old Byte magazines from 15-20 years ago.

That's what early graphis accelerator boards were like in the 1980's - Vectrix VX 384

It was Smoke Signal Broadcasting. Some of the hand-drawn cartoons were amusing though.

Well, I just had a quick look on Freshmeat and found:

RoseGarden
Sweep
Ardour
Audacity
Protux
DAP
ReZound
GLAME

Until today, both ML and Haskell had a common problem: a lack of commercial and real world interest in it and therefore a lack of real-world libraries and supporting frameworks. But now things are going to be changed.

First Ericson came with Erlang, an excelent essence of FP, LP, scripting and networking. Now M$ (I know - evil, but anyway) came with F# bringing OCaml to the real world saving from being forgotten somewhere in Inria.

What next? I think that would be Haskell, the language even more suprior to ML, with already OOP, Parallel and Cuncurrent extensions. Also I like its Functional-Logical dialect - Curry. But who will bring it to the real world? IBM?

Until today, both ML and Haskell had a common problem: a lack of commercial and real world interest in it and therefore a lack of real-world libraries and supporting frameworks. But now things are going to be changed.

First Ericson came with Erlang, an excelent essence of FP, LP, scripting and networking. Now M$ (I know - evil, but anyway) came with F# bringing OCaml to the real world saving from being forgotten somewhere in Inria.

What next? I think that would be Haskell, the language even more suprior to ML, with already OOP, Parallel and Cuncurrent extensions. Also I like its Functional-Logical dialect - Curry. But who will bring it to the real world? IBM?

Fuck you cunt.
http://hal.trinhall.cam.ac.uk/~nrs27

Try making your cunt signature a link. I hate that shit. Fucking cunt.

Your site is fag gay.

Neil you are a fag.

Your PGP key isnt there because you cant get it to work with Outlook.

Your house looks like a pigsty shithole typical of fat people who get no sex.

Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

You have broken links, prick.

W3C validator found errors in your shit site.
Genrally you make me sick

Line 9, column 42: . . ^Error: unknown entity "apos" . .
Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 34, column 18: . that went wrong
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 36, column 13: . and pieces
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 37, column 50: . . ull example of MS Word applying itself to html)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 38, column 50: . . ct areas, using an abbreviation for the course.
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 30: . Slashdot
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 48: . Slashdot
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 39: . The Register
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 60: . The Register
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 37: . The Inquirer
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 58: . The Inquirer
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 36: . BBC News
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 53: . BBC News
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 47, column 14: . Branch)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 18: . Peter
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 33: . Peter
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 42: . Chris
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 56: . Chris
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 43: . John
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 56: . John
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 43: . Joe
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 56: . Joe
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 43: . Matt
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 56: . Matt
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 43: . Stu
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 54: . Stu
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 42: . Dr. Simon Moore
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 66: . Dr. Simon Moore
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
Line 65, column 3: .
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

Fuck you cunt.
http://hal.trinhall.cam.ac.uk/~nrs27

Try making your cunt signature a link. I hate that shit. Fucking cunt.

Your site is fag gay.

Neil you are a fag.

Your PGP key isnt there because you cant get it to work with Outlook.

Your house looks like a pigsty shithole typical of fat people who get no sex.

Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

You have broken links, prick.

W3C validator found errors in your shit site.
Genrally you make me sick

Line 9, column 42: . . ^Error: unknown entity "apos" . .
Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 34, column 18: . that went wrong
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 36, column 13: . and pieces
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 37, column 50: . . ull example of MS Word applying itself to html)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 38, column 50: . . ct areas, using an abbreviation for the course.
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 30: . Slashdot
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 48: . Slashdot
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 39: . The Register
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 60: . The Register
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 37: . The Inquirer
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 58: . The Inquirer
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 36: . BBC News
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 53: . BBC News
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 47, column 14: . Branch)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 18: . Peter
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 33: . Peter
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 42: . Chris
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 56: . Chris
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 43: . John
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 56: . John
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 43: . Joe
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 56: . Joe
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 43: . Matt
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 56: . Matt
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 43: . Stu
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 54: . Stu
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 42: . Dr. Simon Moore
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 66: . Dr. Simon Moore
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
Line 65, column 3: .
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

"But now Weed believes his newest innovation, the Problem Knowledge Coupler, is finally ready for mainstream use."

No kidding. This is not really an innovation by any stretch. Rule-based diagnostic systems such as MYCIN first appead in the '70s!

XPath is a partial query language for XML - it can read, but it has no way of updating the document.

There's also the issue that XPath is very much an XML tool, with a tight binding between semantics and structure (which is the whole thing that I'm saying about XML in the first place). If you have a graph represented in XML, then it's hard to write XPath expressions that can traverse it. If you have RDF stored in XML (which has several possible serialisations for the same semantic content) then it's possible to write XPath that expands these, but it's hard, error-prone, and generally unworkable.

There's still a lot of thought out there that XSLT can translate magically between schemas. Some groups see XML Schema as improving this (Hunter & Lagoze, WWW10). Although Alison Cawsey's paper from WWW 9 shows just why this approach doesn't work. I've abandoned my own work in this field for similar reasons; even though I managed to build something workable, I just never trusted it to be reliable.

Right now, I compose music using a few linux software tools. The mediocre (but increasing!) quality of the software available right now is offset by the good quality hardware I use. The SB Live has open source drivers that are very bleeding edge (there is no MIDI support for the front panel yet, so I don't use MIDI :) My roland JP-8000 can synthesize any sound there is, and the recording from the emu10k1 in the SB Live is top notch.

I know that the abuse will take place.

I just don't know what to do about it.

If you protest, you are taged as a Communist which is ironic since the US has already adopted Communism. Carl Marx had an idea of what it would take for a country to be Commuist, and we seem to have followed his rules fairly well.

You don't even have to be protesting and the mentality of a police state will send me to the hospital.

Ratting 4 - Just blowing off steam.

Same here (a segfault). Although the BUILD file for hewx in the source distribution says that "wxHugo was developed with wxWindows 2.1 snapshot 8 and later" it only seems to work with snapshot 8, not 9!
I got it from here. Brilliant game, BTW!