But most of all because (IMHO) it's not as easy to use as either linux or OSX. I love Linux because I get all the control I want at 0% of the cost. I love OSX because it does everything windows is supposed to do but more intuitively, in my experience faster and with gratuitous use of transparency. I love the two together because they play nicely. Personally I don't see a niche for Windows in my future.
Mochasoft's answer to the ctrl-key problem is to have a row of buttons at the bottom (Ctrl Esc Fx F1x) - for Ctrl-C you hit the Ctrl button and then write a 'c'. It works pretty well.
I'd much rather use putty but it is pretty difficult to use without modifier keys.
Okay I was a little disappointed to hear that the Appeals Court was going to get this first. But people here are right, M$ should get their chance like everyone else even if they can afford the best lawyers money can buy. Unfortunately I don't think the issue is any longer about whether M$ are good or evil.
They are going to do their best to tie us all up with C# and VB and whatever-dot-net If they are broken up next year or 3 years from now or never it's not going to make much difference. What will make a difference is that companies like IBM, Compaq, Dell other big hardware folks are now significantly less scared of them and are free to sell and support the alternatives.
Personally I hope that Microsoft ends up being the Corel of the new Millenium. Loads of monolithic software that nobody uses and those of us who remember the old days chuckle about over our beers.
I just got NT booting under VMware under RedHat6.2 so I can use Linux full time at work to develop Win32 Apps. A year ago I had no choice but NT4.
If I can't completely forget about Microsoft within two years I'm going to quit the tech business and become a lumberjack.
Whether or not it's good or evil to go snooping through someone else's trash, I for one am much happier that it's come to light that these pro-M$ groups were financed by M$. Would that information have come out in a timely fashion otherwise? And it definitely has a bearing on the future of M$. As they obviously realize, the unwary masses are their major support right now.
By all means prosecute Oracle later on if they indeed broke the law - but hey the information is already out there. Hiring a private dick is not in the same class as hijacking an entire industry. IMHO.
They want an easily supported alternative to VB that looks standards compliant and doesn't encourage people to move to other platforms. C and C++ is still the way to do it (no don't take away my pointers, I like my pointers) and everybody else will continue to use them because for some things there is no substitute short of assembly. Why spend the time mastering everything when you can do it all with one tool. But the VB people might finally get to write some solid server code. I agree with everyone flaming the name. What were they thinking?
I couldn't agree more. Ive been writing Win32 for three years and I've yet to see a proper object. MFC does a poor and inefficient job of abstracting the morass of Win32 API functions in an OO way. The only truely OO Desktop OS API of which I'm aware is BeOS.
There are significant innovations - The DLL loading mechanism is pretty cool and fairly efficient but a nightmare to maintain. Win2K improves it but you still don't really know which lib is used where. COM under it all is a solid binary object solution. It's got a bad rap from the bad implementations (eg OLE) that have been built on it. There are some great ideas but all the great ideas in the world won't help if they aren't fully thought out. The MS research group has some cool stuff going on on their website but the only thing I've seen make it mainstream is MS Agent. And who cares about that?
It bugs me too that MS tries to sell VB as the way to build Win32 apps. You can't debug it. You don't know what all the ActiveX controls are doing and why they might generate an exception. Since VB5 you can't even fire an event on a seperate thread. Doesn't sound like much but it makes multithreading and object orientation in apps that use VB much more difficult than they should be.
But the worst thing is that whether or not what comes out of MS research is great stuff, the decision to build it into (or leave it out of) the OS is subsequently forced down the throats of all of us who don't have the luxury of running something else. MS doesn't need anybody's assurance that it's a good idea. they have their own agenda and features are not included or excluded solely on the basis of improving the lot of the user.
Do a couple of things pretty well. As long as you stick to the demo templates you are fairly safe. But that doesn't get you very far. As a web server Domino has some very frustrating anomalies mostly arising from the internal Form and View model. It all looks very attractive as a single package but when you get under the hood there are a million things you have to work your way around.
I don't know how the Linux beta runs - I have it but I haven't had a chance to get it running yet. I run Domino R4.6 under Solaris and that performs better than almost all other platforms I've seen it run on.
Given the choice I'd go the Linux and Apache route every time.
flashback to 1992: i'm trying to print a postscript document generated by m$word, and guess what? some printers hang, some mangle the document, few print it correctly. the problem was unique to micro$oft, i've never seen anyone else's postscript do this, ever.
Slashdot Mirror
But most of all because (IMHO) it's not as easy to use as either linux or OSX. I love Linux because I get all the control I want at 0% of the cost. I love OSX because it does everything windows is supposed to do but more intuitively, in my experience faster and with gratuitous use of transparency. I love the two together because they play nicely. Personally I don't see a niche for Windows in my future.
Mochasoft's answer to the ctrl-key problem is to have a row of buttons at the bottom (Ctrl Esc Fx F1x) - for Ctrl-C you hit the Ctrl button and then write a 'c'. It works pretty well.
I'd much rather use putty but it is pretty difficult to use without modifier keys.
http://www.mochasoft.dk/
Okay I was a little disappointed to hear that the Appeals Court was going to get this first. But people here are right, M$ should get their chance like everyone else even if they can afford the best lawyers money can buy. Unfortunately I don't think the issue is any longer about whether M$ are good or evil.
They are going to do their best to tie us all up with C# and VB and whatever-dot-net If they are broken up next year or 3 years from now or never it's not going to make much difference. What will make a difference is that companies like IBM, Compaq, Dell other big hardware folks are now significantly less scared of them and are free to sell and support the alternatives.
Personally I hope that Microsoft ends up being the Corel of the new Millenium. Loads of monolithic software that nobody uses and those of us who remember the old days chuckle about over our beers.
I just got NT booting under VMware under RedHat6.2 so I can use Linux full time at work to develop Win32 Apps. A year ago I had no choice but NT4.
If I can't completely forget about Microsoft within two years I'm going to quit the tech business and become a lumberjack.
Whether or not it's good or evil to go snooping through someone else's trash, I for one am much happier that it's come to light that these pro-M$ groups were financed by M$. Would that information have come out in a timely fashion otherwise? And it definitely has a bearing on the future of M$. As they obviously realize, the unwary masses are their major support right now.
By all means prosecute Oracle later on if they indeed broke the law - but hey the information is already out there. Hiring a private dick is not in the same class as hijacking an entire industry. IMHO.
They want an easily supported alternative to VB that looks standards compliant and doesn't encourage people to move to other platforms. C and C++ is still the way to do it (no don't take away my pointers, I like my pointers) and everybody else will continue to use them because for some things there is no substitute short of assembly. Why spend the time mastering everything when you can do it all with one tool. But the VB people might finally get to write some solid server code.
I agree with everyone flaming the name. What were they thinking?
I couldn't agree more. Ive been writing Win32 for three years and I've yet to see a proper object. MFC does a poor and inefficient job of abstracting the morass of Win32 API functions in an OO way. The only truely OO Desktop OS API of which I'm aware is BeOS.
There are significant innovations - The DLL loading mechanism is pretty cool and fairly efficient but a nightmare to maintain. Win2K improves it but you still don't really know which lib is used where. COM under it all is a solid binary object solution. It's got a bad rap from the bad implementations (eg OLE) that have been built on it. There are some great ideas but all the great ideas in the world won't help if they aren't fully thought out. The MS research group has some cool stuff going on on their website but the only thing I've seen make it mainstream is MS Agent. And who cares about that?
It bugs me too that MS tries to sell VB as the way to build Win32 apps. You can't debug it. You don't know what all the ActiveX controls are doing and why they might generate an exception. Since VB5 you can't even fire an event on a seperate thread. Doesn't sound like much but it makes multithreading and object orientation in apps that use VB much more difficult than they should be.
But the worst thing is that whether or not what comes out of MS research is great stuff, the decision to build it into (or leave it out of) the OS is subsequently forced down the throats of all of us who don't have the luxury of running something else. MS doesn't need anybody's assurance that it's a good idea. they have their own agenda and features are not included or excluded solely on the basis of improving the lot of the user.
Do a couple of things pretty well. As long as you stick to the demo templates you are fairly safe. But that doesn't get you very far. As a web server Domino has some very frustrating anomalies mostly arising from the internal Form and View model. It all looks very attractive as a single package but when you get under the hood there are a million things you have to work your way around.
I don't know how the Linux beta runs - I have it but I haven't had a chance to get it running yet. I run Domino R4.6 under Solaris and that performs better than almost all other platforms I've seen it run on.
Given the choice I'd go the Linux and Apache route every time.
flashback to 1992: i'm trying to print a postscript document generated by m$word, and guess what? some printers hang, some mangle the document, few print it correctly. the problem was unique to micro$oft, i've never seen anyone else's postscript do this, ever.