I guess it depends how you define a fork. If you consider a patch set a fork, then most distributions fork a large majority of the software they ship. And for the kernel, there are actually many many forks--it's the development model they actively encourage with git.
Consider: the areas where the green light didn't illuminate would be black, if it weren't for the fact that the red and blue light were illuminating that region from a different angle. The red and blue would thus combine to form a purple shadow. Repeat the same simple game for the other directions, and you get differently colored shadows.
Less snarkiness, more thought, and you might actually post a useful reply.
I'll be the first one to admit that for convoluted, multiple-point replies, putting it all on top is completely ridiculous. That doesn't make top-replies inappropriate for every circumstance, though. Sometimes a conversation is so simple that even mouth-breathing idiots can keep all the context in their head at once. It may even be a rather long and wordy conversation, as long as it can fit in ones' head. In these situations, I actually find it quite tedious to scroll through a bunch of stuff I've already read (even worse, a bunch of stuff that I've written) just to get to the salient part of the matter. Say what you will about top-replying, but there are times when it's just more convenient. Of course, the times when it's *not* more convenient make it quite a bit, er, inconvenient.
I think the reason basic browsing has remained unchanged is because it works, and works well. Clicking words to open up new (and, ideally, related) pages is a pretty neat idea. The incremental changes you speak of have combined to create quite a nice browsing experience. Tabs, piemenus, etc... it all works pretty smoothly. Perhaps when there's a big reason for change, change will come about.
As far as Andreessen's comments... he should either put up or shut up. Maybe he could reveal his 18 groundbreaking ideas and let the mozilla hackers roll them in. Or he could actually do some real coding himself. Either way, making profound comments, such as "Navigation is an embarrassment. Using bookmarks and back and forth buttons -- we had about eighteen different things we had in mind for the browser," is an entirely useless endevour.
Despite some major upheaval, perl 6 is going to retain the spirit of perl. A large amount of the syntax is going to stay the same. That which is changing will probably make the language easier to learn, if anything. The new features may indeed make it more difficult to learn the advanced facets of the language, but the simple cases will remain simple -- that's engrained in the perl culture.
I was under the impression that there were also gonna be episodes 7, 8, and 9. So TPM is not actually the beginning of the end, it's not even in the middle. But of course my I could be wrong about 789.
I don't know about anyone else, but I read about this "format war" about three months ago in "Home Theater Magazine." Maybe I am the only person with a subscription?
Maybe JVC's "real" name IS Matsushita? I always thought that JVC created VHS too, but I think maybe JVC is a marketing name for Matsushita.... think about it, who would buy a Matsushita TV? heh
don't take this the wrong way... but it always amazes me how people post (or write in IRC) these wonderful, long responces that have lots of useful information in them, but very little puncuation or attention to spelling.... =)
Then why name it Perl6?
If it's a different language, give it a different name!
Quite simply, because the guy who first created Perl still wants to call it Perl.
I guess it depends how you define a fork. If you consider a patch set a fork, then most distributions fork a large majority of the software they ship. And for the kernel, there are actually many many forks--it's the development model they actively encourage with git.
Before you paste, turn on paste:
Then go to insert mode and paste your little heart out. When you're done, turn paste off:
Hello, did someone forget the difference between a movie and a novel?
Consider: the areas where the green light didn't illuminate would be black, if it weren't for the fact that the red and blue light were illuminating that region from a different angle. The red and blue would thus combine to form a purple shadow. Repeat the same simple game for the other directions, and you get differently colored shadows.
Less snarkiness, more thought, and you might actually post a useful reply.
I'll be the first one to admit that for convoluted, multiple-point replies, putting it all on top is completely ridiculous. That doesn't make top-replies inappropriate for every circumstance, though. Sometimes a conversation is so simple that even mouth-breathing idiots can keep all the context in their head at once. It may even be a rather long and wordy conversation, as long as it can fit in ones' head. In these situations, I actually find it quite tedious to scroll through a bunch of stuff I've already read (even worse, a bunch of stuff that I've written) just to get to the salient part of the matter. Say what you will about top-replying, but there are times when it's just more convenient. Of course, the times when it's *not* more convenient make it quite a bit, er, inconvenient.
I think the reason basic browsing has remained unchanged is because it works, and works well. Clicking words to open up new (and, ideally, related) pages is a pretty neat idea. The incremental changes you speak of have combined to create quite a nice browsing experience. Tabs, piemenus, etc... it all works pretty smoothly. Perhaps when there's a big reason for change, change will come about.
As far as Andreessen's comments... he should either put up or shut up. Maybe he could reveal his 18 groundbreaking ideas and let the mozilla hackers roll them in. Or he could actually do some real coding himself. Either way, making profound comments, such as "Navigation is an embarrassment. Using bookmarks and back and forth buttons -- we had about eighteen different things we had in mind for the browser," is an entirely useless endevour.
Perl programmers usually call these "my-variables" by their proper name: lexicals.
Despite some major upheaval, perl 6 is going to retain the spirit of perl. A large amount of the syntax is going to stay the same. That which is changing will probably make the language easier to learn, if anything. The new features may indeed make it more difficult to learn the advanced facets of the language, but the simple cases will remain simple -- that's engrained in the perl culture.
You just don't get this amount of free documentation in the Perl or Python worlds.
Before making such bold claims, you should probably check out man perl, and the plethora of man pages which are listed therein.
Sounds like a horrible place to work. Do they allow smiling? What about yawning? I'm sure laughing is a huge no-no. :)
Poetic justice that you think BSD is dead. What makes you think it will be any different than Slackware?
I was under the impression that there were also gonna be episodes 7, 8, and 9. So TPM is not actually the beginning of the end, it's not even in the middle. But of course my I could be wrong about 789.
I don't know about anyone else, but I read about this "format war" about three months ago in "Home Theater Magazine." Maybe I am the only person with a subscription?
no that is not the real reason. they have been talking about audio DVD virtually since DVD was being made
Maybe JVC's "real" name IS Matsushita? I always thought that JVC created VHS too, but I think maybe JVC is a marketing name for Matsushita.... think about it, who would buy a Matsushita TV? heh
jeez, why all the anti-katz sentiment floating around here?
:P
it seems like he didn't even WRITE that article, but yet you guys still flame him? it's quite sad actually... i don't think he's that bad
don't take this the wrong way... but it always amazes me how people post (or write in IRC) these wonderful, long responces that have lots of useful information in them, but very little puncuation or attention to spelling.... =)