That's just about true, the first couple of weeks. I missed several lectures while sitting in them that way.
Once the novelty runs out though, I've noticed increases in productivity beyond that of just portable computing. I'll note that I'm refering to wireless ethernet with a laptop, and so the flexibility is probably much more - running linux, I can code anywhere. Being at CMU, coding anywhere basically requires AFS access as well, and so a network connection...
But its just a tool, and it takes a while to realize that. While I will admit to sitting in chem lab reading slashdot, I also spend idle moments in lab looking up MSDS forms or coordinating with time-out-of-sync partner.
Sounds like the fun at CMU we've been having, now that the campus is completely covered with wireless (2mb; wavelan) ethernet. There is active research in the Andrew group to do with palmtop stuff as you describe.
You need to stop any activities that cause scar tissue to build up in your hands. Foremost among these is cracking your knuckles. If your a knuckle cracker, you have to stop. The popping sounds is nitrogen liquifying under the pressure. This is bad for your muscles and is the source of your scare tissue.
Where do you get this factoid? Seems rather improbable to me that joint cracking builds up the pressure to liquify nitrogen (quite a large pressure at room/body temperatures). According to a number of sources it is the sound of gasses (including nitrogen) coming out of solution or filling gaps. I'd be interested to know if you have research/references which refute this.
One interesting thing to note that links both of the NASA articles is that apparently the BBC has a faster refresh as well. Consider this story that was just released, which tells us that, while passing a asteroid at 3.5e4 miles per hour is good, apparently you can't collect amazing amounts of data if your camera is pointed in the wrong direction.
The BBC beat the science log. Interesting, though it sounds like a very tired science log writer - with reason! But its too bad we didn't get all that we could. Oh well, we'll have to try again another time:)
As far as encryption goes, there are some 02.11 compliant things that use 40bit RC4. But really, its not that big a deal under most settings - as its about as secure as ethernet itself. The intelligent, paranoid consumer will be using encrypted channels (ssh) anyway.
As far as lectures, etc. At CMU they have an extensive wireless system (wireless andrew, see wavelan.com for a link to an article about it) which will soon be finished being deployed throughout the campus. Already though, one of the large CS lecturehalls has WavePOINT IIs. This, as well as (and a replacement for) a NetBar system that romes your IP.
But yes, there are nice things about being able to surf during a lecture. And some classrooms being built now (campuses across the country) do have networking infastructures being built in such that teachers can start to take advantage. But wireless stuff is a much better choice, if it does (which it should) become prevalent.
Glad it uses 802.11. Good stuff. We're probably going to see a heck of a lot of these iBooks on campus in the fall as the network is released... Still wouldn't trade my vaio for one, though:)
If BeOS doesn't work on a particular G3 system, the user thinks "This CD that I paid for doesn't work. BeOS sucks."
Actually, I have to disagree. I think I do prefer the previous hypothesis that Be uses it as an excuse to pursue the intel market. I'm a be developer, so I get each version when it comes. One of the guys I work for wanted to try it out. Now, be R4 didn't support a whole lot of intel boxes, but it did support his motherboard - it didn't support his Tulip-based ethernet card, even though it was listed on the (very small) "supported chipsets" list.
Be's response was "oh. damn. uh, send us a bootlisting". I won't get into the ugliness of that, but suffice it to say, the end result was just "oh well" and partition delete. They didn't seem terribly concerned - "try the next version". It struck me as funny, of course, because there are perfectly good GPL tulip drivers (becker) out there they probably could have used.
But so in general, I think they'd do fine reverse-engineering the few G3 models out there, and just stating the few models they do support. As with their intel releases : wait on the next version for more drivers and motherboard support. Be is good enough about their releasing schedules and release upgrading such that this is much more of a viable option.
>I tend to think that in time, the concept of >channels will disappear.
This, in consideration of an old wired article that struck a nerve ( "The Internet will be just like television: There may be 60 or 70 main sites out there, but the audience ends up going to only six or seven on a regular basis.").
And with the Nielsen's trying to demonstrate advertising can happen in a web-style manner ( Nielsen Comes to the Net) we've got some pretty wacky paradigm-buzzword throwdowns ahead of us.
Its interesting. This was almost the review I was going to write about the book. I finished it yesterday, in an attempt to get it out of my system. Its one of those books thats so good, as you read it it starts to affect your outlook, and you continually muse over the characters and scenes.
I've been a diehard Stephenson fan for a while. What makes him cool, beyond being an excellent storyteller - action, humor, tech - is that he really does his homework, and he tries to present ideas that he's been working on for a while. This was obvious in snow crash, diamond age, etc.
The most interesting thing about this book, for me, was that it was a nice merger from some of his shorter writings he's done in the last 3 or so years.
Modern Crypto ideas were in Spew. And he clearly knows the underseas cable world, from his lengthy journal ("the hacker tourist"? With GPS signatures?) in Mother Earth Mother Board.
Perhaps his best writing on the points of the modern thread of Cryptonicon (the Crypt and digital currency backed with cash) was in a fictional story in Time (thus, why all of his modern bios give "one of three authors ever to write a fiction piece for Time magazine") of such a bank, called Simoleon. I envision it takes place about 2-3 years after Cryptonomicon I ends... He also has an interest ing non fiction article on the subject in Time.
Anyway, definately worth the time and money. Then read Applied Cryptography and Kahn's Codebreakers. I'm off to track down some Pynchon, as this is now the third book he's been compared to.
GQmpeg actually does look rather nice. It looks motivating enough for me to perhaps customize a skin as well.
I will note something in favor of X11Amp, though. I was converting a person a couple of weeks ago to linux. He was going to linux from windows because he liked how I made X look, he was very much into aesthetics, and he figured he would do well to know unix.
His only requirements was the ability to listen to MP3s - its predominantly what he does at home without his.edu bandwidth. After installing the system though, we discovered that his (sizeable) mp3 collection was mostly corrupted - the kind of thing when downloading from http with a misconfig'd webserver. mpg123 would give him the clicks and underwater sounds. He had never noticed these things under windows/winamp.
Apparently winamp does on the fly repairing.
So does X11amp, which made him, and me, happy. Because CQmpeg relies on mpg123, that's something which is apparently significant which it lacks.
Just to add/refute abit on the 'obvious part' of your comment. The tactic of hauling in a legal team is different than that taken in free software. However, there is a very split set in the security sector on the appropriate way to find and discuss bugs.
Almost monthly, you'll get flames start up Bugtraq about this. Bugtraq is a full disclosure unix security list - often, raw exploits are posted to it, or tools that someone used to replicate a problem they may have found in software (free or not). Very often, you'll have the author - a vendor, a coder, or a maintainer - or another person bitch about this, because they weren't given prior notice or warnings, etc. Example: The lsof bug of February ( thread starts here).
These threads sometimes, in fact, revolve around people posting for credit or ego/status. While Intel is acting very different, our free movement is not always the clean "thank you" we'd like. However, that's often justified - especially with free software, its better to come bearing patches rather than problems.
Slashdot Mirror
That's just about true, the first couple of weeks. I missed several lectures while sitting in them that way.
Once the novelty runs out though, I've noticed increases in productivity beyond that of just portable computing. I'll note that I'm refering to wireless ethernet with a laptop, and so the flexibility is probably much more - running linux, I can code anywhere. Being at CMU, coding anywhere basically requires AFS access as well, and so a network connection...
But its just a tool, and it takes a while to realize that. While I will admit to sitting in chem lab reading slashdot, I also spend idle moments in lab looking up MSDS forms or coordinating with time-out-of-sync partner.
Sounds like the fun at CMU we've been having, now that the campus is completely covered with wireless (2mb; wavelan) ethernet. There is active research in the Andrew group to do with palmtop stuff as you describe.
(As posted from a vaio while walking home).
You need to stop any activities that cause scar tissue to build up in your hands. Foremost among these is cracking your knuckles. If your a knuckle cracker, you have to stop. The popping sounds is nitrogen liquifying under the pressure. This is bad for your muscles and is the source of your scare tissue.
Where do you get this factoid? Seems rather improbable to me that joint cracking builds up the pressure to liquify nitrogen (quite a large pressure at room/body temperatures). According to a number of sources it is the sound of gasses (including nitrogen) coming out of solution or filling gaps. I'd be interested to know if you have research/references which refute this.
One interesting thing to note that links both of the NASA articles is that apparently the BBC has a faster refresh as well. Consider this story that was just released, which tells us that, while passing a asteroid at 3.5e4 miles per hour is good, apparently you can't collect amazing amounts of data if your camera is pointed in the wrong direction.
:)
The BBC beat the science log. Interesting, though it sounds like a very tired science log writer - with reason! But its too bad we didn't get all that we could. Oh well, we'll have to try again another time
As far as encryption goes, there are some
:)
02.11 compliant things that use 40bit RC4. But really, its not that big a deal under most settings - as its about as secure as ethernet itself. The intelligent, paranoid consumer will be using encrypted channels (ssh) anyway.
As far as lectures, etc. At CMU they have an extensive wireless system (wireless andrew, see wavelan.com for a link to an article about it) which will soon be finished being deployed throughout the campus. Already though, one of the large CS lecturehalls has WavePOINT IIs. This, as well as (and a replacement for) a NetBar system that romes your IP.
But yes, there are nice things about being able to surf during a lecture. And some classrooms being built now (campuses across the country) do have networking infastructures being built in such that teachers can start to take advantage. But wireless stuff is a much better choice, if it does (which it should) become prevalent.
Glad it uses 802.11. Good stuff. We're probably going to see a heck of a lot of these iBooks on campus in the fall as the network is released...
Still wouldn't trade my vaio for one, though
If BeOS doesn't work on a particular G3 system, the user thinks "This CD that I paid for doesn't work. BeOS sucks."
Actually, I have to disagree. I think I do prefer the previous hypothesis that Be uses it as an excuse to pursue the intel market. I'm a be developer, so I get each version when it comes. One of the guys I work for wanted to try it out. Now, be R4 didn't support a whole lot of intel boxes, but it did support his motherboard - it didn't support his Tulip-based ethernet card, even though it was listed on the (very small) "supported chipsets" list.
Be's response was "oh. damn. uh, send us a bootlisting". I won't get into the ugliness of that, but suffice it to say, the end result was just "oh well" and partition delete. They didn't seem terribly concerned - "try the next version". It struck me as funny, of course, because there are perfectly good GPL tulip drivers (becker) out there they probably could have used.
But so in general, I think they'd do fine reverse-engineering the few G3 models out there, and just stating the few models they do support. As with their intel releases : wait on the next version for more drivers and motherboard support. Be is good enough about their releasing schedules and release upgrading such that this is much more of a viable option.
Besides, Be's always been that kind of company.
>I tend to think that in time, the concept of
>channels will disappear.
This, in consideration of an old wired article that struck a nerve
( "The Internet will be just like television:
There may be 60 or 70 main sites out there, but the audience ends
up going to only six or seven on a regular basis.").
And with the Nielsen's trying to demonstrate advertising can
happen in a web-style manner ( Nielsen Comes to the Net)
we've got some pretty wacky paradigm-buzzword throwdowns ahead of us.
Its interesting. This was almost the review I was going to write about the book. I finished it yesterday, in an attempt to get it out of my system. Its one of those books thats so good, as you read it it starts to affect your outlook, and you continually muse over the characters and scenes.
I've been a diehard Stephenson fan for a while. What makes him cool, beyond being an excellent storyteller - action, humor, tech - is that he really does his homework, and he tries to present ideas that he's been working on for a while. This was obvious in snow crash, diamond age, etc.
The most interesting thing about this book, for me, was that it was a nice merger from some of his shorter writings he's done in the last 3 or so years.
Modern Crypto ideas were in Spew. And he clearly knows the underseas cable world, from his lengthy journal ("the hacker tourist"? With GPS signatures?) in Mother Earth Mother Board.
Perhaps his best writing on the points of the modern thread of Cryptonicon (the Crypt and digital currency backed with cash) was in a fictional story in Time (thus, why all of his modern bios give "one of three authors ever to write a fiction piece for Time magazine") of such a bank, called Simoleon. I envision it takes place about 2-3 years after Cryptonomicon I ends... He also has an interest ing non fiction article on the subject in Time.
Anyway, definately worth the time and money. Then read Applied Cryptography and Kahn's Codebreakers. I'm off to track down some Pynchon, as this is now the third book he's been compared to.
GQmpeg actually does look rather nice. It looks motivating enough for me to perhaps customize a skin as well.
.edu bandwidth. After installing the system though, we discovered that his (sizeable) mp3 collection was mostly corrupted - the kind of thing when downloading from http with a misconfig'd webserver. mpg123 would give him the clicks and underwater sounds. He had never noticed these things under windows/winamp.
I will note something in favor of X11Amp, though. I was converting a person a couple of weeks ago to linux. He was going to linux from windows because he liked how I made X look, he was very much into aesthetics, and he figured he would do well to know unix.
His only requirements was the ability to listen to MP3s - its predominantly what he does at home without his
Apparently winamp does on the fly repairing.
So does X11amp, which made him, and me, happy. Because CQmpeg relies on mpg123, that's something which is apparently significant which it lacks.
Just to add/refute abit on the 'obvious part' of your comment. The tactic of hauling in a legal team is different than that taken in free software. However, there is a very split set in the security sector on the appropriate way to find and discuss bugs.
Almost monthly, you'll get flames start up Bugtraq about this. Bugtraq is a full disclosure unix security list - often, raw exploits are posted to it, or tools that someone used to replicate a problem they may have found in software (free or not). Very often, you'll have the author - a vendor, a coder, or a maintainer - or another person bitch about this, because they weren't given prior notice or warnings, etc. Example: The lsof bug of February ( thread starts here).
These threads sometimes, in fact, revolve around people posting for credit or ego/status. While Intel is acting very different, our free movement is not always the clean "thank you" we'd like. However, that's often justified - especially with free software, its better to come bearing patches rather than problems.
Of course, regardless, our bugs get fixed faster.