Turn the other cheek doesn't mean allow yourself to be killed, stolen from, etc.
It seems like it is not totally ridiculous to take the teaching about turning the other cheek to mean to allow yourself to be stolen from: You have heard that it was said, "An eye for an eye and a tooth for a tooth." But I say to you, Do not resist an evildoer. But if anyone strikes you on the right cheek, turn the other also; and if anyone wants to sue you and take your coat, give your cloak as well; and if anyone forces you to go one mile, go also the second mile. Give to everyone who begs from you, and do not refuse anyone who wants to borrow from you.
It's a somewhat viscous cycle. Not only is a bigger screen more expensive, it draws more current than a small screen. This necessitates heavier and/or more expensive batteries.
The storage is very small, and it's mainly a money issue to fix that.
There's no obvious way to make the keyboard bigger without defeating the whole purpose a little bit: a small, light, rugged machine. But for my own two cents, I have an Eee PC and I haven't found the keyboard to be a real problem, even though I have large hands.
I have a 4G Eee PC and I love it. The only real problem is the screen size and resolution, which makes it much less useful for real work. I personally have no problem with the keyboard, and I have pretty big hands and I've found that it has enough power to do everything I've been trying to do on it.
I expected the installations of the software Asus provides to be more customised for the Eee PC. They did a lot to make the interface work well for the small screen, but there are times that customisation just is not there. Some settings pages will not fit in the space provided and some apps even needed resizing. (Skype is one that never wanted to cooperate, but there's really nothing ASUS can do about that.)
Overall, I've been really satisfied.
Incidentally, VIA has a theme among their processors/products of having Biblical codenames for things. In addition to Isaiah, Nehemiah, Eden, Ezra, Esther, and Samuel come to mind.
By the way, the text interface version of Pidgin is called Finch. Things like Finch and Pine (or whatever text email client the original poster was thinking of) do not solve any bandwidth problems. Displaying graphics is a local resource issue. Pidgin and any POP/IMAP email client should work fine. Mostly the same with browsers--Firefox and lynx download the same file and display them differently (though in this instance, Firefox is apt to go out and download a bit more stuff).
TeX was finished in 1989, but it had existed before that. I believe the 1982 version of TeX was significant. PostScript was not, I do not believe, an extremely important standard in those early days.
But, indeed, TeX and PostScript serve different (and complementary!) purposes. You cannot reasonably do in PostScript what you can easily do in TeX.
In this case, we need to make a nozzle-moving-around system that is very accurate. Since the parts are made by a RepRap, they cannot make track or gears, for example, that require more resolution than the current system can move and therefore lay.
The error was intentional. I was participating in a long string of comments correcting others posts with posts with errors in them. You have, disappointingly, broken that patten. (I could argue that your punctuation belong within your quotation marks or your emote was improper, but these seem to be good ways to express one's self.)
Unless you did get it and I am missing something.
He didn't say that he meant ten times as many lines of code. Great solutions to problems are often those that are the most quick, elegant, and simple. It is fair to say that someone who can pump those sorts of solutions out regularly is producing many times what others are.
Slashdot Mirror
You have heard that it was said, "An eye for an eye and a tooth for a tooth." But I say to you, Do not resist an evildoer. But if anyone strikes you on the right cheek, turn the other also; and if anyone wants to sue you and take your coat, give your cloak as well; and if anyone forces you to go one mile, go also the second mile. Give to everyone who begs from you, and do not refuse anyone who wants to borrow from you.
It's a somewhat viscous cycle. Not only is a bigger screen more expensive, it draws more current than a small screen. This necessitates heavier and/or more expensive batteries. The storage is very small, and it's mainly a money issue to fix that. There's no obvious way to make the keyboard bigger without defeating the whole purpose a little bit: a small, light, rugged machine. But for my own two cents, I have an Eee PC and I haven't found the keyboard to be a real problem, even though I have large hands.
I have a 4G Eee PC and I love it. The only real problem is the screen size and resolution, which makes it much less useful for real work. I personally have no problem with the keyboard, and I have pretty big hands and I've found that it has enough power to do everything I've been trying to do on it. I expected the installations of the software Asus provides to be more customised for the Eee PC. They did a lot to make the interface work well for the small screen, but there are times that customisation just is not there. Some settings pages will not fit in the space provided and some apps even needed resizing. (Skype is one that never wanted to cooperate, but there's really nothing ASUS can do about that.) Overall, I've been really satisfied.
Incidentally, VIA has a theme among their processors/products of having Biblical codenames for things. In addition to Isaiah, Nehemiah, Eden, Ezra, Esther, and Samuel come to mind.
I did not read your post well, Mr AC. My apologies. Nevermind.
By the way, the text interface version of Pidgin is called Finch. Things like Finch and Pine (or whatever text email client the original poster was thinking of) do not solve any bandwidth problems. Displaying graphics is a local resource issue. Pidgin and any POP/IMAP email client should work fine. Mostly the same with browsers--Firefox and lynx download the same file and display them differently (though in this instance, Firefox is apt to go out and download a bit more stuff).
TeX was finished in 1989, but it had existed before that. I believe the 1982 version of TeX was significant. PostScript was not, I do not believe, an extremely important standard in those early days. But, indeed, TeX and PostScript serve different (and complementary!) purposes. You cannot reasonably do in PostScript what you can easily do in TeX.
In this case, we need to make a nozzle-moving-around system that is very accurate. Since the parts are made by a RepRap, they cannot make track or gears, for example, that require more resolution than the current system can move and therefore lay.
The error was intentional. I was participating in a long string of comments correcting others posts with posts with errors in them. You have, disappointingly, broken that patten. (I could argue that your punctuation belong within your quotation marks or your emote was improper, but these seem to be good ways to express one's self.) Unless you did get it and I am missing something.
He didn't say that he meant ten times as many lines of code. Great solutions to problems are often those that are the most quick, elegant, and simple. It is fair to say that someone who can pump those sorts of solutions out regularly is producing many times what others are.