classes ::: computer,
children :::
branches ::: new computer
see also :::

bookmarks: Instances - Definitions - Quotes - Chapters - Wordnet - Webgen


object:new computer
class:computer

Just wanted to take some notes about what I am looking for in the new computer. Mine is a 10-12 year old laptop, so even a cheap computer often offers like 4-8 times the ram for example.

on that note:
more ram ::: 8-16 gigs, ddr3 or ddr4 if possible. (ddr4 is more energy efficient (15% or so if I recall))
similar ssd ::: same as last time but if I could get 1TB+ instead of 500, that would be swell
MORE usbs ::: good lord. the laptop had/has 3. I need at least 5 next time. 8 is ideal. (keyboard, draw pad, mouse, keyboard, 1-4 external hard drives). one could imagine more needed in the future aswell.
hd ::: maybe 500 ssd is fine if it also has a 2tb+ hard drive.
processor ::: yep, whatever I can get on this is gravy.

when more things come to mind
I could also just add later what is missing but ideally its all good to begin with. but things like the hard drive could be a potentially easy solve.. potentially.. if I want to play with windows again.


questions, comments, suggestions/feedback, take-down requests, contribute, etc
contact me @ integralyogin@gmail.com or
join the integral discord server (chatrooms)
if the page you visited was empty, it may be noted and I will try to fill it out. cheers


OBJECT INSTANCES [0] - TOPICS - AUTHORS - BOOKS - CHAPTERS - CLASSES - SEE ALSO - SIMILAR TITLES

TOPICS
SEE ALSO


AUTH

BOOKS
Enchiridion
The_Use_and_Abuse_of_History
The_Yoga_Sutras

IN CHAPTERS TITLE
new_computer

IN CHAPTERS CLASSNAME

IN CHAPTERS TEXT
Apology
BOOK_XIII._-_That_death_is_penal,_and_had_its_origin_in_Adam's_sin
ENNEAD_02.09_-_Against_the_Gnostics;_or,_That_the_Creator_and_the_World_are_Not_Evil.
ENNEAD_03.07_-_Of_Time_and_Eternity.
ENNEAD_04.02_-_How_the_Soul_Mediates_Between_Indivisible_and_Divisible_Essence.
ENNEAD_06.05_-_The_One_and_Identical_Being_is_Everywhere_Present_In_Its_Entirety.345
Euthyphro
new_computer

PRIMARY CLASS

computer
SIMILAR TITLES
new computer

DEFINITIONS

backup ::: (operating system) (back up when used as a verb) A spare copy of a file, file system, or other resource for use in the event of failure or loss of the original.The term commonly refers to a copy of the files on a computer's disks, made periodically and kept on magnetic tape or other removable medium (also called a dump).This essential precaution is neglected by most new computer users until the first time they experience a disk crash or accidentally delete the only copy of hardware may be insured against fire, the data on it is almost certainly neither insured nor easily replaced.See also backup software, differential backup, incremental backup, full backup. Compare archive, source code management.(2004-03-16)

backup "operating system" ("back up" when used as a verb) A spare copy of a file, file system, or other resource for use in the event of failure or loss of the original. The term commonly refers to a copy of the files on a computer's {disks}, made periodically and kept on {magnetic tape} or other removable medium (also called a "{dump}"). This essential precaution is neglected by most new computer users until the first time they experience a {disk crash} or accidentally delete the only copy of the file they have been working on for the last six months. Ideally the backup copies should be kept at a different site or in a fire safe since, though your hardware may be insured against fire, the data on it is almost certainly neither insured nor easily replaced. See also {backup software}, {differential backup}, {incremental backup}, {full backup}. Compare {archive}, {source code management}. (2004-03-16)

bare metal ::: 1. New computer hardware, unadorned with such snares and delusions as an operating system, an HLL, or even assembler. Commonly used in the phrase assemblers that will be used to write the compiler back ends that will give the new computer a real development environment.2. Programming on the bare metal is also used to describe a style of hand-hacking that relies on bit-level peculiarities of a particular hardware industrial embedded systems, and in the code of hackers who just can't let go of that low-level control. See Real Programmer.In the world of personal computing, bare metal programming is often considered a Good Thing, or at least a necessary evil (because these computers have often down to the bare metal. People who can do this sort of thing well are held in high regard.[Jargon File]

bare metal 1. New computer hardware, unadorned with such snares and delusions as an {operating system}, an {HLL}, or even {assembler}. Commonly used in the phrase "programming on the bare metal", which refers to the arduous work of {bit bashing} needed to create these basic tools for a new computer. Real bare-metal programming involves things like building {boot PROMs} and {BIOS} chips, implementing basic {monitors} used to test {device drivers}, and writing the assemblers that will be used to write the compiler back ends that will give the new computer a real development environment. 2. "Programming on the bare metal" is also used to describe a style of {hand-hacking} that relies on bit-level peculiarities of a particular hardware design, especially tricks for speed and space optimisation that rely on crocks such as overlapping instructions (or, as in the famous case described in {The Story of Mel}, interleaving of opcodes on a magnetic drum to minimise fetch delays due to the device's rotational latency). This sort of thing has become less common as the relative costs of programming time and computer resources have changed, but is still found in heavily constrained environments such as industrial embedded systems, and in the code of hackers who just can't let go of that low-level control. See {Real Programmer}. In the world of personal computing, bare metal programming is often considered a {Good Thing}, or at least a necessary evil (because these computers have often been sufficiently slow and poorly designed to make it necessary; see {ill-behaved}). There, the term usually refers to bypassing the BIOS or OS interface and writing the application to directly access device registers and computer addresses. "To get 19.2 kilobaud on the serial port, you need to get down to the bare metal." People who can do this sort of thing well are held in high regard. [{Jargon File}]

black art A collection of arcane, unpublished, and (by implication) mostly ad-hoc techniques developed for a particular application or systems area (compare {black magic}). VLSI design and compiler code optimisation were (in their beginnings) considered classic examples of black art; as theory developed they became {deep magic}, and once standard textbooks had been written, became merely {heavy wizardry}. The huge proliferation of formal and informal channels for spreading around new computer-related technologies during the last twenty years has made both the term "black art" and what it describes less common than formerly. See also {voodoo programming}. [{Jargon File}]

break-even point In the process of implementing a new computer language, the point at which the language is sufficiently effective that one can implement the language in itself. That is, for a new language called, hypothetically, FOOGOL, one has reached break-even when one can write a demonstration compiler for FOOGOL in FOOGOL, discard the original implementation language, and thereafter use working versions of FOOGOL to develop newer ones. This is an important milestone. See {My Favourite Toy Language}. [There actually is a language called {Foogol}].

break-even point ::: In the process of implementing a new computer language, the point at which the language is sufficiently effective that one can implement the language in versions of FOOGOL to develop newer ones. This is an important milestone. See My Favourite Toy Language.[There actually is a language called Foogol].

Hard costs - Refers to the price paid to purchase the actual assets. For example, the price paid for a new computer would be considered the hard cost. The soft costs would be any additional fees or charges for services like invoiced installation charges, any extended guarantees or warranties, or extra service and support contracts for the new computer.

John Vincent Atanasoff ::: (person) John Vincent Atanasoff, 1903-10-04 - 1995-06-15. An American mathemetical physicist, and the inventor of the electronic digital computer. Between 1937 and 1942 he built the Atanasoff-Berry Computer with Clifford Berry, at the Iowa State University.Atanasoff was born on 1903-10-04 in Hamilton, New York. In 1925, he got a Bachelor of Science degree in Electrical Engineering from the University of University. He received a PhD as a theoretical physicist from the University of Wisconsin in 1930.While an associate professor of mathematics and physics at Iowa State University, Atanasoff began to envision a digital computational device, electronic digital computer, Atanasoff was introduced to a graduate student named Clifford Berry, who helped him build the computer.The first prototype of the Atanasoff-Berry Computer was demonstrated in December 1939. Although no patent was awarded for the new computer, in 1973 US District Judge Earl R. Larson declared Atanasoff the inventor of the digital computer (declaring the ENIAC patent invalid).Atanasoff was awarded the National Medal of Technology by US President Bush on 1990-11-13. He died following a stroke on 1995-06-15. .[Atanasoff Forgotten Father of the Computer, C. R. Mollenhoff, Iowa State University Press 1988].(2001-10-03)

The story of Mel, a Real Programmer "programming, person" A 1983 article by Ed Nather about {hacker} {Mel Kaye}. The full text follows. A recent article devoted to the macho side of programming made the bald and unvarnished statement, "Real Programmers write in FORTRAN". Maybe they do now, in this decadent era of Lite beer, hand calculators and "user-friendly" software but back in the Good Old Days, when the term "software" sounded funny and Real Computers were made out of {drums} and {vacuum tubes}, Real Programmers wrote in {machine code} - not {Fortran}, not {RATFOR}, not even {assembly language} - {Machine Code}, raw, unadorned, inscrutable {hexadecimal} numbers, directly. Lest a whole new generation of programmers grow up in ignorance of this glorious past, I feel duty-bound to describe, as best I can through the generation gap, how a Real Programmer wrote code. I'll call him Mel, because that was his name. I first met Mel when I went to work for {Royal McBee Computer Corporation}, a now-defunct subsidiary of the typewriter company. The firm manufactured the {LGP-30}, a small, cheap (by the standards of the day) {drum}-memory computer, and had just started to manufacture the RPC-4000, a much-improved, bigger, better, faster -- drum-memory computer. Cores cost too much, and weren't here to stay, anyway. (That's why you haven't heard of the company, or the computer.) I had been hired to write a {Fortran} compiler for this new marvel and Mel was my guide to its wonders. Mel didn't approve of compilers. "If a program can't rewrite its own code," he asked, "what good is it?" Mel had written, in {hexadecimal}, the most popular computer program the company owned. It ran on the {LGP-30} and played blackjack with potential customers at computer shows. Its effect was always dramatic. The LGP-30 booth was packed at every show, and the IBM salesmen stood around talking to each other. Whether or not this actually sold computers was a question we never discussed. Mel's job was to re-write the blackjack program for the {RPC-4000}. ({Port}? What does that mean?) The new computer had a one-plus-one addressing scheme, in which each machine instruction, in addition to the {operation code} and the address of the needed {operand}, had a second address that indicated where, on the revolving drum, the next instruction was located. In modern parlance, every single instruction was followed by a {GO TO}! Put *that* in {Pascal}'s pipe and smoke it. Mel loved the RPC-4000 because he could optimize his code: that is, locate instructions on the drum so that just as one finished its job, the next would be just arriving at the "read head" and available for immediate execution. There was a program to do that job, an "optimizing assembler", but Mel refused to use it. "You never know where its going to put things", he explained, "so you'd have to use separate constants". It was a long time before I understood that remark. Since Mel knew the numerical value of every operation code, and assigned his own drum addresses, every instruction he wrote could also be considered a numerical constant. He could pick up an earlier "add" instruction, say, and multiply by it, if it had the right numeric value. His code was not easy for someone else to modify. I compared Mel's hand-optimised programs with the same code massaged by the optimizing assembler program, and Mel's always ran faster. That was because the "{top-down}" method of program design hadn't been invented yet, and Mel wouldn't have used it anyway. He wrote the innermost parts of his program loops first, so they would get first choice of the optimum address locations on the drum. The optimizing assembler wasn't smart enough to do it that way. Mel never wrote time-delay loops, either, even when the balky {Flexowriter} required a delay between output characters to work right. He just located instructions on the drum so each successive one was just *past* the read head when it was needed; the drum had to execute another complete revolution to find the next instruction. He coined an unforgettable term for this procedure. Although "optimum" is an absolute term, like "unique", it became common verbal practice to make it relative: "not quite optimum" or "less optimum" or "not very optimum". Mel called the maximum time-delay locations the "most pessimum". After he finished the blackjack program and got it to run, ("Even the initialiser is optimised", he said proudly) he got a Change Request from the sales department. The program used an elegant (optimised) {random number generator} to shuffle the "cards" and deal from the "deck", and some of the salesmen felt it was too fair, since sometimes the customers lost. They wanted Mel to modify the program so, at the setting of a sense switch on the console, they could change the odds and let the customer win. Mel balked. He felt this was patently dishonest, which it was, and that it impinged on his personal integrity as a programmer, which it did, so he refused to do it. The Head Salesman talked to Mel, as did the Big Boss and, at the boss's urging, a few Fellow Programmers. Mel finally gave in and wrote the code, but he got the test backward, and, when the sense switch was turned on, the program would cheat, winning every time. Mel was delighted with this, claiming his subconscious was uncontrollably ethical, and adamantly refused to fix it. After Mel had left the company for greener pa$ture$, the Big Boss asked me to look at the code and see if I could find the test and reverse it. Somewhat reluctantly, I agreed to look. Tracking Mel's code was a real adventure. I have often felt that programming is an art form, whose real value can only be appreciated by another versed in the same arcane art; there are lovely gems and brilliant coups hidden from human view and admiration, sometimes forever, by the very nature of the process. You can learn a lot about an individual just by reading through his code, even in hexadecimal. Mel was, I think, an unsung genius. Perhaps my greatest shock came when I found an innocent loop that had no test in it. No test. *None*. Common sense said it had to be a closed loop, where the program would circle, forever, endlessly. Program control passed right through it, however, and safely out the other side. It took me two weeks to figure it out. The RPC-4000 computer had a really modern facility called an {index register}. It allowed the programmer to write a program loop that used an indexed instruction inside; each time through, the number in the index register was added to the address of that instruction, so it would refer to the next datum in a series. He had only to increment the index register each time through. Mel never used it. Instead, he would pull the instruction into a machine register, add one to its address, and store it back. He would then execute the modified instruction right from the register. The loop was written so this additional execution time was taken into account -- just as this instruction finished, the next one was right under the drum's read head, ready to go. But the loop had no test in it. The vital clue came when I noticed the index register bit, the bit that lay between the address and the operation code in the instruction word, was turned on-- yet Mel never used the index register, leaving it zero all the time. When the light went on it nearly blinded me. He had located the data he was working on near the top of memory -- the largest locations the instructions could address -- so, after the last datum was handled, incrementing the instruction address would make it overflow. The carry would add one to the operation code, changing it to the next one in the instruction set: a jump instruction. Sure enough, the next program instruction was in address location zero, and the program went happily on its way. I haven't kept in touch with Mel, so I don't know if he ever gave in to the flood of change that has washed over programming techniques since those long-gone days. I like to think he didn't. In any event, I was impressed enough that I quit looking for the offending test, telling the Big Boss I couldn't find it. He didn't seem surprised. When I left the company, the blackjack program would still cheat if you turned on the right sense switch, and I think that's how it should be. I didn't feel comfortable hacking up the code of a Real Programmer." [Posted to {Usenet} by its author, Ed Nather "utastro!nather", on 1983-05-21]. {Jargon File (http://www.catb.org/jargon/html/story-of-mel.html)}. [{On the trail of a Real Programmer (http://www.jamtronix.com/blog/2011/03/25/on-the-trail-of-a-real-programmer/)}, 2011-03-25 blog post by "jonno" at Jamtronix] [When did it happen? Did Mel use hexadecimal or octal?] (2003-09-12)

The story of Mel, a Real Programmer ::: (programming, person) An article devoted to the macho side of programming made the bald and unvarnished statement, Real Programmers write in Fortran. language - Machine Code. Raw, unadorned, inscrutable hexadecimal numbers, directly.Lest a whole new generation of programmers grow up in ignorance of this glorious past, I feel duty-bound to describe, as best I can through the generation gap, how a Real Programmer wrote code. I'll call him Mel, because that was his name.I first met Mel when I went to work for Royal McBee Computer Corporation, a now-defunct subsidiary of the typewriter company. The firm manufactured the faster -- drum-memory computer. Cores cost too much, and weren't here to stay, anyway. (That's why you haven't heard of the company, or the computer.)I had been hired to write a Fortran compiler for this new marvel and Mel was my guide to its wonders. Mel didn't approve of compilers.If a program can't rewrite its own code, he asked, what good is it?Mel had written, in hexadecimal, the most popular computer program the company owned. It ran on the LGP-30 and played blackjack with potential customers at every show, and the IBM salesmen stood around talking to each other. Whether or not this actually sold computers was a question we never discussed.Mel's job was to re-write the blackjack program for the RPC-4000. (Port? What does that mean?) The new computer had a one-plus-one addressing scheme, in which drum, the next instruction was located. In modern parlance, every single instruction was followed by a GO TO! Put *that* in Pascal's pipe and smoke it.Mel loved the RPC-4000 because he could optimize his code: that is, locate instructions on the drum so that just as one finished its job, the next would be was a program to do that job, an optimizing assembler, but Mel refused to use it.You never know where its going to put things, he explained, so you'd have to use separate constants.It was a long time before I understood that remark. Since Mel knew the numerical value of every operation code, and assigned his own drum addresses, every pick up an earlier add instruction, say, and multiply by it, if it had the right numeric value. His code was not easy for someone else to modify.I compared Mel's hand-optimised programs with the same code massaged by the optimizing assembler program, and Mel's always ran faster. That was because the they would get first choice of the optimum address locations on the drum. The optimizing assembler wasn't smart enough to do it that way.Mel never wrote time-delay loops, either, even when the balky Flexowriter required a delay between output characters to work right. He just located practice to make it relative: not quite optimum or less optimum or not very optimum. Mel called the maximum time-delay locations the most pessimum.After he finished the blackjack program and got it to run, (Even the initialiser is optimised, he said proudly) he got a Change Request from the Mel to modify the program so, at the setting of a sense switch on the console, they could change the odds and let the customer win.Mel balked. He felt this was patently dishonest, which it was, and that it impinged on his personal integrity as a programmer, which it did, so he refused program would cheat, winning every time. Mel was delighted with this, claiming his subconscious was uncontrollably ethical, and adamantly refused to fix it.After Mel had left the company for greener pa$ture$, the Big Boss asked me to look at the code and see if I could find the test and reverse it. Somewhat reluctantly, I agreed to look. Tracking Mel's code was a real adventure.I have often felt that programming is an art form, whose real value can only be appreciated by another versed in the same arcane art; there are lovely gems and reading through his code, even in hexadecimal. Mel was, I think, an unsung genius.Perhaps my greatest shock came when I found an innocent loop that had no test in it. No test. *None*. Common sense said it had to be a closed loop, where the it, however, and safely out the other side. It took me two weeks to figure it out.The RPC-4000 computer had a really modern facility called an index register. It allowed the programmer to write a program loop that used an indexed instruction address of that instruction, so it would refer to the next datum in a series. He had only to increment the index register each time through. Mel never used it.Instead, he would pull the instruction into a machine register, add one to its address, and store it back. He would then execute the modified instruction right taken into account -- just as this instruction finished, the next one was right under the drum's read head, ready to go. But the loop had no test in it.The vital clue came when I noticed the index register bit, the bit that lay between the address and the operation code in the instruction word, was turned on-- yet Mel never used the index register, leaving it zero all the time. When the light went on it nearly blinded me.He had located the data he was working on near the top of memory -- the largest locations the instructions could address -- so, after the last datum was instruction set: a jump instruction. Sure enough, the next program instruction was in address location zero, and the program went happily on its way.I haven't kept in touch with Mel, so I don't know if he ever gave in to the flood of change that has washed over programming techniques since those that I quit looking for the offending test, telling the Big Boss I couldn't find it. He didn't seem surprised.When I left the company, the blackjack program would still cheat if you turned on the right sense switch, and I think that's how it should be. I didn't feel comfortable hacking up the code of a Real Programmer.[Posted to USENET by its author, Ed Nather utastro!nather>, on 1983-05-21]. .[When did it happen? Did Mel use hexadecimal or octal?](2003-09-12)



QUOTES [0 / 0 - 25 / 25]


KEYS (10k)


NEW FULL DB (2.4M)

   3 Walter Isaacson
   3 Austin Kleon
   2 William Zinsser
   2 Mark Manson
   2 Erik Brynjolfsson

*** NEWFULLDB 2.4M ***

1:Nobody told all the new computer writers that the essence of writing is rewriting. ~ William Zinsser,
2:Woz spent a lot of time at home reading his father’s electronics journals, and he became enthralled by stories about new computers, ~ Walter Isaacson,
3:The implied methods would permit construction of entirely new computers reduced in size and basic complexity by a factor of at least a thousand. ~ Frank Herbert,
4:As I get ready to buy a new computer, I'm stunned at all the many micro drafts, of different chapters and scenes and whatnot, that litter the hard drive. ~ Alexander Chee,
5:Nobody told all the new computer writers that the essence of writing is rewriting. Just because they’re writing fluently doesn’t mean they’re writing well. ~ William Zinsser,
6:The art of holding on to money is all about saying no to consumer culture. Saying no to takeout, $4 lattes, and that shiny new computer when the old one still works fine. ~ Austin Kleon,
7:Some people may have noticed the new computer shelf at the anchor desk. Rather than phone calls, we want to take real time e-mails, and we'll be starting that very soon. ~ Catherine Crier,
8:it. The art of holding on to money is all about saying no to consumer culture. Saying no to takeout, $4 lattes, and that shiny new computer when the old one still works fine. ~ Austin Kleon,
9:Every new computer program is basically doing some task that a person used to do. But the computer usually does it faster, more accurately, for less money, and without any health insurance costs. ~ Douglas Rushkoff,
10:We can just assume they have much more and powerful, more advanced technology, all the new computers, everything could be much more easier and help them to build much more and many more nuclear weapons. ~ Mordechai Vanunu,
11:receiver from Hallicrafters, the most sophisticated radios available. Woz spent a lot of time at home reading his father’s electronics journals, and he became enthralled by stories about new computers, such as the powerful ENIAC. ~ Walter Isaacson,
12:I love the hybrid quality, the new computer sections and the books yellowing with age. Libraries for me have always had a cathedral-like ambiance, a hushed sanctuary where learning is revered, where we the people elevate books and education to the level of the religious. ~ Harlan Coben,
13:I for one welcome our new computer overlords.” He later elaborated, “Just as factory jobs were eliminated in the twentieth century by new assembly-line robots, Brad and I were the first knowledge-industry workers put out of work by the new generation of ‘thinking’ machines. ~ Erik Brynjolfsson,
14:The 1970s were the decade of megabytes. In the summer of 1970, IBM introduced two new computer models with more memory than ever before: the Model 155, with 768,000 bytes of memory, and the larger Model 165, with a full megabyte, in a large cabinet. One of these room-filling mainframes could be purchased for $4,674,160. By 1982 Prime Computer was marketing a megabyte of memory on a single circuit board, for $36,000. ~ James Gleick,
15:My grandpa used to tell my dad, “Son, it’s not the money you make, it’s the money you hold on to.” Make yourself a budget. Live within your means. Pack your lunch. Pinch pennies. Save as much as you can. Get the education you need for as cheap as you can get it. The art of holding on to money is all about saying no to consumer culture. Saying no to takeout, $ 4 lattes, and that shiny new computer when the old one still works fine. ~ Austin Kleon,
16:I was in my room, sitting on the Goddamn floor, setting up my new computer when I heard yelling from the living room.
I went out to check what the fuck was happening. The last thing I expected to see was Amanda sitting on Ethan, while he was on his back on the floor. She was slapping the shit out of his head while he was yelling at her to stop.
What the fuck?
I didn't know whether to laugh, cheer, leave, or throw money at them. ~ Jay McLean,
17:In the long run, completing a marathon makes us happier than eating a chocolate cake. Raising a child makes us happier than beating a video game. Starting a small business with friends while struggling to make ends meet makes us happier than buying a new computer. These activities are stressful, arduous, and often unpleasant. They also require withstanding problem after problem. Yet they are some of the most meaningful moments and joyous things we’ll ever do ~ Mark Manson,
18:Jennings, who came in second, added a personal note on his answer to the tournament’s final question: “I for one welcome our new computer overlords.” He later elaborated, “Just as factory jobs were eliminated in the twentieth century by new assembly-line robots, Brad and I were the first knowledge-industry workers put out of work by the new generation of ‘thinking’ machines. ‘Quiz show contestant’ may be the first job made redundant by Watson, but I’m sure it won’t be the last. ~ Erik Brynjolfsson,
19:Finally, at every opportunity you have to move someone—from traditional sales, like convincing a prospect to buy a new computer system, to non-sales selling, like persuading your daughter to do her homework—be sure you can answer the two questions at the core of genuine service. If the person you’re selling to agrees to buy, will his or her life improve? When your interaction is over, will the world be a better place than when you began? If the answer to either of these questions is no, you’re doing something wrong. ~ Daniel H Pink,
20:In the long run, completing a marathon makes us happier than eating a chocolate cake. Raising a child makes us happier than beating a video game. Starting a small business with friends while struggling to make ends meet makes us happier than buying a new computer. These activities are stressful, arduous, and often unpleasant. They also require withstanding problem after problem. Yet they are some of the most meaningful moments and joyous things we’ll ever do. They involve pain, struggle, even anger and despair—yet once they’re accomplished, we look back and get all misty-eyed telling our grandkids about them. ~ Mark Manson,
21:I think it's strange - so alike and yet so different! We are capable of working together, of building the Pyramids of Egypt, the Great Wall of China, the cathedrals of Europe and the temples of Peru. We can compose unforgettable music, work in hospitals, create new computer programs.

"But at some moment all this loses its meaning, and we feel alone, as if we were part of another world, different from the one we have helped to build."

"At times, when others need our help, we grow desperate because this prevents us from enjoying life. At other times, when nobody needs us, we feel useless.

"But that's the way we are. We are complex human beings. Why despair? ~ Anonymous,
22:Cook reduced the number of Apple’s key suppliers from a hundred to twenty-four, forced them to cut better deals to keep the business, convinced many to locate next to Apple’s plants, and closed ten of the company’s nineteen warehouses. By reducing the places where inventory could pile up, he reduced inventory. Jobs had cut inventory from two months’ worth of product down to one by early 1998. By September of that year, Cook had gotten it down to six days. By the following September, it was down to an amazing two days’ worth. In addition, he cut the production process for making an Apple computer from four months to two. All of this not only saved money, it also allowed each new computer to have the very latest components available. ~ Walter Isaacson,
23:But the ugly truth is that a huge number of weapons made or sold in the United States go to Mexican cartels. This is an irrefutable fact. Mexico itself has almost no gun stores and weapons factories and gives away few licenses. Almost all weapons in the hands of cartel armies are illegal. In 2008, Mexico submitted the serial numbers from close to six thousand guns they had seized from gangsters to the U.S. Bureau of Alcohol, Tobacco, and Firearms. About 90 percent, or 5,114 of the weapons, were traced to American gun sellers. The ATF and Obama administration acknowledged America’s responsibility in this tragedy. But the gun lobby still refused to concede the point. What about tens of thousands of other seized weapons in Mexico that hadn’t been traced? gun activists said. The Mexican government, they alleged, was only tracing guns that looked as if they had come from America to sway the debate. So to make it easier to trace weapons seized in Mexico, the ATF introduced a new computer system. Between 2009 and April 2010, this traced another 63,700 firearms to U.S. gun stores.18 And those are only the ones they have captured. People can argue endlessly about the exact percentages, but the underlying fact is that tens of thousands of guns go from American stores to Mexican gangsters. ~ Ioan Grillo,
24:From then on, my computer monitored my vital signs and kept track of exactly how many calories I burned during the course of each day. If I didn’t meet my daily exercise requirements, the system prevented me from logging into my OASIS account. This meant that I couldn’t go to work, continue my quest, or, in effect, live my life. Once the lockout was engaged, you couldn’t disable it for two months. And the software was bound to my OASIS account, so I couldn’t just buy a new computer or go rent a booth in some public OASIS café. If I wanted to log in, I had no choice but to exercise first. This proved to be the only motivation I needed. The lockout software also monitored my dietary intake. Each day I was allowed to select meals from a preset menu of healthy, low-calorie foods. The software would order the food for me online and it would be delivered to my door. Since I never left my apartment, it was easy for the program to keep track of everything I ate. If I ordered additional food on my own, it would increase the amount of exercise I had to do each day, to offset my additional calorie intake. This was some sadistic software. But it worked. The pounds began to melt off, and after a few months, I was in near-perfect health. For the first time in my life I had a flat stomach, and muscles. I also had twice the energy, and I got sick a lot less frequently. When the two months ended and I was finally given the option to disable the fitness lockout, I decided to keep it in place. Now, exercising was a part of my daily ritual. ~ Ernest Cline,
25:But what about the things that you CANNOT do with the electronic version [of a book]?

You cannot drop the computer on the floor in a fit of pique, or slam it shut. You cannot leave a bookmark with a note on it in a computer and then come upon it after several years and feel happy you've found something you thought you had lost. You cannot get any sort of tactile pleasure from rubbing the pages of a computer. (Maybe some people do get a tactile pleasure from rubbing their computers, but they are not people I have any interest in knowing anything about.)

Reading on a computer screen gives you no sense of time or investment. The page always looks the same, and everything else is always in the same exact spot. When reading a book, no matter how large or small it is, a tension builds, concurrent with your progress through its pages. I get a nervous excitement as I see the number of pages that remain to be read draining inexorably from the right to the left...

I've never sat down at a new computer and, prior to using it, felt a deep and abiding need to open it up and sniff it as deeply as I can, the way I have with my a book...and though a computer will inarguably hold far more information than even the largest of books, sitting down at a computer has never provided me with that delicious anticipatory sense that I am about to be utterly and rhapsodically transported by the words within it.

I've never looked across the room at my computer and fondly remembered things that I once read in it. I can while away hours at a time just standing in front of my books and relive my favourite passages by merely gazing at their spines. I have never walked into a room full of computers, far from home, and immediately felt a warm familiarity come over me, the way I have with every library I've ever set foot in.

It is not so much that I am anti-computer; I am resolutely and stubbornly pro-book. ~ Ammon Shea,

IN CHAPTERS [7/7]



   6 Philosophy
   5 Christianity


   4 Plotinus
   2 Plato




Apology, #unset, #Sri Aurobindo, #Integral Yoga
  computers including obsolete, old, middle-aged and new computers. It
  exists because of the efforts of hundreds of volunteers and donations

BOOK XIII. - That death is penal, and had its origin in Adam's sin, #City of God, #Saint Augustine of Hippo, #Christianity
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

ENNEAD 02.09 - Against the Gnostics; or, That the Creator and the World are Not Evil., #Plotinus - Complete Works Vol 02, #Plotinus, #Christianity
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

ENNEAD 03.07 - Of Time and Eternity., #Plotinus - Complete Works Vol 03, #Plotinus, #Christianity
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

ENNEAD 04.02 - How the Soul Mediates Between Indivisible and Divisible Essence., #Plotinus - Complete Works Vol 01, #Plotinus, #Christianity
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

ENNEAD 06.05 - The One and Identical Being is Everywhere Present In Its Entirety.345, #Plotinus - Complete Works Vol 04, #Plotinus, #Christianity
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

Euthyphro, #unset, #Sri Aurobindo, #Integral Yoga
  including obsolete, old, middle-aged and new computers. It exists
  because of the efforts of hundreds of volunteers and donations from

WORDNET


































IN WEBGEN [10000/0]



change font "color":
change "background-color":
change "font-family":
change "padding":
change "table font size":
last updated: 2022-02-04 13:11:12
308304 site hits