I don't really see the problem Boyd describes - of people concentrating on other team member's weaknesses. Most of the time I see people are only too willing to acknowlege other peoples strengths, but not in a positive way. Instead they say stuff like "Dave is really good at the database stuff so why doesn't he do it", i.e. they use other peoples strengths in an area as an excuse to not become proficient in that area themselves, to redirect responsibilities to others.
Boyd must have a really good team if that doesn't happen in his team because I've seen it everywhere I've worked to the extent that the company 'expert' in a given area has resigned because they're fed up with just doing that one particular thing.
I like the way he answered the "what langauge did you use to develop this?" with "DirectX". That's a real manager's answer
Jul 21, 2004 at 5:25 PMThe thing where the window shrinks down into a thumbnail on the desktop instead of to the taskbar ("scalable fabric"?) - isn't there something like that in the latest Mac OSX?
As for the dragable taskbar - I've wanted to drag the buttons on the taskbar since the Win95 days. I thought we might have got it in Win2k as you could drag start menu items and quicklaunch buttons, but still no taskbar button dragging...
And the thing to save and restore app windows - Borland had a program called Dashboard for win3.1 back in 93/94 that did just that (among other things). It suffered from the program though that asside from the cranky old OLE compound document interfaces, there is no standard way to get an application to persist the state of it's user interface in Windows (or any other OS I'm aware of). Sure we can see what programs are running, save their window sizes/locations and try to work out for certain common apps what documents are loaded, but as a general purpose solution it's a bit of a pipe-dream.
This product is looking like a must-have. It's adding some serious value to using visual studio which I was starting to wonder about given the amount of stuff that's just given away in the SDK now (and there have always been plenty of better text editors out there!).
Has it been decided yet whether MSDN subscribers get Team System and if so at what level?
Jul 15, 2004 at 4:00 PMThat's good to hear. I'm really keen on the msbuild functionality. It seems a lot of "real developers" if they use devstudio at all use make to build instead of using the project manager function. Thing is, I really hate make, half-baked unix relic that it is, and from what I've read msbuild is just the thing to finally put it out of its misery.
Anyway, on the subject of the team system stuff, I was thinking for a lot of that video "hey, this is just like Nunit/CSUnit/etc. but integrated" and then just as the guy was expanding on the more interesting tests it ended!
btw. Isn't this going to tread quite badly on the toes of quite a few 3rd part tools vendors? It sounds like a clone for TestComplete to pick one example.
Wow, it's been a while since I heard anyone promoting microkernels. Like '90s style
The microkernel dream doesn't really pan out in reality. Apart from the performance issues Charles mentions, it is quite feasible for a device driver to crash the machine whether it's running in kernel or user mode because it by definition needs to have access to the hardware. OK, you could make the driver go through kernel to sanity-check all the IO operations, but that would make it yet slower still.
As for other people's comments about hardware to directly execute bytecode... Sun tried this with Java and it's not really practical. The stack based architecture of the JVM and CIL isn't designed for hardware execution. That's not to say you can't design hardware that would execute the code, but rather that you would have trouble doing all the speculative and out-of-order execution that modern CPUs do. You could of course translate the CIL into another more conventional register-based instruction set behind the scenes and then take advantage of the huge amount of existing knowlege about how to execute that quickly, and this is what Trasmeta do. If you go this route though it's difficult to see what benefit you then have over a regular JIT like the CLR.
That's not all Microsofts' lot is it?
Anyway, the goof: As Lenn is getting out of the truck at the end the camera flips back to Eric and the shot is of him while they were on the open road, not parked up at the drop-off point.
And no, I don't spot continuity erorrs in movies as a rule