scott wrote:
>> I said I'm bad at writing "large" documents - which is presumably what 
>> a final PhD thesis is. Also, all of my work at uni that involved any 
>> element of what academics refer to as "research" was extremely hard 
>> for me. I have no idea what "research" actually is, or how you're 
>> supposed to do it. As I understand it, a PhD is 82% research...
> 
> Didn't you have to do a final year project at university?

Yes. It was one of the subjects I had substantial trouble with...

I mean, sure, the *programming* part was pretty easy. Time-consuming, 
but not conceptually difficult. But there's supposed to be a "research 
element" in there - whatever the hell that's meant to mean. This gave me 
significant trouble.

> Usually that 
> is meant to be something relatively novel and consists of writing a big 
> report, so presumably that would be a good introduction for what you 
> would be doing during a PhD.

Distrubuted MVC.

VNC, X11, RPD, etc. work at the raster level, which is too low. HTML 
over HTTP doesn't support server push. If MVC could go over a network, 
all these problems would be eliminated. Apparently a tiny amount of 
prior art exists for this problem...

> One example that I heard you mention before of research, is getting 
> Haskell to work on a GPU.

> http://research.microsoft.com/research/default.aspx

Guess where this research is happening? ;-)

[Lots of Haskell-related stuff is funded by Micro$oft - for reasons I 
don't entirely comprehend yet...]

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message