Netscape had as many if not more browser specific extensions in its heyday than IE does now.
Also you missed my point completely, I said you should write code that does not prevent portability but if the portability adds complexity leave that complexity out if its unecessary.
Yeah, but how many times have you seen "eh just don't use that driver, its not stable yet" when dealing with linux? I give linux 100% leeway for crashing based on drivers. I don't know when linux was openly considered unstable let alone having the OS be blamed for bad drivers. What I have heard is that linux has poor hardware support (hear it less all the time) and I also hear that many of the existing linux drivers aren't ready for prime time neither of which blames the OS for anything.
I guess unfortunately the common person does not give this same leeway. If they see a BSOD (or a kernel panic in linux) they say "oh no my OS failed".
It could still easily be ported to alternate hardware as soon as there are custmores for NT on that other hardware. If you think about it xbox 2 will likely run a minimal, processor portable version of NT.
I think portability is for canoes is more to the point of "If running on multiple platforms isn't a customer requirement don't spend time and money on it." Proper design would always to do things the standard way which is most often the portable way. On the other hand if portability requires adding hundreds of interfaces (in order to support multiple subsystems, most of which will never be used) or special platform handling code (got I hate browser sniffing for dhtml) and there is no requirment for it then you should keep the product simple and not support that other platform.
Of course #20 was in regards to working inside your development team. I must agree that if everyone could do the same thing worldwide things would be better.
Um, what dream world are you in? Does MySQL have proper stored procedure support? Trigger support? I rest my case.
Thats not to say that MySQL doesn't do the job in many situations or that it is bad software, but calling it a full featured SQL server is sort of funny. Also comparing performance of MySQL to MS SQL in enterprise applications would be interesting. I don't know the result but I think that MS SQL is still "fastest" in the world depending on just how you rate it.
Would you blame the linux core kernel people for something that is broken in a module written by another group? I think thats the distinction thats trying to be made here. Windows the OS isn't necessarily broken just because there exists a set of drivers that are poorly written.
There may be a fundamental flaw in the os that makes it too easy for poor drivers to bring down the OS and that is definitely something that can be blamed on MS (or on the core kernel people in the case of linux) but if it just happens that a driver is crap it might really just be the fault of the driver author and not the OS author.
The conclusion that should be drawn from the fact that hardware can take the entire OS down is that hardware needs to be more isolated from the core of the OS. Any non-essential hardware should be able to do whatever it wants in its own little sandbox and not kill the OS. In xp this is mostly the case, video drivers being a large exception not that I have a clue what could be done better.
Every time my ATI or NVidia drivers fuck up, or my printer driver which is really crazy since it should have no reason to be in kernel mode and if it were in user mode it shouldn't blue screen.
Anyways, most of my bluescreens are due to privledged processes screwing things up. Maybe the processes shouldn't require themselves to be privledged and that can sort of be blamed on MS but on the other if you are a video driver you need a lot of info that could be expensive to pass out to user mode. Eh I don't know but you are right, not too many XP crashes that are really the fault of the OS these days.
They also failed to note how many of those bugs were ui errors equivalent to spelling and formatting errors. They also failed to note how many of the bugs were of the sort where the software differed from the spec but the outcome was still fully valid (which often get closed out as "we won't fix that" when they really should be closed as "that is by design" followed by opening up a bug against the spec).
Unfortunately that clean interface pushes some key functionality into not easy to use places. I guess they want to retrain me to think thier way, but I don't like it. The drop down "do everything" menu that is on many of the pages annoys me.
If you subscribe to MSN premium service the picture attachement problem is solved. They allow you to make a "picture mail" which allows you to attach a LOT of full size pictures but they are all stored on an MSN server, the mail is quite small as it only has the links to the picture location on the net. Thats the way to do pictures anyway, smtp is not efficient with large files.
This is pretty much a duplicate of the story last week, except in the story last week the RIAA had an excuse. They said that thier automatic allocation program had a bug and that they were fixing the issue. They also said there would be some sort of make good/exchange program in the works to help fix the problem.
It still might be a tax write off and a way to get rid of dead inventory, but they have an excuse. *smile*
Sorry it wasn't clear, but the first sentence was regarding challenger, the second was regarding the columbia breakup on re-entry. Two different events.
Except that the shuttle was in the wrong orbit to be able to reach the ISS on the fuel hey had left and they didn't have enough supplies to last until NASA was prepared to send any sort of help from down here on earth. Granted I'm basing my thoughts on the reports from NASA but they seemed reasonable to me.
Um, I don't call an exploding rocket booster a small problem.
I also don't call a big hole in the heat resistant paneling when you plan to endure metal melting temperatures a small problem either.
In contrast getting your ship pointed in the wrong direction for a while is smaller in that at least you get a chance to correct the problem (and in fact he had already corrected some issues in control moments after he fired the rockets proving he is an excellent pilot, damn lucky, or both).
All in all this flight was probably as perfect as any adventure into space can hope to be.
Here is my method for updating an XP box which hasn't failed yet (though has plenty of opportunity for failure, people just haven't taken the time to make thier worms pierce the XP firewall).
1) Shut down computer 2) Unplug net cable 3) Boot the install cd 4) complete install process 5) enable the XP firewall 5a) (optional) correctly configure an external firewall to put the XP pc behind 6) Plug in net cable 7) Download all updates
I've done this many times an never gotten a worm before update was complete. If I don't enable the firewall I can guarantee a worm in the first minute.
If you press the interview on any of those questions to get more than just the first sentence it becomes much more difficult to lie. Anyways the key isn't the answer itself but what that answer says about the person and how they think.
Some very knowledgeble interviewers will ask the first 3 questions. The idea isn't the straight up answer but instead its about how the person plans to handle thier life. It tends to be a relflection of the attitude they will put forth when working for you.
I do agree however that the last question is a good one, though it really asks the same thing.
Anyways, the hard part of an interview is getting below the surface which is what really matters in the end.
Something tells me that smuggling isn't that easy. I'm certain that you have to go through customs in one way or another to legally get back into the states.
Also transoceanic trips in a yacht aren't so easy as they might seem.
XP ran fine on my 333mhz AMD K6-2 as soon as I got more than 64meg of ram in it. Not nearly as good as on my dual athlon 1900+ but when I go to my parents house (where the computer still lives and still runs windows XP) its usable to browse the net and write e-mail.
I wouldn't start up office on the machine myself but it even seems to run that fast enough that my dad doesn't get pissed of at it.
Slashdot Mirror
Also you missed my point completely, I said you should write code that does not prevent portability but if the portability adds complexity leave that complexity out if its unecessary.
I guess unfortunately the common person does not give this same leeway. If they see a BSOD (or a kernel panic in linux) they say "oh no my OS failed".
It could still easily be ported to alternate hardware as soon as there are custmores for NT on that other hardware. If you think about it xbox 2 will likely run a minimal, processor portable version of NT.
I think portability is for canoes is more to the point of "If running on multiple platforms isn't a customer requirement don't spend time and money on it." Proper design would always to do things the standard way which is most often the portable way. On the other hand if portability requires adding hundreds of interfaces (in order to support multiple subsystems, most of which will never be used) or special platform handling code (got I hate browser sniffing for dhtml) and there is no requirment for it then you should keep the product simple and not support that other platform.
Of course #20 was in regards to working inside your development team. I must agree that if everyone could do the same thing worldwide things would be better.
Thats not to say that MySQL doesn't do the job in many situations or that it is bad software, but calling it a full featured SQL server is sort of funny. Also comparing performance of MySQL to MS SQL in enterprise applications would be interesting. I don't know the result but I think that MS SQL is still "fastest" in the world depending on just how you rate it.
There may be a fundamental flaw in the os that makes it too easy for poor drivers to bring down the OS and that is definitely something that can be blamed on MS (or on the core kernel people in the case of linux) but if it just happens that a driver is crap it might really just be the fault of the driver author and not the OS author.
The conclusion that should be drawn from the fact that hardware can take the entire OS down is that hardware needs to be more isolated from the core of the OS. Any non-essential hardware should be able to do whatever it wants in its own little sandbox and not kill the OS. In xp this is mostly the case, video drivers being a large exception not that I have a clue what could be done better.
Anyways, most of my bluescreens are due to privledged processes screwing things up. Maybe the processes shouldn't require themselves to be privledged and that can sort of be blamed on MS but on the other if you are a video driver you need a lot of info that could be expensive to pass out to user mode. Eh I don't know but you are right, not too many XP crashes that are really the fault of the OS these days.
They also failed to note how many of those bugs were ui errors equivalent to spelling and formatting errors. They also failed to note how many of the bugs were of the sort where the software differed from the spec but the outcome was still fully valid (which often get closed out as "we won't fix that" when they really should be closed as "that is by design" followed by opening up a bug against the spec).
Unfortunately that clean interface pushes some key functionality into not easy to use places. I guess they want to retrain me to think thier way, but I don't like it. The drop down "do everything" menu that is on many of the pages annoys me.
If you subscribe to MSN premium service the picture attachement problem is solved. They allow you to make a "picture mail" which allows you to attach a LOT of full size pictures but they are all stored on an MSN server, the mail is quite small as it only has the links to the picture location on the net. Thats the way to do pictures anyway, smtp is not efficient with large files.
It still might be a tax write off and a way to get rid of dead inventory, but they have an excuse. *smile*
Sorry it wasn't clear, but the first sentence was regarding challenger, the second was regarding the columbia breakup on re-entry. Two different events.
Except that the shuttle was in the wrong orbit to be able to reach the ISS on the fuel hey had left and they didn't have enough supplies to last until NASA was prepared to send any sort of help from down here on earth. Granted I'm basing my thoughts on the reports from NASA but they seemed reasonable to me.
I also don't call a big hole in the heat resistant paneling when you plan to endure metal melting temperatures a small problem either.
In contrast getting your ship pointed in the wrong direction for a while is smaller in that at least you get a chance to correct the problem (and in fact he had already corrected some issues in control moments after he fired the rockets proving he is an excellent pilot, damn lucky, or both).
All in all this flight was probably as perfect as any adventure into space can hope to be.
I think that they only need to have the weight of 3 people on board not three actual people.
Here is my method for updating an XP box which hasn't failed yet (though has plenty of opportunity for failure, people just haven't taken the time to make thier worms pierce the XP firewall).
1) Shut down computer
2) Unplug net cable
3) Boot the install cd
4) complete install process
5) enable the XP firewall
5a) (optional) correctly configure an external firewall to put the XP pc behind
6) Plug in net cable
7) Download all updates
I've done this many times an never gotten a worm before update was complete. If I don't enable the firewall I can guarantee a worm in the first minute.
They probably fit the filter definition of spam. I'm sure if you added the g-mail address to your safe list the mail would make it right through.
If you press the interview on any of those questions to get more than just the first sentence it becomes much more difficult to lie. Anyways the key isn't the answer itself but what that answer says about the person and how they think.
I thought that the ATI did its mpeg2 encoding in software.
I'd like to try out the Haupauge WinTV PVR-250 I've heard it works quite well.
I do agree however that the last question is a good one, though it really asks the same thing.
Anyways, the hard part of an interview is getting below the surface which is what really matters in the end.
Like the fool next door who runs wireless and wired connected to the i-net + ICS and has no idea how to configure it :)
Also transoceanic trips in a yacht aren't so easy as they might seem.
Creating dynamic flash content is remotely interesting but there is a library written to do it so using the library seems elementary.
I wouldn't start up office on the machine myself but it even seems to run that fast enough that my dad doesn't get pissed of at it.