Last estimates I heard placed Longhorn's release in 2007, so I think they'll be the ones catching up if desktop Linux development continues at anywhere near its present pace.
I agree. Every pad that Gravis has ever made is absolute garbage. Aside from a handful of Saiteks and my trusty Thrustmaster Firestorm, I've found that the only acceptable controller is a good old Playstation controller with PSX->USB adapters, especially for PSX/SNES/Genesis emulation.
It doesn't matter that there's corporate red tape if there's a problem. I don't care what your company's policies are as an end user; I don't work there. If your red tape is preventing my product from working properly, get rid of the red tape and fix the damn problem or I, as a customer, am finding a new product.
If your software is so tangled in intertwined components that a patch for an issue this simple would conceivably break something elsewhere on your system, then your terrible product design is the concern, not the QA.
I'd imagine they're using sessions of some kind to keep track of your IP address, since I visited the site before and the direct link from Slashdot works fine for me.
Again just to reiterate my point. people don't care about which OS they run. they want their computer to be like their cars. "if i got someplace else and sit in a car i should be able to drive it". We need to change the marketing strategy of UNIX.
That's part of the problem. The beauty of cars is that we're all driving on the same roads. Microsoft, on the other hand, likes to damage interoperability in such a way that to get from your house to 7-Eleven, you have to convert your automatic transmission to a manual transmission and connect your headlights to the top of your car, and then on the way back your car gets infected by the Internet Explorer worm of the month and ends up going the wrong way down a highway at 120 MPH.
The irony comes later in the article when, he says something to the effect of "Windows is better because Aunt Madge gets confirmation that her email was sent," because I've never seen a single email client give "sent" confirmation.
Therein lies a fundamental part of the problem itself -- Microsoft's APIs are so entirely overcomplicated and nonintuitive that you need all kinds of API documentation. When I'm creating a simple Windows GUI application, I don't want to memorize 32 different properties of a WNDCLASS or WNDCLASSEX, and I don't want to pile half of my application's GUI code into an event loop. I think the UNIX "everything is a file" methodology combined with a self-describing signal/slot mechanism in the GUI toolkits means I shouldn't even need an API reference because I can do everything I need to with only a limited subset of standard C/C++ functions. Third-party libraries are, with few exceptions, equally simple. You can figure out how to do things in SDL, for example, by looking at the headers and function prototypes because they're self-explanatory -- no figuring out needless and cryptic DirectX COM calls and the like. If you remember what the function is called then you can easily recall how to use it. I don't get that ease-of-development on Windows systems, for certain, unless I'm using third-party toolkits like wxWindows.
I do agree, however, that documentation is much more important than having full access to the source code for a particular API.
I am in the exact same situation. I'd been an XFce4/Gnome user ever since I switched to Linux full-time over the summer, up until a few weeks ago when I compiled the whole of KDE since I needed a good bit of it for K3B anyway.
KDE seems even more responsive than XFce4 on this machine, and it's the primary reason why Konqueror is now my new browser, KWord is now my new word processor and Quanta Plus is now my new HTML/PHP editor. I, like my sibling poster, still use a handful of GTK+ applications (Evolution, Gaim, Pan, Nicotine, The Gimp) but they certainly do feel noticeably slower than the Qt applications on my desktop right now. I'm running a performance-tuned prelinked Gentoo system, however, so I'm not 100% entitled to say how something would perform on a "normal" binary-based Linux installation.
Of course, this is entirely without taking into effect the excellent design of Qt's derived widgets, the elegance of KDE's kioslaves, customizability of toolbars, common widgets and file dialogs, and so on.
The only thing I can say KDE is deficient in is its user interface, but this is perfectly in line with Eric Raymond's Art of Unix Programming, separating policy from mechanism. Every interface issue in KDE can get sorted out in a single.1 version release. GNOME's going to have a much harder time catching up because they've spent all of their time concentrating on a consistent user interface that's lacking such common sense features as "undo" in a textbox or a usable file dialog.
Especially considering that one of the features that was paid so much attention in the review was that "Personality" Linux emulation layer. How is that any different from the one featured in FreeBSD? Of course, FreeBSD won't need it for most things anyway, since stuff will actually compile on it.
In 1970, nearly every vehicle was rear wheel drive. Nowadays, nearly every vehicle is front wheel drive and and can handle much more safely, in addition to coming equipped with standard anti-lock brakes and, in most cases, airbags. Vehicles have crumple zones designed to reduce the risk of injury or fatality in a frontal collision.
Don't you think these should be taken into consideration as a factor in determining the speed limit?
Then you're entering a legal grey area with regards to copyright infringement, especially when you're mirroring pictures, videos, etc. without permission.
I think that would still be preferred by most site authors to DoSing, though.
I don't agree with this line of thinking. Typically, when speeding isn't enforced, it's for a reason -- the officer realizes that if the person is going over the speed limit, but is driving responsibly -- staying in the center of their lane, not constantly changing lanes and cutting people off -- they're not a danger. The danger comes from people who drive aggressively, and these people are threatening at any speed. Speeding laws provide a pretext to pull these people over, because "he thought I was driving too aggressively" is debatable in court due to its subjectivity. "My radar clocked him going 10 miles over the speed limit," however, is much harder to refute.
Now if the highway is not busy most (if not all drivers) are violating the law by speeding. It's bad because it creates a style of thinking: "it's ok beacuse everyone's doing the same". No need to mention that many people are dead from speeding.
First off, if everyone on the 55 MPH freeway is driving a 75 MPH and you're moving at 20 MPH below the speed of traffic, you are yourself creating a potential traffic hazard, so you would be more likely to be involved in an accident, possibly the result of road rage, at the speed limit than at the speed of traffic.
How can someone be dead from speeding? If the road is wet and someone skids and wraps around a telephone pole at 60 miles per hour, do you really think the effect is going to be that different than at 55 miles per hour? If they're driving faster than that in the rain, the issue is that their car is going faster than it and/or the driver can safely handle in those conditions -- it has little to do with what number appears on the sign.
Again, I'd like to see some conclusive studies that speed limits actually help these situations. There's always a political or emotional spin on statistics released. How many of people killed in 85 MPH accidents were drunk? How many managed to fall asleep at the wheel? How many were talking on a cell phone? Obviously it helps somewhat but I'm curious just how much.
No. The site appears to be Slashdot, and the URL above seems to point to slashdot.org, but this is really a hoax taking advantage of an Internet Explorer exploit allowing, through JavaScript, the location in the address bar to be spoofed.
Are you kidding? Winamp5 has been in active development for months and to my knowledge they just released RC1 after a long alpha/beta cycle. Sure, Winamp3 hasn't been touched in a year -- that's because it sucks and you're unlikely to find a person on the planet who doesn't agree.
Shit, at least learn what you're talking about before you go spewing verbal diarrhea.
As already mentioned, the Ximian Connector for Exchange allows you to connect to Exchange servers. But that still requires you to pay inordinate amounts of money for the Exchange licenses, right?
It's completely unfair to group the majority of Republicans, the majority of whom are relatively centrist, in with the batshit insane neocons like Hatch, Coulter, O'Reilly and Hannity. It's just the nutjobs who get all the time in front of the camera because they stir up controversy.
You're entirely missing the point of the entire post. This was from the perspective of a desktop user, using the right tool for the job. For my desktop user graphics needs, The Gimp is wonderful to work with, and doesn't cost $500. However, I certainly agree, anyone involved in the graphics or advertising industries should certainly continue to use Photoshop on Windows or OS X.
Slashdot Mirror
Yes, but there's very little that actually takes advantage of it aside from emulated Playstation or Nintendo 64 games.
Last estimates I heard placed Longhorn's release in 2007, so I think they'll be the ones catching up if desktop Linux development continues at anywhere near its present pace.
I agree. Every pad that Gravis has ever made is absolute garbage. Aside from a handful of Saiteks and my trusty Thrustmaster Firestorm, I've found that the only acceptable controller is a good old Playstation controller with PSX->USB adapters, especially for PSX/SNES/Genesis emulation.
It doesn't matter that there's corporate red tape if there's a problem. I don't care what your company's policies are as an end user; I don't work there. If your red tape is preventing my product from working properly, get rid of the red tape and fix the damn problem or I, as a customer, am finding a new product.
If your software is so tangled in intertwined components that a patch for an issue this simple would conceivably break something elsewhere on your system, then your terrible product design is the concern, not the QA.
I really don't understand the need to mention Bush here.
I'd imagine they're using sessions of some kind to keep track of your IP address, since I visited the site before and the direct link from Slashdot works fine for me.
Just like that wxWindows thing, right?
That's part of the problem. The beauty of cars is that we're all driving on the same roads. Microsoft, on the other hand, likes to damage interoperability in such a way that to get from your house to 7-Eleven, you have to convert your automatic transmission to a manual transmission and connect your headlights to the top of your car, and then on the way back your car gets infected by the Internet Explorer worm of the month and ends up going the wrong way down a highway at 120 MPH.
The irony comes later in the article when, he says something to the effect of "Windows is better because Aunt Madge gets confirmation that her email was sent," because I've never seen a single email client give "sent" confirmation.
Oops.
Therein lies a fundamental part of the problem itself -- Microsoft's APIs are so entirely overcomplicated and nonintuitive that you need all kinds of API documentation. When I'm creating a simple Windows GUI application, I don't want to memorize 32 different properties of a WNDCLASS or WNDCLASSEX, and I don't want to pile half of my application's GUI code into an event loop. I think the UNIX "everything is a file" methodology combined with a self-describing signal/slot mechanism in the GUI toolkits means I shouldn't even need an API reference because I can do everything I need to with only a limited subset of standard C/C++ functions. Third-party libraries are, with few exceptions, equally simple. You can figure out how to do things in SDL, for example, by looking at the headers and function prototypes because they're self-explanatory -- no figuring out needless and cryptic DirectX COM calls and the like. If you remember what the function is called then you can easily recall how to use it. I don't get that ease-of-development on Windows systems, for certain, unless I'm using third-party toolkits like wxWindows.
I do agree, however, that documentation is much more important than having full access to the source code for a particular API.
No, you just need a much larger noose to get around the gigantic necks of us overweight Linux nerds. ;)
I am in the exact same situation. I'd been an XFce4/Gnome user ever since I switched to Linux full-time over the summer, up until a few weeks ago when I compiled the whole of KDE since I needed a good bit of it for K3B anyway.
.1 version release. GNOME's going to have a much harder time catching up because they've spent all of their time concentrating on a consistent user interface that's lacking such common sense features as "undo" in a textbox or a usable file dialog.
KDE seems even more responsive than XFce4 on this machine, and it's the primary reason why Konqueror is now my new browser, KWord is now my new word processor and Quanta Plus is now my new HTML/PHP editor. I, like my sibling poster, still use a handful of GTK+ applications (Evolution, Gaim, Pan, Nicotine, The Gimp) but they certainly do feel noticeably slower than the Qt applications on my desktop right now. I'm running a performance-tuned prelinked Gentoo system, however, so I'm not 100% entitled to say how something would perform on a "normal" binary-based Linux installation.
Of course, this is entirely without taking into effect the excellent design of Qt's derived widgets, the elegance of KDE's kioslaves, customizability of toolbars, common widgets and file dialogs, and so on.
The only thing I can say KDE is deficient in is its user interface, but this is perfectly in line with Eric Raymond's Art of Unix Programming, separating policy from mechanism. Every interface issue in KDE can get sorted out in a single
Especially considering that one of the features that was paid so much attention in the review was that "Personality" Linux emulation layer. How is that any different from the one featured in FreeBSD? Of course, FreeBSD won't need it for most things anyway, since stuff will actually compile on it.
In 1970, nearly every vehicle was rear wheel drive. Nowadays, nearly every vehicle is front wheel drive and and can handle much more safely, in addition to coming equipped with standard anti-lock brakes and, in most cases, airbags. Vehicles have crumple zones designed to reduce the risk of injury or fatality in a frontal collision.
Don't you think these should be taken into consideration as a factor in determining the speed limit?
Then you're entering a legal grey area with regards to copyright infringement, especially when you're mirroring pictures, videos, etc. without permission.
I think that would still be preferred by most site authors to DoSing, though.
I've got to agree. 100% of the 50+ CDs I've purchased in the past three years came from bands I've found on the Internet in various places.
You entirely missed the point, which was that in skid-causing rain, you should be driving well below the speed limit in the first place.
First off, if everyone on the 55 MPH freeway is driving a 75 MPH and you're moving at 20 MPH below the speed of traffic, you are yourself creating a potential traffic hazard, so you would be more likely to be involved in an accident, possibly the result of road rage, at the speed limit than at the speed of traffic.
How can someone be dead from speeding? If the road is wet and someone skids and wraps around a telephone pole at 60 miles per hour, do you really think the effect is going to be that different than at 55 miles per hour? If they're driving faster than that in the rain, the issue is that their car is going faster than it and/or the driver can safely handle in those conditions -- it has little to do with what number appears on the sign.
Again, I'd like to see some conclusive studies that speed limits actually help these situations. There's always a political or emotional spin on statistics released. How many of people killed in 85 MPH accidents were drunk? How many managed to fall asleep at the wheel? How many were talking on a cell phone? Obviously it helps somewhat but I'm curious just how much.
No. The site appears to be Slashdot, and the URL above seems to point to slashdot.org, but this is really a hoax taking advantage of an Internet Explorer exploit allowing, through JavaScript, the location in the address bar to be spoofed.
Are you kidding? Winamp5 has been in active development for months and to my knowledge they just released RC1 after a long alpha/beta cycle. Sure, Winamp3 hasn't been touched in a year -- that's because it sucks and you're unlikely to find a person on the planet who doesn't agree.
Shit, at least learn what you're talking about before you go spewing verbal diarrhea.
When you optimize code or add new features, you also introduce new bugs that weren't there before. Out with the old, in with the new.
They obviously haven't spotted the new, so it's a beta.
As already mentioned, the Ximian Connector for Exchange allows you to connect to Exchange servers. But that still requires you to pay inordinate amounts of money for the Exchange licenses, right?
Yeah, the Linux community is working on that, too.
It's completely unfair to group the majority of Republicans, the majority of whom are relatively centrist, in with the batshit insane neocons like Hatch, Coulter, O'Reilly and Hannity. It's just the nutjobs who get all the time in front of the camera because they stir up controversy.
You're entirely missing the point of the entire post. This was from the perspective of a desktop user, using the right tool for the job. For my desktop user graphics needs, The Gimp is wonderful to work with, and doesn't cost $500. However, I certainly agree, anyone involved in the graphics or advertising industries should certainly continue to use Photoshop on Windows or OS X.