Yes but, assuming I'm following this, very little real desktop stress is created in a neat little TTY.
For most desktop users really high load is caused by X programs that don't run in a tty. (run ps -A and see how may ?'s are in the second column)
The real solution to better desktop performance is
A)to make X a little less network transparent so it will reliably report PIDs to the window manager (at least for apps running locally, which for most people is all of them, and moreover even if there are some running on a foreign host, they won't be the ones to bring the local machine to its knees). ATM you have to rely on the _NET_WM_PID atom which is entirely voluntary, and some major--both in terms of users and memory footprint--programs don't set it (OOo).
And B) make it so that users can renice their own apps to lower values, as long as it follows some policy, e.g., a normal user can't set his processes' nice value below 0. There is no reason I can think of for a blind only-root-can-ever-lower-the-nice-value-on-any-process policy.
If we did these two things, then the window manger--which actually has the information about what window and process needs to be responsive (i.e., the one with focus) and which don't (i.e., ones that are unmapped/minimized/on-other-desktops)--could dynamically alter scheduling priority in an intelligent way instead of the kernel trying to guess what is interactive and needs low latency and what isn't.
I thought he was trying to say, 'The smallest fonts in the wold exist.'
Of course I was left wondering why anyone would need to say this, unless of course he was simply expressing, in an extremely round-about way, that some font exists.
Only slightly on topic, but I split my side when I read this at wikipedia:
A hunger strike cannot be effective if the fact that it is being undertaken is not publicized so as to be known by the people who are to be impressed, concerned or embarrassed by it.
Do you understand how laws get passed in the US? The legislature is made up of two chambers: the House and the Senate; a Bill must pass in each of them and then it has to be signed by the president.
Thus controlling either the House, or the Senate, or the White House is enough to stop a Bill from becoming law. In fact, you only need 2/3rds to stop a bill on procedure in the senate.
If the Republicans act as a whole, they can stop every last bill in Congress right where it is (not only do they control the House, they also have more than enough in the Senate to fillibuster.)
The only reason republicans need to do what the Democrats want is if the Republicans are trying to get something done on their own and thus need to gain some Democratic support.
Unless of course what you are calling crap is the whole US system of legislating.
Obama has made it legal for him to assassinate US citizens with nothing more than an accusation and the citizen is given no opportunity for due process. It's a fact. It was first reported by a couple of liberal reporters.
My thoughts exactly: Great, another resource-hogging annoyance." What if I lean forward because I'm trying to see something small in the corner?
Rule no. 1 of UI design: When in doubt make the interface stupid but predictable. Smart systems that guess wrong even 2% of the time are just frustrations.
But by the time you start doubting the NIC driver (from the manufacturer), haven't you pretty much worked yourself into a corner. I mean, there is nothing (that I can tell) that would keep the manufacturer from just sticking the nasty bits into the chip itself, if he were set on hurting you). At some point you have to just trust the company.
You are right. Using sound delay would be retarded and require several mics.
Oh and it's in the 3rd paragraph of TFA:
“What we're doing is using the existing microphone to detect sounds - the different areas of a phone have a unique sound signature,” said Mike Bradley, founder of TouchDevice.
I have copious photos and am taking as much HD video as I can without being a jerk, so images and sounds are taken care of (and backed up securely).
I'm not going to go to the extreme of the parent, but it sounds like you are spending a lot of time trying frantically to freeze your wife forever. I'v never been through something like this, but maybe everyone would get more out of it if you just--i don't know--forget that she is dying and spend as much natural time with her as you can. Then you (and your kids) will have memories of Mom as she was when she was happy with her family, rather than hours of video with an elephant in the room.
Grand parent.
Your post is this post's parent.
The one you were replying to was this post's GP (your parent).
The one before that was this post's Great grand parent, (GGP). Etc.
I read an article not long ago (sorry, can't find a link) basically saying that artists think of their work as part of their soul. This doesn't mean artists never give away work, and it doesn't meant that programmer's think of their work as worthless, but it does seem like there is a tendency for artists to elevate the value of their work to the invaluable-and-irreplaceable end of the scale.
I suspect there are a few other things that compound the problem, and make it easier for programmers to cooperate. For example, most programers think of their programs as tools. As long as everyone agrees on what the tool is doing (i.e., what features fit) it is pretty easy for other people to contribute. If your patch fixes a bug--and doesn't introduce regressions--then it's pretty cut and dry: it makes the tool a better tool for everyone and makes the dev's job easier; if it implements a feature that the lead developer wants but hasn't had time to write, ditto. Obviously there are gray areas, where the bugfix is a dirty hack or the dev doesn't want the feature, but it is generally clear-ish, and even the grey areas can be ironed out if the team is communicating (e.g., "I'm not taking this hack for x, y, z reasons. . . do it right and come back").
As you noted, artwork doesn't have such clear lines about what is and isn't an improvement.
Slashdot Mirror
what does COW have to do with knowing your data got committed?
Yes but, assuming I'm following this, very little real desktop stress is created in a neat little TTY.
For most desktop users really high load is caused by X programs that don't run in a tty. (run ps -A and see how may ?'s are in the second column)
The real solution to better desktop performance is
A)to make X a little less network transparent so it will reliably report PIDs to the window manager (at least for apps running locally, which for most people is all of them, and moreover even if there are some running on a foreign host, they won't be the ones to bring the local machine to its knees). ATM you have to rely on the _NET_WM_PID atom which is entirely voluntary, and some major--both in terms of users and memory footprint--programs don't set it (OOo).
And B) make it so that users can renice their own apps to lower values, as long as it follows some policy, e.g., a normal user can't set his processes' nice value below 0. There is no reason I can think of for a blind only-root-can-ever-lower-the-nice-value-on-any-process policy.
If we did these two things, then the window manger--which actually has the information about what window and process needs to be responsive (i.e., the one with focus) and which don't (i.e., ones that are unmapped/minimized/on-other-desktops)--could dynamically alter scheduling priority in an intelligent way instead of the kernel trying to guess what is interactive and needs low latency and what isn't.
it's the danged preamble to the danged consitution
Is it?
really?
I thought he was trying to say, 'The smallest fonts in the wold exist.'
Of course I was left wondering why anyone would need to say this, unless of course he was simply expressing, in an extremely round-about way, that some font exists.
A hunger strike cannot be effective if the fact that it is being undertaken is not publicized so as to be known by the people who are to be impressed, concerned or embarrassed by it.
Do you understand how laws get passed in the US? The legislature is made up of two chambers: the House and the Senate; a Bill must pass in each of them and then it has to be signed by the president.
Thus controlling either the House, or the Senate, or the White House is enough to stop a Bill from becoming law. In fact, you only need 2/3rds to stop a bill on procedure in the senate.
If the Republicans act as a whole, they can stop every last bill in Congress right where it is (not only do they control the House, they also have more than enough in the Senate to fillibuster.)
The only reason republicans need to do what the Democrats want is if the Republicans are trying to get something done on their own and thus need to gain some Democratic support.
Unless of course what you are calling crap is the whole US system of legislating.
Obama has made it legal for him to assassinate US citizens with nothing more than an accusation and the citizen is given no opportunity for due process. It's a fact. It was first reported by a couple of liberal reporters.
citation?
Interesting, I always thought 'triangulation' referred to tirlateration.
Isn't that basically how all the TOS's on major sites work? By using this site/service you agree to the following.
even how to pronounce her name
Just like the first queen of Carthage.
Of course this may have been hyperbole on her part.
hyperbole or hyperbola?
let me try: l0ve4eva
Do you see *'s?
It seems like that would make it easy to get lost, fractals have an odd way of looking similar at various magnifications.
I always thought they could be odd but I had no idea liberals smoke hippies.
My thoughts exactly: Great, another resource-hogging annoyance." What if I lean forward because I'm trying to see something small in the corner?
Rule no. 1 of UI design: When in doubt make the interface stupid but predictable. Smart systems that guess wrong even 2% of the time are just frustrations.
Apparently the title is a reference to Newton, not Russell and Whitehead.
I know, I was disappointed too.
But by the time you start doubting the NIC driver (from the manufacturer), haven't you pretty much worked yourself into a corner. I mean, there is nothing (that I can tell) that would keep the manufacturer from just sticking the nasty bits into the chip itself, if he were set on hurting you). At some point you have to just trust the company.
Okay, take back the last bit. I need to pay more attention to context.
Oh and it's in the 3rd paragraph of TFA:
“What we're doing is using the existing microphone to detect sounds - the different areas of a phone have a unique sound signature,” said Mike Bradley, founder of TouchDevice.
GP is talking out his ass.
I have copious photos and am taking as much HD video as I can without being a jerk, so images and sounds are taken care of (and backed up securely).
I'm not going to go to the extreme of the parent, but it sounds like you are spending a lot of time trying frantically to freeze your wife forever. I'v never been through something like this, but maybe everyone would get more out of it if you just--i don't know--forget that she is dying and spend as much natural time with her as you can. Then you (and your kids) will have memories of Mom as she was when she was happy with her family, rather than hours of video with an elephant in the room.
Grand parent.
Your post is this post's parent.
The one you were replying to was this post's GP (your parent).
The one before that was this post's Great grand parent, (GGP).
Etc.
I'm a moron: please explain how running 64bit on a computer with 4G of ram will fix thrashing.
how did this not get modded up?
I read an article not long ago (sorry, can't find a link) basically saying that artists think of their work as part of their soul. This doesn't mean artists never give away work, and it doesn't meant that programmer's think of their work as worthless, but it does seem like there is a tendency for artists to elevate the value of their work to the invaluable-and-irreplaceable end of the scale.
I suspect there are a few other things that compound the problem, and make it easier for programmers to cooperate. For example, most programers think of their programs as tools. As long as everyone agrees on what the tool is doing (i.e., what features fit) it is pretty easy for other people to contribute. If your patch fixes a bug--and doesn't introduce regressions--then it's pretty cut and dry: it makes the tool a better tool for everyone and makes the dev's job easier; if it implements a feature that the lead developer wants but hasn't had time to write, ditto. Obviously there are gray areas, where the bugfix is a dirty hack or the dev doesn't want the feature, but it is generally clear-ish, and even the grey areas can be ironed out if the team is communicating (e.g., "I'm not taking this hack for x, y, z reasons. . . do it right and come back").
As you noted, artwork doesn't have such clear lines about what is and isn't an improvement.