One thought... If you are only going to learn 1 or 2 languages, I would recommend that those languages be ones that expose more underlying concepts ( machine architechture, pointers, etc, etc ). Like C/C++, et al. Personally, I would recommend more than just one or two languages. The more you are exposed to, the more different ways to "skin the cat" you will know.
I would also add a compiler construction course to the above. You will be amazed how much easier picking up those other languages will be, if you know the basics of how a compiler/interpreter works.
And there is a precident for this. Apparently, breaking apart old ships is done there. They drag it up on the beach, and the down and outers work on it.
Dos isnt done until Lotus doesnt run? DR Dos "activities"?
1) I dont know, but I would not rule out MS playing with the Win32 SDK. It was new, and those outside MS would know the true direction and have access earlier. Those outside would be at a disadvantage. I believe that they did. Proof? Well, nothing except past MS behaviour.
2) See number 1. Also, it was not clear at that time that Windows was going anywhere. The only company that was going to bet the farm on Windows was the author of Windows.
AFA letting go? I would presume that Novell would not be following this up if they did not expect to have a chance to win.
does this make MS any better or worse then any other corp that wont play nice with the competition? No it doesn't.
Corps are ( supposed to be ) limited here in the US in how they can go about these things. When a company has a monopoly hold on a market, the rules change, and they are not allowed to do some things that are permissible when there is competition. Like some of the things MS has done to stifle others.
Netscape, Stac, etc, etc.
MS cannot and would not try to stop you from this.
Read up on some recent history. MS *has* and does attempt ( and they succeed ) at stopping those that want to compete with them.
I personally think that Linux is about the only way to reintroduce competition, MS cant kill it, cant buy it, cant do much about it. But look at what that means, no ordinary company can expect to compete ( not without immensely deep pockets, and a very very long range plan ).
If MS switched every kernel to BSD based, slashdot would still find a reason to call them evil, and create more FUD just because it's MS
A: Unix != good business. SCO for example. The complaint I have ( and I think, many others ) is based on their actions in the market, not thier technology. ( I do tire of them spouting about having "the best" this and that, when they are basically average ( note, I did *not* say worst, just average ), but that is another rant ).
So, since switching to a BSD kernal would not change their business practices, yes, we probably will continue to call them bad until they change.
FUD? Just because it is true? Just because they have gotten away with it?
The "collected exception handling in one place" model usually leads to
A: Poor or ugly error reporting. Usually it is difficult to figure out what line above threw the error, so the report devolves to "something bad happened". It is then difficult to figure out what did happen. In the cases where the main body throws disjoint exception types, obviously this would not be the case, but you would have a large number of catch blocks, one for each type that could be thrown.
B: Poor or ugly cleanup. Deallocating everything that was allocated in the main body can be interesting. If everything is "deallocated-in-destructor", then you are safe.
But, I cant get cooler without shedding clothing. And I am not wearing all that much to start with. You, on the other hand, could become warmer very easily.
I am glad that you are healthy, wealthy and wise. I havent made it yet. Should I suffer for this, despite my best efforts in these directions?
Slashdot Mirror
One thought... If you are only going to learn 1 or 2 languages, I would recommend that those languages be ones that expose more underlying concepts ( machine architechture, pointers, etc, etc ). Like C/C++, et al. Personally, I would recommend more than just one or two languages. The more you are exposed to, the more different ways to "skin the cat" you will know.
I would also add a compiler construction course to the above. You will be amazed how much easier picking up those other languages will be, if you know the basics of how a compiler/interpreter works.
You were not informed, but each letter in every newspaper is tagged such that they know where the paper was printed and when.
And there is a precident for this. Apparently, breaking apart old ships is done there. They drag it up on the beach, and the down and outers work on it.
Dos isnt done until Lotus doesnt run?
DR Dos "activities"?
1) I dont know, but I would not rule out MS playing with the Win32 SDK. It was new, and those outside MS would know the true direction and have access earlier. Those outside would be at a disadvantage. I believe that they did. Proof? Well, nothing except past MS behaviour.
2) See number 1. Also, it was not clear at that time that Windows was going anywhere. The only company that was going to bet the farm on Windows was the author of Windows.
AFA letting go? I would presume that Novell would not be following this up if they did not expect to have a chance to win.
Yer prolly a troll, but just in case.
does this make MS any better or worse then any other corp that wont play nice with the competition? No it doesn't.
Corps are ( supposed to be ) limited here in the US in how they can go about these things. When a company has a monopoly hold on a market, the rules change, and they are not allowed to do some things that are permissible when there is competition. Like some of the things MS has done to stifle others.
Netscape, Stac, etc, etc.
MS cannot and would not try to stop you from this.
Read up on some recent history. MS *has* and does attempt ( and they succeed ) at stopping those that want to compete with them.
I personally think that Linux is about the only way to reintroduce competition, MS cant kill it, cant buy it, cant do much about it. But look at what that means, no ordinary company can expect to compete ( not without immensely deep pockets, and a very very long range plan ).
If MS switched every kernel to BSD based, slashdot would still find a reason to call them evil, and create more FUD just because it's MS
A: Unix != good business. SCO for example. The complaint I have ( and I think, many others ) is based on their actions in the market, not thier technology. ( I do tire of them spouting about having "the best" this and that, when they are basically average ( note, I did *not* say worst, just average ), but that is another rant ).
So, since switching to a BSD kernal would not change their business practices, yes, we probably will continue to call them bad until they change.
FUD? Just because it is true? Just because they have gotten away with it?
See there, on the dial. Not 10, 11!
I think it was the exclaimation marks more than anything. That and a great parent post to work from.
No, the OS that stays crunchy in milk!
Filled with vitamin fortified DLL's!
And a free application in every box!
If I want to separate Nitrogen from Oxygen, just pay the oxygen tax, dont pay the Nitrogen tax!
So simple!
Finding the drum after it has smashed thru the brick walls.
Or right.
Water is kinda scarce.
A beowulf cluster of PC fans cooling your cars engine.
That they did not confiscate, impound or destroy the items was bothering me a bit.
What happened to due process? Shouldnt there first be a court finding that there was a violation? Then enforcement? Or was this done already?
What does Customs have to do with enforcing copyright? Shouldnt that be a court issue? On what basis can they tell her to remove items from the shelf?
The "collected exception handling in one place" model usually leads to
A: Poor or ugly error reporting. Usually it is difficult to figure out what line above threw the error, so the report devolves to "something bad happened". It is then difficult to figure out what did happen. In the cases where the main body throws disjoint exception types, obviously this would not be the case, but you would have a large number of catch blocks, one for each type that could be thrown.
B: Poor or ugly cleanup. Deallocating everything that was allocated in the main body can be interesting. If everything is "deallocated-in-destructor", then you are safe.
OK.. More easily than I can get cooler.
Note also, that I dont know what your particular office environment is. Maybe it just is too cold for everyone there.
You have a point there.
:-)
I know! How about a heated keyboard!
a, c, e
for me.
But, I cant get cooler without shedding clothing. And I am not wearing all that much to start with. You, on the other hand, could become warmer very easily.
I am glad that you are healthy, wealthy and wise. I havent made it yet. Should I suffer for this, despite my best efforts in these directions?
body
That would be the belly button!
Good idea, thanks!
I thought of that, but I was hoping for a "everything points at machine 'x'" solution, for those brain-dead moments. :-)
Also, I am used to switching with the key commands, not by hitting the buttons on the front of the kvm, so...
I dont yet have two monitors, ( waiting, waiting ).
Thanks!
Are there kvm switches that handle multi-monitor setups?