Haha...1.4 Meg zipped for a program to translate Binary to Text. Doncha just love VB?
Re:Snow Crash is still my favorite
on
The Diamond Age
·
· Score: 1
Mother Earth, Motherboard is an excelent article. That was actually my first introduction to Stephenson, and it was a couple years before I made the connection that he wrote that. I was reading a Bio in a review for Cryptonomicon and saw that article mentioned. I had to reread it.
We'd love to have you, no interview required. Just fly on over tomorrow. I'll be waiting at the airport. Oh, and as a signing bonus, you'll be recieving some beachfront property in Arizona. We can't wait to have you on board.
Standard Disclamer: IANAL I think the standard agreement (the only thing I'll ever sign anyway) simply states that anything developed using company resources is the property of the company.
besides that, there is no way any one company could legaly usurp the Linux kernel. The original code was written long before Transmeta, and Linus didn't write the whole thing anyway. Additionally, many (maybe all) GNU projects require a release from your employer before they'll accept your code. I'd provide a link stating as much, but I don't have the time right now...sorry.
Paul Allen hasn't had much to do with MS (other than owning stock) for years. Besides, even if that article you linked to made the statement, "Microsoft invested in Transmeta"(which it didn't), that's not proof. That's some journalist making a statement.
Do I have to spell everything out?! Follow the damn link I supplied to find out what is meant by labeling. Well...you apparently didn't want to before, so I might as well quote that part to you as well...this is at the end of the page: This statement, however, does not exclude the adoption of organizational schemes designed as directional aids or to facilitate access to materials.
I would like to think that people on/. have the brains to extrapolate this sort of thing on their own...but sometimes I wonder.
Tell me about it. I had to scrap my plans to create a fleet of killer Lego robots controlled by my Palm. It violated the licence agreement and they threatened to sue.
The second, at least in my experience, is the desire to meet someone who shares interests with one's self. "Geeks" tend to put a very high value on not only intellegence, but technical aptitude(sp?). Women in technology fields are rare. That, combined with problem one, makes for a pretty lame time for any women brave enough to venture into what is, sadly, a male dominated arena.
In the past I tried very, very hard to meet someone who would know what the hell I was talking about when I told them what I was working on. I, for one, gave up and met a classics major. That way we can speak foreign languages at each other and it pretty much evens out.:)
Better come up with a better explanation. One cannot be "mildly afflicted by downs syndrome." Down's Syndrome is a specific defect in which there is an extra 21st chromosome. Either you have it, or you don't (although the severity of its symtoms vary).
Hmm..I took that down syndrome remark as sarcasm. Then again...maybe geek syndrome is clouding my judgement.:)
I wonder what the mode of propulsion will be. I suppose all you'd really need is a fan or something to move it around...Just brainstorming, I'd say compressed air might be better though.
(Sigh), let me copy over the first draft(sans HTML). This was the original message. I deleted the Linux != OSS because I thought it was a bit redundant.
Original (un-edited) message:
Wow, in your haste to flame Microsoft, you completely failed to understand his message.
Read this again...carefully: It seems that the corporate and open-source development models have at least one flaw in common: insufficient documentation.
He said corporate(Microsoft) and open-source (Linux) have one flaw in common (BTW, I know Linux != Open Source. I'm trying to reach a particular mindset here.). Documentation is a means, not an end. Documentation doesn't necesarily make better software...it gives developers the ability to make better software. As a result, the "good software potential" for every developer, whether open or proprietary, benefits. That, my rash friend, is the point he was trying to make.
If one does NOT understand the source code one does _NOT_ have any business messing with it. Documented or not dumented. Period.
Why do people always revert to this? This has nothing to do with the discussion at hand. Appropriate documentation makes it easier to understand the source in the first place! I am loathe to make broad sweeping statements, but, I must say this: People who don't understand the value of good documentation are missing a valuable and important aspect of programming. This "rambo" coding does nothing but degrade code quality.
Sorry, but this is a recent "issue" with me because I've had to pick up the pieces from some asshole who thought he was too good to research and document what he was doing before he went coding some difficult and sensitive code. Result?? I rewrote the whole damn thing...properly. I may have been able to reuse some of what he had, but there was no documentation. So I was forced to start over.
People who don't think documentation is valuable are coding in a black box. End of Story.
Though I find your comments insulting, I will say this...Good code is a combination of easy to read code and appropriate documentation. No one said anything about documentation being a substitute. You made that up.
Reference Steve McConnell's excellent book, "Code Complete". Specifically chapters 18 and 19: "Layout and Style" and "Self-Documenting Code" respectively.
because of this one problem i think his maps should look like a tree and not a star. with a tree you get the more realistic view of only ONE viewing point I like that idea. But you can tell that this was mapped from one viewpoint. That big bundle is where the traceroutes must've started. Since that big bundle maps to Cable and Wireless, that must be where Bell Labs gets their pipe!
If I remember right, the doublespace thing wasn't quite so clear cut as this sounds. This would be the equivalent of Microsoft buying one copy of Stacker, then making a bunch of copies, labeling them as doublespace, and selling them.
Slashdot Mirror
#include
t |=(c=='1')?(1i):(isspace(c))?putc(t,st dout),i=8,t=0:0;}
#include
void main(){int c,i=8,t=0;while(((c=getc(stdin))!=EOF)&&(i==i--))
#include
= (c=='1')?(1
#include
void main(){int c,i=8,t=0;while(((c=getc(stdin))!=EOF)&&i==i--)t|
How about:
t |=(c=='1')?(1i):(isspace(c))?putc(t,st dout),i=8,t=0:0;}
void main(){int c,i=8,t=0;while(((c=getc(stdin))!=EOF)&&(i==i--))
Haha...1.4 Meg zipped for a program to translate Binary to Text. Doncha just love VB?
Mother Earth, Motherboard is an excelent article. That was actually my first introduction to Stephenson, and it was a couple years before I made the connection that he wrote that. I was reading a Bio in a review for Cryptonomicon and saw that article mentioned. I had to reread it.
I've mirrored this on http://www.sarahandcasey.com/mirrored/
Hi John, this is Mr. Ditzel.
We'd love to have you, no interview required. Just fly on over tomorrow. I'll be waiting at the airport. Oh, and as a signing bonus, you'll be recieving some beachfront property in Arizona. We can't wait to have you on board.
Standard Disclamer: IANAL I think the standard agreement (the only thing I'll ever sign anyway) simply states that anything developed using company resources is the property of the company.
besides that, there is no way any one company could legaly usurp the Linux kernel. The original code was written long before Transmeta, and Linus didn't write the whole thing anyway. Additionally, many (maybe all) GNU projects require a release from your employer before they'll accept your code. I'd provide a link stating as much, but I don't have the time right now...sorry.
Paul Allen hasn't had much to do with MS (other than owning stock) for years. Besides, even if that article you linked to made the statement, "Microsoft invested in Transmeta"(which it didn't), that's not proof. That's some journalist making a statement.
Do I have to spell everything out?! Follow the damn link I supplied to find out what is meant by labeling. Well...you apparently didn't want to before, so I might as well quote that part to you as well...this is at the end of the page:
/. have the brains to extrapolate this sort of thing on their own...but sometimes I wonder.
This statement, however, does not exclude the adoption of organizational schemes designed as directional aids or to facilitate access to materials.
I would like to think that people on
GnrcMan
Tell me about it. I had to scrap my plans to create a fleet of killer Lego robots controlled by my Palm. It violated the licence agreement and they threatened to sue.
Hmmm, if you combine this with the palm's ability to steal auto security codes, maybe you could make a robot that goes around stealing cars! >:>
Generic Man
The purpose of the v-chip is to block content. blocked content=censorship.
Regardless of that, anything which arbitrarily labels content is censorship. The mere act of labeling something is a very real form of censorship.
Here's what the ALA(American Library Association) has to say about labeling: (full text can be found here)
Labeling is an attempt to prejudice attitudes and as such, it is a censor's tool.
They have much more to say on the matter, so I recommend following the link to the full text.
Generic Man
As far as the proposals, etc., let me offer my views (being of the male persuasion, I guess I'm probably qualified).
:)
There are a couple factors coming into play, the first being a lack of social graces.
The second, at least in my experience, is the desire to meet someone who shares interests with one's self. "Geeks" tend to put a very high value on not only intellegence, but technical aptitude(sp?). Women in technology fields are rare. That, combined with problem one, makes for a pretty lame time for any women brave enough to venture into what is, sadly, a male dominated arena.
In the past I tried very, very hard to meet someone who would know what the hell I was talking about when I told them what I was working on. I, for one, gave up and met a classics major. That way we can speak foreign languages at each other and it pretty much evens out.
Better come up with a better explanation. One cannot be "mildly afflicted by downs syndrome." Down's Syndrome is a specific defect in which there is an extra 21st chromosome. Either you have it, or you don't (although the severity of its symtoms vary).
:)
Hmm..I took that down syndrome remark as sarcasm. Then again...maybe geek syndrome is clouding my judgement.
I wonder what the mode of propulsion will be. I suppose all you'd really need is a fan or something to move it around...Just brainstorming, I'd say compressed air might be better though.
Hmmm...any other ideas?
GnrcMan
Ummm...Bruce Schneier is the author of "Applied Cryptography". If anyone has impecable crypto credentials, it's him.
(Sigh), let me copy over the first draft(sans HTML). This was the original message. I deleted the Linux != OSS because I thought it was a bit redundant.
Original (un-edited) message:
Wow, in your haste to flame Microsoft, you completely failed to understand his message.
Read this again...carefully:
It seems that the corporate and open-source development models have at least one flaw in common: insufficient documentation.
He said corporate(Microsoft) and open-source (Linux) have one flaw in common (BTW, I know Linux != Open Source. I'm trying to reach a particular mindset here.). Documentation is a means, not an end. Documentation doesn't necesarily make better software...it gives developers the ability to make better software. As a result, the "good software potential" for every developer, whether open or proprietary, benefits. That, my rash friend, is the point he was trying to make.
If one does NOT understand the source code one does _NOT_ have any business messing with it. Documented or not dumented. Period.
Why do people always revert to this? This has nothing to do with the discussion at hand. Appropriate documentation makes it easier to understand the source in the first place! I am loathe to make broad sweeping statements, but, I must say this: People who don't understand the value of good documentation are missing a valuable and important aspect of programming. This "rambo" coding does nothing but degrade code quality.
Sorry, but this is a recent "issue" with me because I've had to pick up the pieces from some asshole who thought he was too good to research and document what he was doing before he went coding some difficult and sensitive code. Result?? I rewrote the whole damn thing...properly. I may have been able to reuse some of what he had, but there was no documentation. So I was forced to start over.
People who don't think documentation is valuable are coding in a black box. End of Story.
Generic Man
Though I find your comments insulting, I will say this...Good code is a combination of easy to read code and appropriate documentation. No one said anything about documentation being a substitute. You made that up.
Reference Steve McConnell's excellent book, "Code Complete". Specifically chapters 18 and 19: "Layout and Style" and "Self-Documenting Code" respectively.
I guess you can think of it as looking down at a (somewhat off-centered) tree from the top.
because of this one problem i think his maps should look like a tree and not a star. with a tree you get the more realistic view of only ONE viewing point I like that idea. But you can tell that this was mapped from one viewpoint. That big bundle is where the traceroutes must've started. Since that big bundle maps to Cable and Wireless, that must be where Bell Labs gets their pipe!
That's cable and wireless. Since this was mapped using traceroutes, that would (obviously) mean that bell's pipe is from C&W.
If I remember right, the doublespace thing wasn't quite so clear cut as this sounds. This would be the equivalent of Microsoft buying one copy of Stacker, then making a bunch of copies, labeling them as doublespace, and selling them.
One of the cool things about the Alpha is it's flexability. It can do either. But it doesn't really matter from a performance standpoint.