Actually, he missed out on one UI bug in Evolution that makes me laugh. I wish I had a screenshot, but on fairly regular occasion, Evolution gives me an error message with a label saying, "Error: Success." Gets me every time:)
Hiding the mouse pointer completely is usually a pretty stupid idea. It's quicker for the user to move the pointer out of the way than it is to find a hidden pointer when they need to use the mouse again...
This is something I've thought, as well. User interface enthusiasts always refer to widgets directly on the screen border (*especially* in corners) as having near-infinite size. And rightly so--all you have to do is flick the mouse in that direction with enough magnitude, and you can click blindly.
But shouldn't this be an argument against having the mouse pointer disappear? If it's in the way, all you have to do is flick the mouse to any corner of the screen (the easiest thing to do, in terms of user interfaces), and it's not a problem. On the other hand, if your mouse cursor disappears when typing, it's always been difficult for me to remember where the cursor was. This results in a net loss of time as I have to then rediscover its location to proceed with my next task.
Corporations are legally obliged (to protect shareholders) not to be nice and to take advantage of every tax loopholes and squeeze every last penny they can.
Bullshit. Corporations are legally obliged to make money for their shareholders. Nothing is ever said about how that money is made. If Larry and Sergiy think that the best way to accomplish this goal in the long-term is to have happy customers, give Google a sterling reputation, and give back to the community, then that fulfills the requirement.
Unfortunately, the numbers don't always work out that evenly. Even if you make half the units, you'd still probably make the same number of models, which would require similar numbers of designers. Since I presume they would be more expensive than people manufacturing, you're probably going to have higher costs.
I agree wholeheartedly with your comment on Design by Contract. So much so, in fact, that I'm writing a DBC processor for.NET languages. Put in contact through attributes, and the DBC parser will go in and insert the correct assertions and checks for you.
Sorry, but this is an extremely naive way of coding, in my opinion. Errors occur for a reason; if you don't do something about their existence, you're likely to start experiencing unexpected problems. Crash early crash often isn't a joke; it's far better to die when you can gracefully than it is to ignore all errors and crash losing data.
...which is exactly why LFS is pointless. Let the distro maintainers do this, not the end user. Should it be cleaned up for the distro maintainer? Sure. But the complexity of the build system has nothing to do with end users.
I agree. I can't answer what mechanism would do this, but I can assume that the pressure caused by external oxygen would inhibit even distribution, whereas a complete lack of external oxygen might encourage the balloon's shape to more easily reflect the imperfections in the latex.
Re:We know quarks, but not this...
on
Bang But No Splash
·
· Score: 2, Insightful
This sounds like something that could be easily explained. When you blow into a balloon, the air inside does not stretch the latex evenly in all directions. By evenly, I mean that the latex is thicker and thinner in some areas than others due to imperfections in manufacturing. When you blow up the balloon, these imperfections aren't accounted for and there are likely to be a few "weakest" areas with some stronger ones around.
In theory, removing the surrounding air would eliminate or significantly reduce the opposition to this "uneven" (when considering the imperfect makeup of the balloon itself) distribution, and allow the air inside the balloon to distribute itself so that all points on the balloon's surface experience the same tension to strength ratio. Once a certain threshold is exceeded, they would then all exceed it at the same time, and result in many many tears, opposed to just a few.
No, commas should be used where is grammatically appropriate. The two overlap a lot (and rightly so, since that's where the comma originated from), but it's not strictly true any more. Specifically, there are many times where you would take a small pause in normal speech but where it would be inappropriate to insert a comma.
And that was sort of the point of that sentence. Commas themselves are "optional" in many circumstances to prevent their overuse. It's still grammatically correct to write a sentence like that, but I know I consider it abusive.
I cannot understand why Apple is sodding around with Motorola on this. They should have partnered with Nokia.
I couldn't agree more. My Nokia ended up breaking after about four years, and I ended up getting a Motorola. I've regretted every minute of it. Whereas Nokia seems to have a smiliar mindset to that of Apple (a focus on usability), my Motorola is the most unusable piece of crap I've ever had the displeasure of dealing with.
I can store something like five minutes of voice on the cell phone, but I'll be damned if it runs out of space with twenty text messages. You can't turn the volume off without making more noise. Even when the volume is off, some buttons still make noise (and are conveniently on the outside of the phone, so it can beep in your pocket) making the vibrate feature nearly useless. The "Accept" and "Cancel" buttons are on different sides at different times. The dial and hangup buttons are permanently juxtaposed. The "Memory Meter" shows you a representation of how much memory is left on the phone, but you have no way of telling whether or not a full bar means it's full of space or filled up. Assigning a one-touch dial number to contacts is a pain in the ass. The power connector features two microscopic hooks which are so easy to break it's unbelievable. The phone takes five minutes after "booting" before I can place a call, view my contact list, check messages, etc. Switching the phone to "Silent" or "Vibrate" does not necessarily turn the volume off.
I swear to god if I ever meet the man who designed this worthless piece of shit, I am going to bludgeon him with a tractor.
Commas, even when, grammatically speaking, used correctly, can still, in many cases, inhibit reading, in ways that, in my opinion, no other punctuation can.
So what you're saying is that the placebo effect is, in effect, a placebo? That the placebo effect only works because we believe in the placebo effect?
Well, I'm sure Debian has their reasons, but I suspect they're suffering due to some of their fans dropping it for other distros. Late releases, stupid politics and aged packages isn't doing this distro any justice.
Debian doesn't suffer from lack of users by any stretch of the imagination. Contrary to what you see on Slashdot, most Debian users understand that the delays going into Sarge and the heated discussions about GFDL licenses are painful but necessary.
Slashdot Mirror
rm -Rf / as nonroot will make you give a sigh of relief. As root will be your nightmare.
I dare you to try this. Dare.
Note: you may wish to back your home directory up first. Preferably somewhere not under /, or using with someone else's permissions.
Actually, he missed out on one UI bug in Evolution that makes me laugh. I wish I had a screenshot, but on fairly regular occasion, Evolution gives me an error message with a label saying, "Error: Success." Gets me every time :)
Hiding the mouse pointer completely is usually a pretty stupid idea. It's quicker for the user to move the pointer out of the way than it is to find a hidden pointer when they need to use the mouse again...
This is something I've thought, as well. User interface enthusiasts always refer to widgets directly on the screen border (*especially* in corners) as having near-infinite size. And rightly so--all you have to do is flick the mouse in that direction with enough magnitude, and you can click blindly.
But shouldn't this be an argument against having the mouse pointer disappear? If it's in the way, all you have to do is flick the mouse to any corner of the screen (the easiest thing to do, in terms of user interfaces), and it's not a problem. On the other hand, if your mouse cursor disappears when typing, it's always been difficult for me to remember where the cursor was. This results in a net loss of time as I have to then rediscover its location to proceed with my next task.
Modern computers already match us in terms of raw power. However, our operating system is *way* cooler, and we get better peripherals :)
Corporations are legally obliged (to protect shareholders) not to be nice and to take advantage of every tax loopholes and squeeze every last penny they can.
Bullshit. Corporations are legally obliged to make money for their shareholders. Nothing is ever said about how that money is made. If Larry and Sergiy think that the best way to accomplish this goal in the long-term is to have happy customers, give Google a sterling reputation, and give back to the community, then that fulfills the requirement.
Unfortunately, the numbers don't always work out that evenly. Even if you make half the units, you'd still probably make the same number of models, which would require similar numbers of designers. Since I presume they would be more expensive than people manufacturing, you're probably going to have higher costs.
It would be funny if you replied to this message saying, "Oops, I meant 12."
Spelt is a word. Check the dictionary.
If someone spelt it wrong, how would we know?
I agree wholeheartedly with your comment on Design by Contract. So much so, in fact, that I'm writing a DBC processor for .NET languages. Put in contact through attributes, and the DBC parser will go in and insert the correct assertions and checks for you.
Sorry, but this is an extremely naive way of coding, in my opinion. Errors occur for a reason; if you don't do something about their existence, you're likely to start experiencing unexpected problems. Crash early crash often isn't a joke; it's far better to die when you can gracefully than it is to ignore all errors and crash losing data.
...which is exactly why LFS is pointless. Let the distro maintainers do this, not the end user. Should it be cleaned up for the distro maintainer? Sure. But the complexity of the build system has nothing to do with end users.
I wasn't correcting his spelling :(
I agree. I can't answer what mechanism would do this, but I can assume that the pressure caused by external oxygen would inhibit even distribution, whereas a complete lack of external oxygen might encourage the balloon's shape to more easily reflect the imperfections in the latex.
This sounds like something that could be easily explained. When you blow into a balloon, the air inside does not stretch the latex evenly in all directions. By evenly, I mean that the latex is thicker and thinner in some areas than others due to imperfections in manufacturing. When you blow up the balloon, these imperfections aren't accounted for and there are likely to be a few "weakest" areas with some stronger ones around.
In theory, removing the surrounding air would eliminate or significantly reduce the opposition to this "uneven" (when considering the imperfect makeup of the balloon itself) distribution, and allow the air inside the balloon to distribute itself so that all points on the balloon's surface experience the same tension to strength ratio. Once a certain threshold is exceeded, they would then all exceed it at the same time, and result in many many tears, opposed to just a few.
I don't know about you, but I'm pretty sure most of us know the properties of atmosphere in a vaccuum
And by the way, that sentence is perfectly grammatically correct. If not, as I mentioned before, abusive :)
No, commas should be used where is grammatically appropriate. The two overlap a lot (and rightly so, since that's where the comma originated from), but it's not strictly true any more. Specifically, there are many times where you would take a small pause in normal speech but where it would be inappropriate to insert a comma.
And that was sort of the point of that sentence. Commas themselves are "optional" in many circumstances to prevent their overuse. It's still grammatically correct to write a sentence like that, but I know I consider it abusive.
I cannot understand why Apple is sodding around with Motorola on this. They should have partnered with Nokia.
I couldn't agree more. My Nokia ended up breaking after about four years, and I ended up getting a Motorola. I've regretted every minute of it. Whereas Nokia seems to have a smiliar mindset to that of Apple (a focus on usability), my Motorola is the most unusable piece of crap I've ever had the displeasure of dealing with.
I can store something like five minutes of voice on the cell phone, but I'll be damned if it runs out of space with twenty text messages. You can't turn the volume off without making more noise. Even when the volume is off, some buttons still make noise (and are conveniently on the outside of the phone, so it can beep in your pocket) making the vibrate feature nearly useless. The "Accept" and "Cancel" buttons are on different sides at different times. The dial and hangup buttons are permanently juxtaposed. The "Memory Meter" shows you a representation of how much memory is left on the phone, but you have no way of telling whether or not a full bar means it's full of space or filled up. Assigning a one-touch dial number to contacts is a pain in the ass. The power connector features two microscopic hooks which are so easy to break it's unbelievable. The phone takes five minutes after "booting" before I can place a call, view my contact list, check messages, etc. Switching the phone to "Silent" or "Vibrate" does not necessarily turn the volume off.
I swear to god if I ever meet the man who designed this worthless piece of shit, I am going to bludgeon him with a tractor.
Commas, even when, grammatically speaking, used correctly, can still, in many cases, inhibit reading, in ways that, in my opinion, no other punctuation can.
So what you're saying is that the placebo effect is, in effect, a placebo? That the placebo effect only works because we believe in the placebo effect?
That hurts even my head.
Actually, if your computer really did type "n" when you hit "m", your explanation would have been reversed :)
Probably my health & car insurance companies too. It'd be great if I could save 15% on my car insurance.
You could always just call Geico.
Damn, I never thought I'd life to see the day where somebody mentions that a KDE app's user interface "is much cleaner and easier to navigate".
Well, I'm sure Debian has their reasons, but I suspect they're suffering due to some of their fans dropping it for other distros. Late releases, stupid politics and aged packages isn't doing this distro any justice.
Debian doesn't suffer from lack of users by any stretch of the imagination. Contrary to what you see on Slashdot, most Debian users understand that the delays going into Sarge and the heated discussions about GFDL licenses are painful but necessary.