Some web pages, such as photo albums, actually increase in size when converted to CSS layout. The idea that replacing table tags with equivalent div's and span's somehow reduces code bloat is a misconception.
Umm, you do know that Linux uses X11 too right? I guess you also know that the Mac OS X X11 implementation is largly based on the linux one, but has some compositing improvements which actually speed it up compared to linux.
Linux runs X11. Mac runs X11 on top of Aqua.
Do you see the difference? By the way, there is no Linux specific X11.
Just because somebody doesn't know how something works or can't work on it does *NOT* mean that they shouldn't use it.
Thats the funniest thing I've heard all week. Lets see, if I don't know how to use a gun...I should just go ahead and start shooting without instruction? Or a hypodermic needle? Or drive a car without knowing how? Or fly a plane? Or use a chainsaw?
You must live a bland life. Which would be why you argue on Slashdot, of course. Which brings up the question of why I am bothering to reply. Gah, I hate getting sucked in by trolls.
The items you chose for examples all share one property. This property is the reason why new users are taught how to use them. Can you guess what the property is? That's right. All of these, used improperly, will kill, seriously maim, or injure you or others. By comparing them to Linux, you are implicitly implying that if you use the operating system wrong, that it will grow teeth and chew your leg off or something. Is this your intent?
Call Linux a tool if you like. A more accurate description might be a commodity. You must realize something. As a techie, you see the computer very differently than the general population. They see a computer as a means to information, just like a VCR is a means to entertainment and a phone is a means to communication.
How long did it take you to learn how to play a movie in your VCR or DVD player? How long to learn how to dial the telephone? If you go to a friend's house, can you borrow his/her phone or do you need a week of lessons to use it?
This is the experience that the end user is expecting. If they are forced to learn the ins and outs of the system, they won't be interested. Just like you wouldn't be interested in a car if there were no repair stations and you had to carry your own toolset in the trunk. This of course describes car ownership in the twenties when the auto industry was still very young. People made the very same comments that you are making now. A car owner would have scoffed at the idea of a common person owning a car and not a complete repair shop.
Well, surprise surprise. Today you don't even have to know how to change your oil to drive a car. Imagine that.
Home computing is in the same situation. It is a very young industry. There are people, such as yourself, scoffing at the idea of the average person owning a computer (running Linux even, it's just the damn operating system) and not knowing the first thing of how it works.
Hell, it's already happening. You probably don't know the difference between a jmp and a longjmp. You don't have to! The guys who came before you abstracted that away and now you can program with widgets. Of course, they laughed at the idea of someone programming the computer in something other than assembly or machine code.
Apparently you got p0wned by Linux and have hard feelings. If I tried to replace a cracked block on my car without knowing how to use the right tools, and the engine fell on me, then well, I'd be embarassed too.
No, I can't say that I've ever had a bad experience with Linux. Matter of fact, I'm currently writing a kernel driver for my Synaptics LCD touchpad on my Toshiba laptop.
And no, I've never dropped an engine, though I've pulled many. It's actually pretty hard to accomplish dropping an engine on yourself, since once you disconnect the transmission all the work is done from above.
Go back to your video games and "p0wning" your buddies. This topic is talked out.
I'm way off? So your saying hardware support is distro specific and not kernel specific and that by upgrading your kernel....you would not get additional hardware support?
Install Slackware. Immediately after the install completes, play an MP3 with a graphical player. What? You can't do it? There's no GUI?!
Now install Mandrake. Immediately after the install, start X and play an MP3 with a graphical player.
What's the difference? Mandrake sets up more hardware than Slack does. Slack does -not- set up X. Clearly to an end user hardware support is distribution specific.
You or I know that the driver support is in the kernel, but to an end user, that means zilch. As it rightly should. Why the hell should my mom have to learn how to write an XF86Config file when Mandrake does it for her? For that matter, why should I? I could be writing code and getting PAID for it instead of futzing around. There is a reason that XFree86 now autoconfigures nearly everything for you.
Get real, why should everybody learn how Linux works? Can you sew your own clothes? No? Stop wearing them, dammit. Can you make your own soap, shampoo, toothpaste? No? Stop using them, dammit. Can you replace the wax seal on your toilet? No? Stop using it, dammit. Could you replace a timing belt or repair a cracked block on your car? No? Stop driving, dammit. Do you know how to calculate the exact slope required for your drains? Do you know code for how steep your stairs are allowed to be? Can you milk a cow? Can you butcher a chicken? Can you thresh wheat? Do you know why a VCR head spins? Do you know how to write a legal brief? Do you know how to calculate amortization? Hell, for that matter, can you repair the damn cathode tube in your monitor?
Just because somebody doesn't know how something works or can't work on it does *NOT* mean that they shouldn't use it. Go take a history class at your local college (assuming that you are old enough for that) and learn about an important concept in the development of civilization called specialization.
The basic idea is that civilization got to where it is by allowing groups of people to specialize in one area and NOT KNOW HOW EVERYTHING WORKS and simply trade services or goods with people who specialize in areas they needed.
That is why your lawyer doesn't know how to work on his PC. He hires you to do it. Just like you hire him instead of learning every last iota of divorce law when your wife leaves you because of your self-righteous preaching.
Now quit arguing on Slashdot. Go help a newb and make a few bucks while you're at it. Don't get pissed or make fun of them because they know less than you do. Without them, chances are that you wouldn't have a job.
This is pretty much the root of all MDIR. Hardware support is part of the kernel, not the distribution. For example, if you install Mandrake 9 and your sound card is not supported then one day kernel 2.6.x comes out with support for your card, by installing that kernel, you will have support for that card with Mandrake 9. In other words, disitrbutions support whatever hardware that the kernel they ship with supports and will continue to support more hardware as you update your kernel.
No, you're way off here. Note that he said sound *did* work until he rebooted. Clearly the issue is not that of not having kernel support, it is hardware configuration tools not setting his card up appropriately.
You are thinking WP9, aka WP Office 2000. WP8 was a motif app. Looked ugly as hell, but was one speedy motherfucker and worked great. (compared to the other word processors of the time)
I installed Debian on an old PC for my mom several years ago. Since then, the only time she's had troubles was when she had a friend of my brother's rent a room for a while. He *thought* he know Linux, and talked the root password out of her . . . . .
These guys amaze me. Just when I thought they couldn't get any worse, here they go and do it. I've got to say, even winxp is easier to use than that steaming heap of pigshit looks like. Man, 2.4 was bad, this is just terrible.
Slashdot Mirror
Only if you do it wrong.
try something like this:and styling it with:If you are messing with floats, you may have to insert something like above and/or below the img tags to keep them contained in the parent div. (Yes, I know this is a hack, hopefully it will be remedied someday.)
Also, apostrophes indicate possesive or abbreviation, not plurality.
Because proprietary developers get paid for their work, and one of the theories as to why open source developers work for free is for the notoriety.
Umm, you do know that Linux uses X11 too right? I guess you also know that the Mac OS X X11 implementation is largly based on the linux one, but has some compositing improvements which actually speed it up compared to linux.
Linux runs X11.
Mac runs X11 on top of Aqua.
Do you see the difference? By the way, there is no Linux specific X11.
Can make a tray icon on minimizing, but can't remove task bar icon.
Don't minimize it, close the window.
Just because somebody doesn't know how something works or can't work on it does *NOT* mean that they shouldn't use it.
Thats the funniest thing I've heard all week. Lets see, if I don't know how to use a gun...I should just go ahead and start shooting without instruction? Or a hypodermic needle? Or drive a car without knowing how? Or fly a plane? Or use a chainsaw?
You must live a bland life. Which would be why you argue on Slashdot, of course. Which brings up the question of why I am bothering to reply. Gah, I hate getting sucked in by trolls.
The items you chose for examples all share one property. This property is the reason why new users are taught how to use them. Can you guess what the property is? That's right. All of these, used improperly, will kill, seriously maim, or injure you or others. By comparing them to Linux, you are implicitly implying that if you use the operating system wrong, that it will grow teeth and chew your leg off or something. Is this your intent?
Call Linux a tool if you like. A more accurate description might be a commodity. You must realize something. As a techie, you see the computer very differently than the general population. They see a computer as a means to information, just like a VCR is a means to entertainment and a phone is a means to communication.
How long did it take you to learn how to play a movie in your VCR or DVD player? How long to learn how to dial the telephone? If you go to a friend's house, can you borrow his/her phone or do you need a week of lessons to use it?
This is the experience that the end user is expecting. If they are forced to learn the ins and outs of the system, they won't be interested. Just like you wouldn't be interested in a car if there were no repair stations and you had to carry your own toolset in the trunk. This of course describes car ownership in the twenties when the auto industry was still very young. People made the very same comments that you are making now. A car owner would have scoffed at the idea of a common person owning a car and not a complete repair shop.
Well, surprise surprise. Today you don't even have to know how to change your oil to drive a car. Imagine that.
Home computing is in the same situation. It is a very young industry. There are people, such as yourself, scoffing at the idea of the average person owning a computer (running Linux even, it's just the damn operating system) and not knowing the first thing of how it works.
Hell, it's already happening. You probably don't know the difference between a jmp and a longjmp. You don't have to! The guys who came before you abstracted that away and now you can program with widgets. Of course, they laughed at the idea of someone programming the computer in something other than assembly or machine code.
Apparently you got p0wned by Linux and have hard feelings. If I tried to replace a cracked block on my car without knowing how to use the right tools, and the engine fell on me, then well, I'd be embarassed too.
No, I can't say that I've ever had a bad experience with Linux. Matter of fact, I'm currently writing a kernel driver for my Synaptics LCD touchpad on my Toshiba laptop.
And no, I've never dropped an engine, though I've pulled many. It's actually pretty hard to accomplish dropping an engine on yourself, since once you disconnect the transmission all the work is done from above.
Go back to your video games and "p0wning" your buddies. This topic is talked out.
I'm way off? So your saying hardware support is distro specific and not kernel specific and that by upgrading your kernel....you would not get additional hardware support?
Install Slackware. Immediately after the install completes, play an MP3 with a graphical player. What? You can't do it? There's no GUI?!
Now install Mandrake. Immediately after the install, start X and play an MP3 with a graphical player.
What's the difference? Mandrake sets up more hardware than Slack does. Slack does -not- set up X. Clearly to an end user hardware support is distribution specific.
You or I know that the driver support is in the kernel, but to an end user, that means zilch. As it rightly should. Why the hell should my mom have to learn how to write an XF86Config file when Mandrake does it for her? For that matter, why should I? I could be writing code and getting PAID for it instead of futzing around. There is a reason that XFree86 now autoconfigures nearly everything for you.
Get real, why should everybody learn how Linux works? Can you sew your own clothes? No? Stop wearing them, dammit. Can you make your own soap, shampoo, toothpaste? No? Stop using them, dammit. Can you replace the wax seal on your toilet? No? Stop using it, dammit. Could you replace a timing belt or repair a cracked block on your car? No? Stop driving, dammit. Do you know how to calculate the exact slope required for your drains? Do you know code for how steep your stairs are allowed to be? Can you milk a cow? Can you butcher a chicken? Can you thresh wheat? Do you know why a VCR head spins? Do you know how to write a legal brief? Do you know how to calculate amortization? Hell, for that matter, can you repair the damn cathode tube in your monitor?
Just because somebody doesn't know how something works or can't work on it does *NOT* mean that they shouldn't use it. Go take a history class at your local college (assuming that you are old enough for that) and learn about an important concept in the development of civilization called specialization.
The basic idea is that civilization got to where it is by allowing groups of people to specialize in one area and NOT KNOW HOW EVERYTHING WORKS and simply trade services or goods with people who specialize in areas they needed.
That is why your lawyer doesn't know how to work on his PC. He hires you to do it. Just like you hire him instead of learning every last iota of divorce law when your wife leaves you because of your self-righteous preaching.
Now quit arguing on Slashdot. Go help a newb and make a few bucks while you're at it. Don't get pissed or make fun of them because they know less than you do. Without them, chances are that you wouldn't have a job.
This is your place in society.
This is pretty much the root of all MDIR. Hardware support is part of the kernel, not the distribution. For example, if you install Mandrake 9 and your sound card is not supported then one day kernel 2.6.x comes out with support for your card, by installing that kernel, you will have support for that card with Mandrake 9. In other words, disitrbutions support whatever hardware that the kernel they ship with supports and will continue to support more hardware as you update your kernel.
No, you're way off here. Note that he said sound *did* work until he rebooted. Clearly the issue is not that of not having kernel support, it is hardware configuration tools not setting his card up appropriately.
Read the article again before flaming. After the experiment you refer to, he also set the machine up to dual boot and had the same problems.
And why should it really matter what chipset it was? When writing about a generic topic, details of specific examples become less important.
If his new soundcard worked under 2000 but not XP, then he should downgrade to 2000 right?
Why not? It happens all the time.
According to the article, they are under different ownership now and don't have MS funding anymore . . . so I think things just might be different.
You are thinking WP9, aka WP Office 2000. WP8 was a motif app. Looked ugly as hell, but was one speedy motherfucker and worked great. (compared to the other word processors of the time)
Get used to it. Slashdot editors are retarded.
Can you post URLs in the comments for us to see?
mplayer with the proper DLLs installed opens more media files than windows media player does.
I installed Debian on an old PC for my mom several years ago. Since then, the only time she's had troubles was when she had a friend of my brother's rent a room for a while. He *thought* he know Linux, and talked the root password out of her . . . . .
The first line of the comment you are replying to:
The problem with CD printers is that:
These guys amaze me. Just when I thought they couldn't get any worse, here they go and do it. I've got to say, even winxp is easier to use than that steaming heap of pigshit looks like. Man, 2.4 was bad, this is just terrible.
Only if you want to run the extras. I'm running XFCE on my laptop (P2.2 w/ 512MB), got everything I need and it screams.
I also run XFCE on my old laptop (Cyrix 166 w/ 32MB) and it is very useable.
So tell me, replacing one cartridge every year or two, how long would it be before my injet cost more than the laser?
$500 - $50 == $450 difference
$450 / $60 == 7.5 cartridges
7.5 / 1 per year == 7.5 years.
I dunno about you, but I think that after 7 years, I'd like a new printer anyways.
Don't assume that because somebody's needs are not what yours are that they are stupid. I purchased a $150 injet and it has been well worth the money.
"prank calling" 911 just might mean somebody dies. You think that warrants "30 days in prison, tops?"
Man, I'm glad you're just an AC on slashdot and not someone whose opinion matters.
udev FAQ
Nice, Solaris is getting devfs support . . . just as it is marked deprecated in Linux 2.6
It would.
But it wouldn't know it.
The algorithm in the book used something called "rotating cleartext" to make it impossible for a computer to recognize when it had broken the code.
That is the way things work in the Open Source world. It happened with gcc (remember egcs?) and eventually the gcc project became better for it.
Maybe because it is an emerging market?
You can't cite circumstantial evidence to support an argument.
Desktop Linux use is overtaking Mac as we speak. Look it up. And regardless of market share, no company can afford to piss off 3% of its customers.
Your petty troll is laughed at.