Any info about Iomega (IOM)? Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Non-Tech : Any info about Iomega (IOM)?

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Cogito who wrote (47989)	2/16/1998 12:53:00 PM
From: AreWeThereYet	Read Replies (1) of 58324

Allen *OT* >> But there seem to be many programmers who have no trouble writing something to make it crash. Sometimes it doesn't crash completely, it just slows down to the point of being unuseable, so you end up having to reboot. << This apply to virtually all OS. Name me one mutlitasking OS which is not crashable. Especially when you define "slow down to unusable" as crash but in reality they are different. NT is reliable due to the fact that it is hard to bring down the whole system to halt. Even a dozen of applicaitons crashed, the system is still handling jobs from existing running process. The UI may crash so that no new process is allowed to schedule but what is already running is protected. This is why I consider stupid when MS decided to move GDI to ring0. I can understand the reason for NT Workstation but it is unacceptable on NT Server since it is a potential bomb for the whole system. The system will halt when ring0 is dead. There is no question that Mac has better program de/installation design, this is true even when compare to NT since it is pretty much the same as Win95. I must also admit that "fail to follow the guideline" is not the only reason for the uninstall mess. Another reason is the program bug but it is not the problem of the OS. The idea of DLL is good for shared component, If you installed multiple applications which use share component (ie: MS Office products) in Mac, uninstall one of the applicaton will go thru the same registry checking process as Win95 (tell me if you can think of a more elegant design). It is the programmer's fault who decide to left the orphan entries in the registry and not the OS. Unfortunately backward compatibility is very important, there is too many legacy system which is too expensive to migrate. There are bugs everywhere and as a computer programmer, we can only work around the problem. aC

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next