OCR the books and keep the originals. Provide a way for reader feed back of problem spots.
That would maintain The Librarians musty stacks while providing for us in the country (really, the country...with corn and deer and gun racks).
[ Foget about the stability of digital media. It will always change. In 8 years I've had 8 harddrives; one filesystem. My home directory contains files that have not been modified since 1992. I've moved from a 15 MB filesystem to a 40 GB filesystem without loosing any data. Expect evolution of media. ]
How about 41,000 MOSIX patched Linux instances. That would make the migration of processes to idle VMs transparent.
[off topic - Is the architecture of a mainframe expensive or just the high end IBM implementation that's expensive? Could an amature cobble together a slow "mainframe" (robust, multi-cpu, multi-partition, hot swappable peripherals) at home out of PC parts and a soldering iron (ignoring the O/S issues for now)?]
I read Orwell's 1984 in 6th grade (is that 12?). I wasn't even an advanced reader. I had friends reading much harder stuff. Don't allow her to shun the whole genre just because the first book she read was to simple. I wouldn't worry about mentioning sex; may be avoid too much of a description. At 13 she knows the mechanics, you just don't want to spark too much interest.
Recongnize that there are many styles. 1. Fantasy (I don't like, so there is just one fantasy style;-) 2. closed end SF -- Asamov is my favorite example. More questions are answered than asked in his stories. 3. open end SF -- Brin is my favorite example. At the end of the book, you have more questions than you started with (My favorite style). 4. cyberpunk/highly stylized -- BladeRunner (a movie), Snowcrash, Idoru. 5. good books that aren't SF like Willis's Dooms Day Book and Stephenson's Zodiac.
Then realize that some writing styles challenge more that just your imagination. I am reading Difference Machine for the second time in two months and am having problems putting the whole story together. I would toss Asimov in with the easy readers and Gibson in with the tough readers.
The best book ever written is Earth, by David Brin. My father who only reads Clancy style fiction loved the wealth of ideas presented in the book.
I've been wrestling with some internal docs at a client site. How could we transmit the internal data using standard doc types, when I bumped into the following (at learned how wrong I was, for my case in particular).
I had a problem with my right elbow (mouse arm), then I started drinking water with my left arm...now they both hurt.:-)
Seriously, I found that placing the keyboard on my lap and the mouse directly infront of me, instead of a foot to the right had an almost immediate reduction of pain in the mouse elbow.
I just switched to an ergo keyboard with a pointing stick, but that just made different parts of my arms hurt (muscles farther from my wrists). I am going to try a ergo keyboard with a touchpad next.
I'm not criticizing anything I've read today, but I wonder if the amount of criticism of/.'s English and spelling is due to the number of non native speakers that frequent this site? After studying English from a book, you may notice the details a lot more than those of use that gloss over the details.
Are you kidding? You're going to spend ~$3k with out touching, seeing, or holding an item that you might spend 10+ hours a day with?
I just bought a laptop. I ended up with a Compaq because I could find retail outlets that had some in stock. I did not buy a VIAO because I couldn't find one on a shelf anywhere to feel what it was like (weight, balance, "solidness", etc).
[As a side note, I couldn't even tell Sony this because I couldn't find a feedback email address anywhere on their sight.]
People still like to touch the goods their going to buy. I'd bet that IBM's internet sales slow now that users can't go to the store to evaluate the product, then go buy it on the internet.
I do all my business on a Compaq 1900T (400 Celeron, 128 MB RAM, 10 GB disk, 1024x768x16bit at 13.3"). I am a Java/CORBA/Web/cool stuff consultant.
I use Applix for my reports (export to RTF) and my invoicing. Applix has read every document I've thrown at it pretty well. I haven't had any complains from folks using Word to read Applix either.
I use javac, emacs, mysql, gcc, etc for "real" work.
My book keeper does use Win95 for Quicken and I have to travel to a client site to use Rational Rose on NT.
The Compaq 1900T has worked pretty well, except if I close 'er up on suspend, it gets hot, the fan kicks on, the battery goes dead, then it cools down. I would prefer that it stay cold or shutdown.
Compaq offers no documentation on the sound system. Apparently it is part of the NEOMagic graphics chips. OSS offeres limited support (good enough for me).
I don't, nor did I plan to use the built in modem. That isn't normally an issue; I'm either on site or at home, both of which have ethernet.
If the programs are completely independent and will never be changed, I'd agree.
Of course in the real world, I don't plan on writing the same code twice (so the programs would use a common library) and programs are constantly changing to adapt to the changing business around them (so someone else may need to maintain them later).
Writing code is easy, but doesn't pay so well. Solving business problems is hard, but is compensated accordingly.
The evil empire doesn't care which artist you spend money on. Everything is relative, so most folks wont decrease their spending on music if the quality is poor, because most folks don't know any better.
I was under the impression that XML was just a way to organize data (using the user defined tags). How does that constitute a Word Proc format? MS could change the meaning of the tags every couple years. No difference, just with XML the files will be bigger (ascii instead of binary).
This is why I _don't_ think that there will be a developer glut in 2005, like some of the media is predicting (due to the Y2K increase in developers).
Plus, many (not all, but many, many) of these folks doing design work out there without the fundimentals are generating junk that will need to be reworked about 2005.
I typed at least 20,000 LOC, but I most didn't make it to production. ~60,0000 LOC that were generated by my code did make it to production though, so it is hard to measure.
LOC suck anyway. I could write a 300 line HelloWorld.java. Would that make me a better programer?
My most productive days have resulted in net negative LOC!
I can't think of a better ending to his books than what he provided. Why not just end them? I am glad I read each of them, even if I was disappointed when the prose just ended on the last page.
OK, about 6 years ago, I took a EE course that taught us CSs about CPU design.
At the time we were comparing Pentium, PA-RISC, Alpha, and MIPS.
If I remember, Alpha hadd a huge amount of transistors dedicated to branch prediction. PS-RISK always assumed that the program would loop. As a class, we questioned how much branch prediction actually helped. Does anyone have a good feel, or even some numbers to descibe how much branch prediction improves performance?
This Merced design of executing both branches seems like it would take an enormous amount of work. Is it really worth it? Isn't a simpler design able to operate at a higher clock rate?
And, has anyone read about async processors lately? Anything ever released commercially for that?
Thanks, Joe [forgive the English, I don't have an English compiler.]
One of the issues with the release of Melissa was its unauthorized use of personal information to propagate. So, Microsfot's misleading lack of mention of the GUID, or unauthorized use of personal information, to catch him is good?!
Joe
WYSIWYG ends up sucking
on
Quickie Fu
·
· Score: 1
Try reload. I got a blank page with NS4.07, but then hit reload and it was fine. Of course I'm behind a MS proxy server today.
It is all about design. If you design something as a prototype, it will not be maintainable or extensible. If you always do industrial strength design for prototypes, you will never get anything done.
I worked in a well designed ObjC system where we could through up new apps in less than an hour, but we always rewrote them after getting buy in from the customer. We did NOT change languages, just designed them for the long haul, instead of as PROTOTYPES.
With my limited VB experience, I do question how you would do industrial strength VB programming. The libraries are too big to find the "Right Way" to do things.
Slashdot Mirror
No, it's just old. It was is CNET last week and has been featured at IBM for a few days.
Joe
It's our library. Let us proof them.
OCR the books and keep the originals. Provide a way for reader feed back of problem spots.
That would maintain The Librarians musty stacks while providing for us in the country (really, the country...with corn and deer and gun racks).
[ Foget about the stability of digital media. It will always change. In 8 years I've had 8 harddrives; one filesystem. My home directory contains files that have not been modified since 1992. I've moved from a 15 MB filesystem to a 40 GB filesystem without loosing any data. Expect evolution of media. ]
Joe
How about 41,000 MOSIX patched Linux instances. That would make the migration of processes to idle VMs transparent.
[off topic - Is the architecture of a mainframe expensive or just the high end IBM implementation that's expensive? Could an amature cobble together a slow "mainframe" (robust, multi-cpu, multi-partition, hot swappable peripherals) at home out of PC parts and a soldering iron (ignoring the O/S issues for now)?]
You anti-social-stay-at-home suburbanites never go to the library. Even Podunk libraries have net access. Every town has a public library.
In Fort Wayne (a cite of 160,000) has one "cybercafe" in the corner of a local bar.
Joe
I read Orwell's 1984 in 6th grade (is that 12?). I wasn't even an advanced reader. I had friends reading much harder stuff. Don't allow her to shun the whole genre just because the first book she read was to simple. I wouldn't worry about mentioning sex; may be avoid too much of a description. At 13 she knows the mechanics, you just don't want to spark too much interest.
;-)
Recongnize that there are many styles.
1. Fantasy (I don't like, so there is just one fantasy style
2. closed end SF -- Asamov is my favorite example. More questions are answered than asked in his stories.
3. open end SF -- Brin is my favorite example. At the end of the book, you have more questions than you started with (My favorite style).
4. cyberpunk/highly stylized -- BladeRunner (a movie), Snowcrash, Idoru.
5. good books that aren't SF like Willis's Dooms Day Book and Stephenson's Zodiac.
Then realize that some writing styles challenge more that just your imagination. I am reading Difference Machine for the second time in two months and am having problems putting the whole story together. I would toss Asimov in with the easy readers and Gibson in with the tough readers.
The best book ever written is Earth, by David Brin. My father who only reads Clancy style fiction loved the wealth of ideas presented in the book.
Joe
I've been wrestling with some internal docs at a client site. How could we transmit the internal data using standard doc types, when I bumped into the following (at learned how wrong I was, for my case in particular).
/ meaning.html
http://www-4.ibm.com/software/developer/library
Joe
I had a problem with my right elbow (mouse arm), then I started drinking water with my left arm...now they both hurt. :-)
Seriously, I found that placing the keyboard on my lap and the mouse directly infront of me, instead of a foot to the right had an almost immediate reduction of pain in the mouse elbow.
I just switched to an ergo keyboard with a pointing stick, but that just made different parts of my arms hurt (muscles farther from my wrists). I am going to try a ergo keyboard with a touchpad next.
I think I just need more excersize.
Joe
I'm not criticizing anything I've read today, but I wonder if the amount of criticism of /.'s English and spelling is due to the number of non native speakers that frequent this site? After studying English from a book, you may notice the details a lot more than those of use that gloss over the details.
Joe
Are you kidding? You're going to spend ~$3k with out touching, seeing, or holding an item that you might spend 10+ hours a day with?
I just bought a laptop. I ended up with a Compaq because I could find retail outlets that had some in stock. I did not buy a VIAO because I couldn't find one on a shelf anywhere to feel what it was like (weight, balance, "solidness", etc).
[As a side note, I couldn't even tell Sony this because I couldn't find a feedback email address anywhere on their sight.]
People still like to touch the goods their going to buy. I'd bet that IBM's internet sales slow now that users can't go to the store to evaluate the product, then go buy it on the internet.
Joe
I do all my business on a Compaq 1900T (400 Celeron, 128 MB RAM, 10 GB disk, 1024x768x16bit at 13.3"). I am a Java/CORBA/Web/cool stuff consultant.
I use Applix for my reports (export to RTF) and my invoicing. Applix has read every document I've thrown at it pretty well. I haven't had any complains from folks using Word to read Applix either.
I use javac, emacs, mysql, gcc, etc for "real" work.
My book keeper does use Win95 for Quicken and I have to travel to a client site to use Rational Rose on NT.
The Compaq 1900T has worked pretty well, except if I close 'er up on suspend, it gets hot, the fan kicks on, the battery goes dead, then it cools down. I would prefer that it stay cold or shutdown.
Compaq offers no documentation on the sound system. Apparently it is part of the NEOMagic graphics chips. OSS offeres limited support (good enough for me).
I don't, nor did I plan to use the built in modem. That isn't normally an issue; I'm either on site or at home, both of which have ethernet.
Joe
If the programs are completely independent and will never be changed, I'd agree.
Of course in the real world, I don't plan on writing the same code twice (so the programs would use a common library) and programs are constantly changing to adapt to the changing business around them (so someone else may need to maintain them later).
Writing code is easy, but doesn't pay so well. Solving business problems is hard, but is compensated accordingly.
Joe
Other systems I have seen like this fade out at 2 km and are useless in fog, snow, rain.... Anyone know any specifics about this one?
I know there is one in production in Arizona somewhere.
Joe
"They" might have this take on things.
The evil empire doesn't care which artist you spend money on. Everything is relative, so most folks wont decrease their spending on music if the quality is poor, because most folks don't know any better.
Possibility?
Joe
Where I work "they" are cracking down because 40% of all sick days are taken on Mondays or Fridays.
Joe
I was under the impression that XML was just a way to organize data (using the user defined tags). How does that constitute a Word Proc format? MS could change the meaning of the tags every couple years. No difference, just with XML the files will be bigger (ascii instead of binary).
Joe
Heat.
This is why I _don't_ think that there will be a developer glut in 2005, like some of the media is predicting (due to the Y2K increase in developers).
Plus, many (not all, but many, many) of these folks doing design work out there without the fundimentals are generating junk that will need to be reworked about 2005.
Just my opinion,
Joe
I typed at least 20,000 LOC, but I most didn't make it to production. ~60,0000 LOC that were generated by my code did make it to production though, so it is hard to measure.
LOC suck anyway. I could write a 300 line HelloWorld.java. Would that make me a better programer?
My most productive days have resulted in net negative LOC!
Joe
Think of the loose ending as his signature.
It wouldn't really be Stephenson without it.
I can't think of a better ending to his books than what he provided. Why not just end them? I am glad I read each of them, even if I was disappointed when the prose just ended on the last page.
Joe
OK, about 6 years ago, I took a EE course that taught us CSs about CPU design.
At the time we were comparing Pentium, PA-RISC, Alpha, and MIPS.
If I remember, Alpha hadd a huge amount of transistors dedicated to branch prediction. PS-RISK always assumed that the program would loop. As a class, we questioned how much branch prediction actually helped. Does anyone have a good feel, or even some numbers to descibe how much branch prediction improves performance?
This Merced design of executing both branches seems like it would take an enormous amount of work. Is it really worth it? Isn't a simpler design able to operate at a higher clock rate?
And, has anyone read about async processors lately? Anything ever released commercially for that?
Thanks,
Joe
[forgive the English, I don't have an English compiler.]
One of the issues with the release of Melissa was its unauthorized use of personal information to propagate. So, Microsfot's misleading lack of mention of the GUID, or unauthorized use of personal information, to catch him is good?!
Joe
Try reload. I got a blank page with NS4.07, but then hit reload and it was fine. Of course I'm behind a MS proxy server today.
Joe
It is all about design. If you design something as a prototype, it will not be maintainable or extensible. If you always do industrial strength design for prototypes, you will never get anything done.
I worked in a well designed ObjC system where we could through up new apps in less than an hour, but we always rewrote them after getting buy in from the customer. We did NOT change languages, just designed them for the long haul, instead of as PROTOTYPES.
With my limited VB experience, I do question how you would do industrial strength VB programming. The libraries are too big to find the "Right Way" to do things.