Of course nobody was outside helping him. That was the point. He got lured there and went in alone. So he had to make it alone. It added pressure to the plot.
I love this trick. People point out inconsistencies in some biblical BS, and the Bible-thumpers come back and say that the inconsistencies are actually *proof* that what they are saying is The Truth. Classic.
You do realize that you shoot yourself in the foot, of course. It may well be that the Noah story is the wrong one and some other civilization has the more correct one. Or it may be that none of them are correct and whatever event they refer to was rather different from any of the legends and myths that have survived. Thanks for playing, though.
It has a way to do capslock with the shift key by double tapping. But seriously, it's really not that hard to type acronyms with the shift key unless you have some sort of physical disorder with your hands. As I said in another post, I use SQL a lot and use the shift key instead of annoying caps lock to type in the keywords. It doesn't slow down my typing and I actually feel like I have finer-grained control over when I capitalize or not since it's a matter of simply lifting my right pinky off the shift key rather than sending a finger out to caps lock to turn it off again.
It's never done that for me. I never use capslock, but I do plenty of SQL. So I'm holding down shift all the time, often without really thinking about it. Not once has any dialog popped up.
And that's significantly worse than seven layers of nested if-statements and loops? If the function is so complicated that you have to expend considerable mental effort to figure out who calls the labels, then you'd probably have the same problem with nested loops and if-statements.
Right...but the parent was talking about those situations where you don't have try-finally and OOP, like in C. In that case, goto really is the best solution. And as it stands, exceptions are actually worse than goto because where the execution flow ends up after an exception is thrown is unpredictable as it is basically a goto to a runtime-determined location outside the called function.
"actor inflects the verb" -- what does this even mean? Do you understand any of the terms you are using? I still vaguely get your point, but it's a dumb one and so is your faux-linguistic explanation of it.
It is not belief without fact. It's an area in science that hasn't been filled in yet. There's a fundamental difference in approach that you and your ilk are missing.
Get over yourself. Overlapping windows make for much more efficient use of the screen real estate. Most people rarely spend that much time manually positioning and resizing windows. It usually works fine, especially with a taskbar and alt-tab. As it turns out, tiled window management is a proper subset of overlapping window management. So with overlapping WMs, you get a tiled WM for free. The reverse is not true.
Why bother? We already have machines that are good at that: two year olds. Two year olds aren't good at doing trend analysis on a million data points, which is why we have computers. We'd gain pretty much nothing from making a silicon-based two year old. It'd probably be just as slow and would cost considerably more than a two year old.
You say that like it's a widespread problem. I can think of only one occasion in my own life where someone I knew posted something about me that I didn't want public. You can also untag yourself from these things once you find out (which is immediately, since Facebook emails you to tell you, or you could check your photos page to see if you are an in any photos).
By the way, this new tool actually could be used to more easily find out what people are posting about you, thus helping your problem even more.
I'll chime in too about not having this problem. I've used Linux since late 2004. I've used Fedora 3, 4, 6 and 12, Ubuntu (since Edgy) and Gentoo (my main Linux distro), with Ubuntu in VMs sometimes -- all these across six or seven machines. I've never had the desktop grind to a halt with heavy I/O. In fact, I was relieved that unlike Windows, the harddrive can be grinding away and I can still actually use my computer and start programs in a reasonable amount of time. So when I first started hearing about this issue recently, I was quite surprised and thought maybe it was just a localized config problem or something specific to certain people's hardware. Now that everyone on Slashdot seems to be having this problem, I can't help but wonder how I managed to be so lucky all these years. WTF is going on?
I've used a Windows XP VM on both Windows 7 as host and Linux. Works great in both, although it feels snappier in the Linux host. It's more than adequate for relatively recent hardware. It actually worked quite well back on my ThinkPad T43 (I have a T500 now) and that was without VT-x and friends.
It's like you *almost* get that there really are only a few distros, but then miss the upshot of that. The upshot is that the hundreds or thousands of other distros are irrelevant when it comes to why, e.g., Linux graphics suck or software distribution is hard. Nobody cares or pays attention to those one-off distros or super-custom distros. They are expected to maintain their own stuff. Developers target the main distros and that's about it. Since the main distros use more or less the same software, even that's not as big of a problem as it's made out to be.
MMV indeed. I've seen the same slowdown on Linux as on Windows. I don't know why. It's probably a combination of factors having to do with continually installing software (even in small bits here and there) and filesystem degradation. Either way, my experience has been that both end up slow after a while and also that if you are careful and clean up from time to time, you can keep both running relatively fast indefinitely.
My experience is that the same is now true for Linux. Running modern distros on older hardware requires using esoteric window managers and special settings, or else you have to deal with the same sluggishness and hard-drive grinding that you have to deal with on Windows. Also, the GUI is generally much less responsive than on Windows, making it feel even slower. Again, you can tweak and tweak and tweak until it is more acceptable, but will the average user do this?
How about COM? WMI? I'm not a huge Windows person, but for work I've had to do some light tasks and I've found that the various scripting and automation tools on Windows to be underrated. Granted, COM has its own history of being a big pain, but at the very least a lot of Windows apps are scriptable or programmable through it, especially MS Office.
Slashdot Mirror
He switched to Git (from nothing) a few weeks ago, according to his blog. I was surprised it took this long.
Of course nobody was outside helping him. That was the point. He got lured there and went in alone. So he had to make it alone. It added pressure to the plot.
There's no difference between GUI code and non-GUI code. What would that even mean?
"biased" is the word you are looking for.
Yes, superficially, hierarchies look like other hierarchies.
I love this trick. People point out inconsistencies in some biblical BS, and the Bible-thumpers come back and say that the inconsistencies are actually *proof* that what they are saying is The Truth. Classic. You do realize that you shoot yourself in the foot, of course. It may well be that the Noah story is the wrong one and some other civilization has the more correct one. Or it may be that none of them are correct and whatever event they refer to was rather different from any of the legends and myths that have survived. Thanks for playing, though.
It has a way to do capslock with the shift key by double tapping. But seriously, it's really not that hard to type acronyms with the shift key unless you have some sort of physical disorder with your hands. As I said in another post, I use SQL a lot and use the shift key instead of annoying caps lock to type in the keywords. It doesn't slow down my typing and I actually feel like I have finer-grained control over when I capitalize or not since it's a matter of simply lifting my right pinky off the shift key rather than sending a finger out to caps lock to turn it off again.
It's never done that for me. I never use capslock, but I do plenty of SQL. So I'm holding down shift all the time, often without really thinking about it. Not once has any dialog popped up.
And that's significantly worse than seven layers of nested if-statements and loops? If the function is so complicated that you have to expend considerable mental effort to figure out who calls the labels, then you'd probably have the same problem with nested loops and if-statements.
Right...but the parent was talking about those situations where you don't have try-finally and OOP, like in C. In that case, goto really is the best solution. And as it stands, exceptions are actually worse than goto because where the execution flow ends up after an exception is thrown is unpredictable as it is basically a goto to a runtime-determined location outside the called function.
"actor inflects the verb" -- what does this even mean? Do you understand any of the terms you are using? I still vaguely get your point, but it's a dumb one and so is your faux-linguistic explanation of it.
It is not belief without fact. It's an area in science that hasn't been filled in yet. There's a fundamental difference in approach that you and your ilk are missing.
I think they crap out of their anus like all other mammals.
Get over yourself. Overlapping windows make for much more efficient use of the screen real estate. Most people rarely spend that much time manually positioning and resizing windows. It usually works fine, especially with a taskbar and alt-tab. As it turns out, tiled window management is a proper subset of overlapping window management. So with overlapping WMs, you get a tiled WM for free. The reverse is not true.
Why bother? We already have machines that are good at that: two year olds. Two year olds aren't good at doing trend analysis on a million data points, which is why we have computers. We'd gain pretty much nothing from making a silicon-based two year old. It'd probably be just as slow and would cost considerably more than a two year old.
You say that like it's a widespread problem. I can think of only one occasion in my own life where someone I knew posted something about me that I didn't want public. You can also untag yourself from these things once you find out (which is immediately, since Facebook emails you to tell you, or you could check your photos page to see if you are an in any photos). By the way, this new tool actually could be used to more easily find out what people are posting about you, thus helping your problem even more.
I'll chime in too about not having this problem. I've used Linux since late 2004. I've used Fedora 3, 4, 6 and 12, Ubuntu (since Edgy) and Gentoo (my main Linux distro), with Ubuntu in VMs sometimes -- all these across six or seven machines. I've never had the desktop grind to a halt with heavy I/O. In fact, I was relieved that unlike Windows, the harddrive can be grinding away and I can still actually use my computer and start programs in a reasonable amount of time. So when I first started hearing about this issue recently, I was quite surprised and thought maybe it was just a localized config problem or something specific to certain people's hardware. Now that everyone on Slashdot seems to be having this problem, I can't help but wonder how I managed to be so lucky all these years. WTF is going on?
I've used a Windows XP VM on both Windows 7 as host and Linux. Works great in both, although it feels snappier in the Linux host. It's more than adequate for relatively recent hardware. It actually worked quite well back on my ThinkPad T43 (I have a T500 now) and that was without VT-x and friends.
Not any Linux that I've used. Do you mean that half-baked, barely working session-management built into KDE/GNOME?
It's like you *almost* get that there really are only a few distros, but then miss the upshot of that. The upshot is that the hundreds or thousands of other distros are irrelevant when it comes to why, e.g., Linux graphics suck or software distribution is hard. Nobody cares or pays attention to those one-off distros or super-custom distros. They are expected to maintain their own stuff. Developers target the main distros and that's about it. Since the main distros use more or less the same software, even that's not as big of a problem as it's made out to be.
Windows has done that for years, if you are referring to suspend-to-disk.
What does freedom of speech have to do with this?
MMV indeed. I've seen the same slowdown on Linux as on Windows. I don't know why. It's probably a combination of factors having to do with continually installing software (even in small bits here and there) and filesystem degradation. Either way, my experience has been that both end up slow after a while and also that if you are careful and clean up from time to time, you can keep both running relatively fast indefinitely.
My experience is that the same is now true for Linux. Running modern distros on older hardware requires using esoteric window managers and special settings, or else you have to deal with the same sluggishness and hard-drive grinding that you have to deal with on Windows. Also, the GUI is generally much less responsive than on Windows, making it feel even slower. Again, you can tweak and tweak and tweak until it is more acceptable, but will the average user do this?
How about COM? WMI? I'm not a huge Windows person, but for work I've had to do some light tasks and I've found that the various scripting and automation tools on Windows to be underrated. Granted, COM has its own history of being a big pain, but at the very least a lot of Windows apps are scriptable or programmable through it, especially MS Office.