>>I think that the kde desktop is much easier then any windows in the past or current. There's a reason.
>And what reason would that be?
That windows 8 sucks big time. (I use it everyday so I know). And kde is easy to use. (I use it everyday too!)
Your ATI is funky between distros isn't because there isn't an ABI (there is, it's opensource you can't get more ABI then that!) It's because ATI has problems. I don't switch between distros much so I can't really comment on why ATI is having problems, but all I can say that with Sabayon or Gentoo they've worked flawlessly.
As for IE support, I don't give a flying fuck.
Point is there is no reason to change to Win8. If you are using Windows 7 and like it stick with it. Win 8 wasn't built for the desktop.
Also this discussion was about using Linux for Non-Technical users. I still support that kde is easier to use then Windows of any strip but probably not enough to change if you have already learned MS's system. If you haven't used any system kde is the way to go.
Given a price of $1.17 per liter, and given 3.78541 liters per gallon, I paid around $4.42 per gallon.
I like how the US sticks to imperial, then changes the size of the gallon to smaller so you think you aren't paying as much. At least in Canada we know we are paying through the nose. We export to the US so does that mean that Canadian citizens are supporting the US economy? We are actually paying for you to drive?
I sometimes just don't get it.
I think that the kde desktop is much easier then any windows in the past or current. There's a reason.
But VERY FUNNY and very different. (although I like her earlier work best!)
I hope so, it would be great to get a lithograph 3d printer.
I've got a makerbot and have had no problems with overhang. I've been able to bridge 2.5 cm's and it's perfect. There were some minor problems with the kit, but it was a very enjoyable project. If you have any skills at building things at all you can do it, and it's fun.
If I had mod points I would moderate you at +1 missed the obvious.
And I must say that as the Editor in Chief he has a very simplistic view of the problem. If I understand, his view is that a global exception added at the compiler level would somehow solve all the problems. He gives the example of calling "open" without worrying about it failing. Of course he doesn't state how to handle the failure when it occurs. For example
What happens to file1 in this case? How is the code cleaned up? There may be a case where you don't want to just close all files in the functions, but just create file2 if the open failed. (for example).
His complaint is that there is too many options available for error handling, and that they lead to cluttered code. As far as I can see the alternative is not enough options available and code not always doing what you want, and having to fight the compiler in order to get what you want.
The trouble with opportunity is that it always comes disguised as hard work. -- Herbert V. Prochnow