The thing is that on guitar, your hands are working together. On piano, your hands are working separately. Even if you have melody plus bassline on guitar, both hands are cooperating to do those two things. On piano, each hand is generally working on its own separate part. I always found that aspect of piano very challenging.
I think you're right in that the initial learning curve is steeper for guitar, but I feel it levels off pretty quickly, whereas the piano curve gets pretty steep after you have the basics down...
Sorry, I should've been clearer--you made a good point, and I wanted to add that if OO.o is being localized for different countries, they could localize things like indents that make sense with common paper sizes found in that locale.
I don't know if this is close enough to be helpful, but ctl-left arrow (and ctl-right arrow) will skip "words", like in text-editing contexts. Here, "words" are contiguous non-empty cells, so if you enter text in B3, C3, and D3 (I don't know if Excel does it the other way, but in OO.o, columns are lettered), and then hit ctl-left, then enter, you'll be in B4. I agree the Excel behavior seems a lot more intuitive, though.
I'm not arguing against the change--I think it will make the UI friendlier to less experienced users. I'm arguing to expose an easy way to keep the status quo. I don't think the current close button behavior is broken, especially not for power users. It's antagonistic to that part of the user base to proclaim "No, that way of doing it is wrong; we're changing it," when it would've been pretty easy to add a configuration option to keep the current behavior (especially somewhere hidden like about:config)...
Exactly. Especially when you've got a bajillion tabs open and you click on a tab and you're not quite sure if you clicked on it so you click again but your original click brings the tab to the front (since the response was just slow from having so many tabs open) and your second click closes it. Bleargh.
Middle-click tabs to close them. We don't need no stinking close buttons cluttering up the tabs.
Do you realize that if a majority of users like Design 1 for accomplishing Feature A and a majority of users also like Design 2 for accomplishing Feature B, it's very unlikely that those two majorities perfectly overlap? Not a problem with just two features and two design decisions on each, but once you've got dozens of features, it's easy to come up with a design that no one will be happy with, even though each individual solution appeals to a "majority" of users...
And if another AI bot notices me sneaking around and starts yelling, that should bring everyone in range running too. I'm pretty sure some of the Metal Gear AIs did this.
A lot of the stealth-based FPS games do this now. I think I first saw it in No One Lives Forever, but I'd be surprised if that was really the first game to do this...
Its going to be just as much a challenge either way, so in the end it doesn't really matter to me.
So do you think an acceptable way to implement a higher level of difficulty would be to randomly discard some of your mouse clicks? To have some of your units spontaneously combust?
Part of the appeal of winning a game is facing an opponent on even terms. A somewhat spurious proposition to begin with when facing a computer, but I find it more interesting to fight "smarter" enemies rather than just "more" or "tougher".
aptitude should be used because it keeps track of automatically installed packages (required by something that you want to install). When you uninstall, aptitude will automagically uninstall the automatically installed pre-reqs, whereas apt-get will leave the pre-reqs on your system. Nice if you use GNOME but want to try KSomething, which needs ten different Klibs, and then decide that you don't like KSomething after all. aptitude will remove the libs for you on uninstall, whereas with apt, you'd have to do it yourself.
"Eternal Sunshine of the Spotless Mind" and "The Princess Bride" are among my favorite movies, so I'm certainly not opposed to sappy stuff. But that "Star Wars III" scene is absolutely the worst writing ever put on film, and I will not apologize for that opinion.
Of course, I suppose you might not realize that, since your RealDoll doesn't talk.
Hitting below the belt, are we? Fine, two can play at that game...
Of course, I suppose you might think that banter like this is normal, having learned all your sweet talking from your mom.
I was working with a team of classmates on a software engineering project last fall, a C# digital photo organizer (note that it's a way-pre-1.0 release, even though it's quite functional now). We used the exiv2 library for EXIF/IPTC metadata reading/writing. A couple of weeks before the final deliverable was due, our app started nondeterministically throwing an AccessViolation Exception (something that C# does when an unmanaged library accesses invalid memory). We traced this to the exiv2 library, and, having the code, all the way to the offending function call. I didn't have enough C++ experience to realize what was going on (a string manipulation function was being called on a raw char buffer, not a null-terminated string), but I asked the developers on their forum, and they realiezd what was wrong and offered a patch two days before the project was due.
Most of this would have been impossible with a closed-source library. We would have had to either move to another library (and there aren't many which actually write EXIF/IPTC) or stick with the ugly hack of a workaround that I came up with initially. It sort of worked, but was terrible for performance and conceptually hideous: since the invalid memory access was nondeterministic, we wrapped the whole thing in a while(true) try/catch block and just kept trying to do the metadata operation in question until it succeeded.
Slashdot Mirror
Mod parent oxymoronic.
And no, I'm not trolling. Most of IE's problems are due to its engine.
The thing is that on guitar, your hands are working together. On piano, your hands are working separately. Even if you have melody plus bassline on guitar, both hands are cooperating to do those two things. On piano, each hand is generally working on its own separate part. I always found that aspect of piano very challenging.
I think you're right in that the initial learning curve is steeper for guitar, but I feel it levels off pretty quickly, whereas the piano curve gets pretty steep after you have the basics down...
Shift-Delete cuts. Ctrl-Insert copies.
A Java long is generally two words, but a C long can be just one.
Oh wait. Never mind.
Sorry, I should've been clearer--you made a good point, and I wanted to add that if OO.o is being localized for different countries, they could localize things like indents that make sense with common paper sizes found in that locale.
I don't know if this is close enough to be helpful, but ctl-left arrow (and ctl-right arrow) will skip "words", like in text-editing contexts. Here, "words" are contiguous non-empty cells, so if you enter text in B3, C3, and D3 (I don't know if Excel does it the other way, but in OO.o, columns are lettered), and then hit ctl-left, then enter, you'll be in B4. I agree the Excel behavior seems a lot more intuitive, though.
Right, and as long as you're localizing, why not localize this aspect as well?
This is not news.
Yeah, but I'm sure the tag will be deprecated as soon as the server-side blink tag takes off.
I'm not arguing against the change--I think it will make the UI friendlier to less experienced users. I'm arguing to expose an easy way to keep the status quo. I don't think the current close button behavior is broken, especially not for power users. It's antagonistic to that part of the user base to proclaim "No, that way of doing it is wrong; we're changing it," when it would've been pretty easy to add a configuration option to keep the current behavior (especially somewhere hidden like about:config)...
Exactly. Especially when you've got a bajillion tabs open and you click on a tab and you're not quite sure if you clicked on it so you click again but your original click brings the tab to the front (since the response was just slow from having so many tabs open) and your second click closes it. Bleargh.
Middle-click tabs to close them. We don't need no stinking close buttons cluttering up the tabs.
Do you realize that if a majority of users like Design 1 for accomplishing Feature A and a majority of users also like Design 2 for accomplishing Feature B, it's very unlikely that those two majorities perfectly overlap? Not a problem with just two features and two design decisions on each, but once you've got dozens of features, it's easy to come up with a design that no one will be happy with, even though each individual solution appeals to a "majority" of users...
...think that this looks a lot like Slave I?
Huh?
It's a JavaScript issue, I think (or at least something that the JavaScript is doing) because if you turn it off, Opera renders this fine.
What are you talking about? This is great: storage and water cooling in one technology!
For all intensive purposes, he was just towing the line.
A lot of the stealth-based FPS games do this now. I think I first saw it in No One Lives Forever, but I'd be surprised if that was really the first game to do this...
So do you think an acceptable way to implement a higher level of difficulty would be to randomly discard some of your mouse clicks? To have some of your units spontaneously combust?
Part of the appeal of winning a game is facing an opponent on even terms. A somewhat spurious proposition to begin with when facing a computer, but I find it more interesting to fight "smarter" enemies rather than just "more" or "tougher".
aptitude should be used because it keeps track of automatically installed packages (required by something that you want to install). When you uninstall, aptitude will automagically uninstall the automatically installed pre-reqs, whereas apt-get will leave the pre-reqs on your system. Nice if you use GNOME but want to try KSomething, which needs ten different Klibs, and then decide that you don't like KSomething after all. aptitude will remove the libs for you on uninstall, whereas with apt, you'd have to do it yourself.
You mean you haven't heard of this (potentially NSFW)?
Hitting below the belt, are we? Fine, two can play at that game...
Of course, I suppose you might think that banter like this is normal, having learned all your sweet talking from your mom.
No movie containing that a conversation like that can ever be taken seriously.
Because if there's one thing MS Office is known for, it's the lean formats? Nice try...
I was working with a team of classmates on a software engineering project last fall, a C# digital photo organizer (note that it's a way-pre-1.0 release, even though it's quite functional now). We used the exiv2 library for EXIF/IPTC metadata reading/writing. A couple of weeks before the final deliverable was due, our app started nondeterministically throwing an AccessViolation Exception (something that C# does when an unmanaged library accesses invalid memory). We traced this to the exiv2 library, and, having the code, all the way to the offending function call. I didn't have enough C++ experience to realize what was going on (a string manipulation function was being called on a raw char buffer, not a null-terminated string), but I asked the developers on their forum, and they realiezd what was wrong and offered a patch two days before the project was due.
Most of this would have been impossible with a closed-source library. We would have had to either move to another library (and there aren't many which actually write EXIF/IPTC) or stick with the ugly hack of a workaround that I came up with initially. It sort of worked, but was terrible for performance and conceptually hideous: since the invalid memory access was nondeterministic, we wrapped the whole thing in a while(true) try/catch block and just kept trying to do the metadata operation in question until it succeeded.