Funny how it only really works that way on Linux and OSX, in my experience.
Uh, when did you start using Linux? When I first installed Mandrake three or four years ago, the sound didn't work and I couldn't connect to the internet. Later, I got to experience the joys of setting up a printer. Things only got easy on Linux within the past year or so with the advent of HAL and Project Utopia. A year ago, someone wanted me to print out a file for them off a USB memory stick. I plugged it in. Nothing happened. I tried to Google for how to use USB memory in Linux, but after about two minutes, she said "Never mind, I can get someone else to print it." That's right: Linux cost me thanks-for-printing-my-essay-for-me sex. Today I can plug in my USB drive and it will mount itself and open a window displaying its contents. If Dvorak's facts are wrong, they're only a few months wrong.
That is great, but until grandma can turn on a computer running linux and NDisWrapper automagically realizes the device isn't support by linux and goes out and finds the windows driver Dvorak's point stands.
Grandma's computer either comes with the device set up, or the device comes with instructions and a driver CD to help her set it up. Linux can't compete with that unless hardware vendors ship their devices with instructions on how to install the device in Linux. That's not going to happen because of low market share and the diversity of desktop Linux. You'll need to provide as many installation instructions as there are distros. This brings us back to your point: Linux distros have to provide a way to install basically everything automatically to compete with the Windows world. What will that take? Something like NDISWrapper, except for all device drivers. In other words, porting the Windows driver stack to Linux, which is what Dvorak is suggesting in the first place. The sad thing is that this will probably be done, not by Microsoft, but by the open source community. Whoever does it will be flamed, and rightfully so: it'll be the end of open source drivers on Linux.
The parent is right. Neupogen is used to increase the production of white blood cells. That would increase the number of T-cell precursors and B-cells in the blood. The B-cells are already mature, but the T-cell precursors mature further in the thymus. They're still not stem cells per se. It'd be pretty complicated to separate the precursor cells from the mature cells that would centrifuge out along with them, so I'm pretty sure they just wanted to transfer white blood cells.
1. Mono doesn't use Wine for it's Windows.Forms implementation anymore.
2. Most open source applications based on Mono use GTK#, which is completely independent from anything Microsoft. Worries about the.NET implementation are the only ones that have merit, because the rest is basically a C# compiler and GTK bindings. All the Gnome applications you see that are based on Mono can't be affected by Microsoft.
It's ok to suggest alternatives and all, but if you're going to criticize a project, at least learn something about it. Novell is basing future versions of NetMail on Hula. It's not so much abandoning as it is getting people to help them work on a project for free. Read the FAQ.
From the Hula FAQ: "Novell has indicated that the Hula codebase will form the basis for future versions of NetMail or a NetMail successor product." They're not selling Hula. They're selling NetMail. It's a Netscape-esque kind of thing.
Don't the updates come from updates.mozilla.org? If an extension turns sour, they could just take it down. Some people would surely get it before that would happen. I wonder if they have a way to remotely uninstall extenstions...
A lot of posts so far have been criticisms from people who clearly haven't used GNOME before. How about trying the software out first, then pointing out legitimate problems with it rather than complaining about little things you've picked out of a screenshot?
I don't have the first fucking idea what that's supposed to mean.
And you shouldn't if you don't use GNOME, because even if you did use it, you're not supposed to need to select a different backend for GStreamer. Some distros don't even include it in the menu because its advanced configuration that most users will never need. It's purpose is to allow you to use a different sound server, like KDE's artsd. If you want to know more about it, google some of the terms you don't know about. I'm not trying to to belittle you, but you're coming out of nowhere trying to put down the design of things you've never even used. It shouldn't be a surprise that you don't know the purpose of some things.
Volume isn't related to sound controls? I think you'll find you're mistaken.
No, that's not what I said. Volume isn't related to the Multimedia Systems Selector. It's named that because that's exactly what it is. Just because you don't understand it doesn't mean it should have a volume control slapped on it. Like I said before, it's a window that you would never see unless you typed the command in the command line since it's not in the menu.
What's a panel, and what's an applet?
Panels are the bars at the top and bottom of the screen. they hold programs called applets. Look in the screenshot you were referring to. See the little speaker icon at the top right? That's what any user trying to change the volume would go to, not the Multimedia Systems Selector, because, for the third and final time, it's an advanced configuration program not meant for most users to deal with.
Pop in one of the many live CDs that have been posted on Slashdot over the past week or so and try out GNOME. I think you'll be pleasantly surprised by how much easier it is to use than you think. There's still a lot of room for improvement though, and it gets better with every release. I hear 2.10 has a new volume control applet.
This is what happens when people who don't use the software in question try to badmouth it. The program you're referring to lets you pick the backend that GStreamer outputs audio and video (aka multimedia) to. It doesn't have a volume control on it because that isn't related to the function of the program. You contol the volume through the -- gasp! -- volume control applet in the panel. Just like in Windows and OS X.
Yet, Microsoft doesn't patch Windows 2000 every time a new laptop comes out, but it always works.
Laptop manufacturers make sure their computers work with Windows 2000, not vice versa. Their viability depends on it, but Microsoft's doesn't. When someone buys a laptop and the shipped version of Windows doesn't play well with the hardware, they'll blame it on the laptop, not Windows.
There is no way to fix this except by having two completely separate sets of documentation.
Or man pages could just be written well. If they started off by explaing usage in the most common use cases, one page would be fine for everyone. The tar man page in Debian does a nice job of this by showing examples right after the description, then showing what each flag does afterwards. If I come to the page trying to extract a tar.gz, I just skim through the man page and come across this:
tar -xvvzf foo.tar.gz
extract gzipped foo.tar.gz
If they were all like this, there'd be less of a problem. All it takes is an email to the maintainer with how you think they should change the man page.
It's a common misconception. Ubuntu has all the packages that Debian does, just with more recent versions. The assurance that people get from Debian stable is that the packages won't change. Ubuntu releases are the same way, except they don't take three years. Each release is supported for 18 months, which is terribly long, but upgrading once every 18 months isn't too often for most people.
Slashdot Mirror
Funny how it only really works that way on Linux and OSX, in my experience.
Uh, when did you start using Linux? When I first installed Mandrake three or four years ago, the sound didn't work and I couldn't connect to the internet. Later, I got to experience the joys of setting up a printer. Things only got easy on Linux within the past year or so with the advent of HAL and Project Utopia. A year ago, someone wanted me to print out a file for them off a USB memory stick. I plugged it in. Nothing happened. I tried to Google for how to use USB memory in Linux, but after about two minutes, she said "Never mind, I can get someone else to print it." That's right: Linux cost me thanks-for-printing-my-essay-for-me sex. Today I can plug in my USB drive and it will mount itself and open a window displaying its contents. If Dvorak's facts are wrong, they're only a few months wrong.
The rest of the article is still bullshit.
That is great, but until grandma can turn on a computer running linux and NDisWrapper automagically realizes the device isn't support by linux and goes out and finds the windows driver Dvorak's point stands.
Grandma's computer either comes with the device set up, or the device comes with instructions and a driver CD to help her set it up. Linux can't compete with that unless hardware vendors ship their devices with instructions on how to install the device in Linux. That's not going to happen because of low market share and the diversity of desktop Linux. You'll need to provide as many installation instructions as there are distros. This brings us back to your point: Linux distros have to provide a way to install basically everything automatically to compete with the Windows world. What will that take? Something like NDISWrapper, except for all device drivers. In other words, porting the Windows driver stack to Linux, which is what Dvorak is suggesting in the first place. The sad thing is that this will probably be done, not by Microsoft, but by the open source community. Whoever does it will be flamed, and rightfully so: it'll be the end of open source drivers on Linux.
NetworkManager or netapplet might help with that.
The parent is right. Neupogen is used to increase the production of white blood cells. That would increase the number of T-cell precursors and B-cells in the blood. The B-cells are already mature, but the T-cell precursors mature further in the thymus. They're still not stem cells per se. It'd be pretty complicated to separate the precursor cells from the mature cells that would centrifuge out along with them, so I'm pretty sure they just wanted to transfer white blood cells.
They tried to buy title insurance, but got scammed at tilteinsurance.com. Happens to the best of us.
[hand wave]
This is not the movie you are looking for. But you will watch it anyway.
how in hell could you cheat at pong?!
So I'm the only one who used an aimbot in Pong?
Or is it another case of a dot.com investor not really understanding what they're buying into?
It makes me cry whenever I hear people say this. I dry the tears with my Webvan stock certificates.
Timothy is the internet's TBS.
1. Mono doesn't use Wine for it's Windows.Forms implementation anymore. .NET implementation are the only ones that have merit, because the rest is basically a C# compiler and GTK bindings. All the Gnome applications you see that are based on Mono can't be affected by Microsoft.
2. Most open source applications based on Mono use GTK#, which is completely independent from anything Microsoft. Worries about the
It's ok to suggest alternatives and all, but if you're going to criticize a project, at least learn something about it. Novell is basing future versions of NetMail on Hula. It's not so much abandoning as it is getting people to help them work on a project for free. Read the FAQ.
From the Hula FAQ: "Novell has indicated that the Hula codebase will form the basis for future versions of NetMail or a NetMail successor product." They're not selling Hula. They're selling NetMail. It's a Netscape-esque kind of thing.
I'll have you know that selling panties is a cutthroat industry. Stay the fuck away. Or else.
They should probably add that the vendor is named after a head covering that reflects light around 700 nm.
Yay! America bashing!
Team Anti-America: America?! Fuck no!
But wouldn't they want to know how to assemble an atomic bomb?
Don't the updates come from updates.mozilla.org? If an extension turns sour, they could just take it down. Some people would surely get it before that would happen. I wonder if they have a way to remotely uninstall extenstions...
A lot of posts so far have been criticisms from people who clearly haven't used GNOME before. How about trying the software out first, then pointing out legitimate problems with it rather than complaining about little things you've picked out of a screenshot?
I don't have the first fucking idea what that's supposed to mean.
And you shouldn't if you don't use GNOME, because even if you did use it, you're not supposed to need to select a different backend for GStreamer. Some distros don't even include it in the menu because its advanced configuration that most users will never need. It's purpose is to allow you to use a different sound server, like KDE's artsd. If you want to know more about it, google some of the terms you don't know about. I'm not trying to to belittle you, but you're coming out of nowhere trying to put down the design of things you've never even used. It shouldn't be a surprise that you don't know the purpose of some things.
Volume isn't related to sound controls? I think you'll find you're mistaken.
No, that's not what I said. Volume isn't related to the Multimedia Systems Selector. It's named that because that's exactly what it is. Just because you don't understand it doesn't mean it should have a volume control slapped on it. Like I said before, it's a window that you would never see unless you typed the command in the command line since it's not in the menu.
What's a panel, and what's an applet?
Panels are the bars at the top and bottom of the screen. they hold programs called applets. Look in the screenshot you were referring to. See the little speaker icon at the top right? That's what any user trying to change the volume would go to, not the Multimedia Systems Selector, because, for the third and final time, it's an advanced configuration program not meant for most users to deal with.
Pop in one of the many live CDs that have been posted on Slashdot over the past week or so and try out GNOME. I think you'll be pleasantly surprised by how much easier it is to use than you think. There's still a lot of room for improvement though, and it gets better with every release. I hear 2.10 has a new volume control applet.
sure there is, they could read your mind and adjust volume levels perfectly to suit your desire...
That's slated for 3.0.
This is what happens when people who don't use the software in question try to badmouth it. The program you're referring to lets you pick the backend that GStreamer outputs audio and video (aka multimedia) to. It doesn't have a volume control on it because that isn't related to the function of the program. You contol the volume through the -- gasp! -- volume control applet in the panel. Just like in Windows and OS X.
Yet, Microsoft doesn't patch Windows 2000 every time a new laptop comes out, but it always works.
Laptop manufacturers make sure their computers work with Windows 2000, not vice versa. Their viability depends on it, but Microsoft's doesn't. When someone buys a laptop and the shipped version of Windows doesn't play well with the hardware, they'll blame it on the laptop, not Windows.
If Microsoft cared about security issues in third party programs, their list of security announcements would be a lot longer than they are now.
There is no way to fix this except by having two completely separate sets of documentation.
Or man pages could just be written well. If they started off by explaing usage in the most common use cases, one page would be fine for everyone. The tar man page in Debian does a nice job of this by showing examples right after the description, then showing what each flag does afterwards. If I come to the page trying to extract a tar.gz, I just skim through the man page and come across this:
tar -xvvzf foo.tar.gz
extract gzipped foo.tar.gz
If they were all like this, there'd be less of a problem. All it takes is an email to the maintainer with how you think they should change the man page.
It's a common misconception. Ubuntu has all the packages that Debian does, just with more recent versions. The assurance that people get from Debian stable is that the packages won't change. Ubuntu releases are the same way, except they don't take three years. Each release is supported for 18 months, which is terribly long, but upgrading once every 18 months isn't too often for most people.