Slashdot Mirror
The Gnutella War: Free vs. Commercial
Anenga writes "Slyck has an interesting interview with Mike of Shareaza regarding Gnutella2 (see older stories), where he expresses his opinions on how Gnutella2 has been recieved within both the user and developer community. The reaction from the top commercial clients, Limewire and BearShare, on Gnutella2 (as seen in the GDF and elsewhere) is that they will not support it because of how it was presented, however, Gnucleus (free, open source) plans to support it and feels the GDF is not seeing the bigger picture. John Marshall of Gnucleus says 'Now it's more like "Free vs Commercial" clients, which [the latter] would rather develop their own next generation protocol (which would probably never happen).' The article in short: Shareaza will keep Gnutella2 open/free, it's already been very successful with a 80-100k growing userbase, Gnutella2 was *not* based on Limewire's GUESS proposal and is in fact very different from it and Shareaza will continue to both support the original Gnutella ('G1') and of course G2."
So when they finish with the G3 they are going to use it to power iMacs right??
My question would have to be why Limewire/Bearshare/etc have flat out decided to absolutely not support the new protocol, when it seems fairly obvious that both protocols could be implemented within one client. I understand their wish perhaps develop their own proprietary protocol, but this seems like treading water to me. SPECIFICALLY in a P2P architecture, wouldn't more protocols be a direct correlation to access to more files, and in that case, an increase in popularity, quality and then, in turn, profitability?
Sig.i>
In recent years p2p systems have caught the fancy of CS researchers. Gnutella always gave the feeling of being designed more by hackers than people with a sound theoretical base.
Has Gnutella2 taken cue from the recent research publications?
What I don't understand is how desperate you have to be to go commercial with application which is used mainly for illegal file sharing. I mean, cmon people are sharing mp3's, divx-ripps, applications and games. Not like somebody would actually download mpegs of my pets or my kid brother's birthday. Not that I am preaching, but it was kinda gray activity, we all know what it is used for. Going commercial is going to be the death of it, but hey they, are just lazy and are trying to make a living without having a proper job. I wish somebody would pay me money to change desktop backgrounds in my blackbox, and play around with my Eterm, because I think it's fun. I kinda grow out of that idea long time ago, and had a nice job since... Get a life.
I think the paragraph that pays for me is:
"The GDF's first reaction was negative because they claimed it used the same ideas from other proposals. Once the protocol specs were released this was obviously false, but the GDFs reaction was still negative so Mike has not bothered to release the rest of the specs.
What it really sounds like is that the commercial entities are balking for something. That is, they are negotiating with their veto.What specifically they want out of this, whether it is a voice in the process or perhaps a cut of the action, I'm not entirely clear. I'd like more on what the author of the article called the 'backstory'.
--- have you healed your church website?
Free software can be commercial. You mean proprietary.
...Napster?
;)
I just say: "In former times..."
My spirit takes a journey through my mind...
The published interview is about as balanced as a Linux press-release issued by Microsoft. A couple of points to consider:
- Shareeza has implemented a new protocol and released it soely on it's own client. It hasn't publish any hard details and it's dubbed it "Gnutella2" with no support from existing supporters of the Gnutella protocol.
- The existing clients are a bit upset that Mike has done this, and his actions since, but doesn't really have an opinion on the technology becuase its specifications have not been released.
This seems to me as a fairly egotistical kid hijacking the Gnutella name for his own purposes, then charactising eveybody else as bitter about his wonderful new tchnology.
Theworse thing is that the GDF even pay attention to this fellow, they should just igonre him rather than waste their energy on being upset at his lack of manners.
Reliable, Great Value Hosting: $7.95/mo 2.4G/120G
In about 10 years from now, Russia will be the freest country in the world I guess. America is the next police state, Europe does its best to fit American needs, China's people are all prisoners anyway of their government... Oh, Russio is oppressive, too. But they do not have the money to control and dragoon their hole state, so overall it will be the freest country...
Why do you need PING/PONGs in a network where resource discovery (i.e. files) is more important than host discovery? Pings/Pongs would make sense if it were a UDP based protocol, but the Gnutella protocol uses TCP--so why do I need to check if a host is still there? Who really cares? It's content that I'm looking for, not a particular servent.
I agree that you have a point about "proprietary," but I think the word "commercial" in the article and synopsis is accurate. There are three types of Gnutella clients:
a) Those which are free to download, free to use, and open-source
b) Those which cost money to download and use (e.g. "BearShare Pro")
c) Those which are free to download, free to use, closed-source, and invariably "ad-supported"
It's category c being referred to as "commercial" Gnutella clients. They're the ones who are in it to make some sort of a profit or at least to generate revenue - the software comes bundled with some adware or another - thus they are indeed "commercial" in nature.
"BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
Raphael Manfred: "I'm speaking only for myself here, but I will NOT support Mike's protocol unless I'm forced to do it. I was neutral-positive when this saga started, but Mike ruined it all by his stubborn attitude, and I'm now rather hostile-negative.
If there are good ideas in what he did, you can rest assure that we'll end up using them. He'll even get credit for those ideas, but it will be within the Gnutella network."
"tonygeek": I am sceptical. All signs are there that (Gnutella 2) is one strictly commercially driven undertaking/experiment (possibly by a very large company pulling all the strings from behind) and that somebody wants to experiment with his own network attached to one that is already up and functional.
"fungusbuttocks": I am another who is against Mike's use of the "Gnutella 2" name, because he simply did it as a marketing strategy (...)
If Mike releases a nicely documented unambiguous protocol doc when he's finished testing the beta, and the protocol appears to have some sort of mathematical merit to it, we should support the protocol.
Looks like the situation's less one-sided than the writeup makes it seem.
Nice to see that people are still out there chipping away at making Gnutella a smooth P2P network. It sure as hell needed some work. I haven't had to use Gnutella since KaZaA was released, but I would be interested in the opinions of anyone who has used Gnutella recently.
1) The developers opposing Gnutella2 seem to be the LimeWire developers (their client is open-source under the GPL see www.limewire.org), gtk-gnutella (GPL as well, see gtk-gnutella.sf.net) and BearShare (not open-source). So calling this a war between free and commercial is stupid, especially since Shareaza IS NOT open-source.
2) LimeWire and the other opposed Gnutella2 for a variety of reasons. They didn't want a new message format where the old would still work, they preferred the GUESS search algorithm over the Gnutella2 search and they said they would not accept the name because if there ever was a Gnutella2 it should be announced by the whole GDF (Gnutella Developer Forum) and not by a single developer.
3) After Shareaza developer Mike Stokes has shown an attitude towards the GDF that could very well be called hostile, things got a little out of hand. The GDF now demands that Mike hands the Gnutella2.com domain to the people running Gnutella.com. Mike won't do so and Raphael Manfraedi (gtk-gnutella) has even proposed to start blocking gnutella2 enabled clients.
4) Shareaza fan's like the one who posted this news story helped a great deal to create the current situation by flaming on the GDF, posting rumors and lies (like Shareaza had 80k-100k users - even Mike Stokes denied that) on various news sites and in gnutella-centric forums.
5) The Gnutella2 protocol is still an undocumented proprietary extension.
Have you tried any of the stripped down version of Kazaa like KazaaLite? I feel that Kazaa has a better engine in practice than the big G but without being stripped down to the bare essentials, Gnutella definately wins. However, look at Kazaalite vs. Gnutella and there's quite a bit to like on the streamlined kazaa. Mostly tho, Gnutella (when I used it) was a bit bigger of a bandwidth hog than Kaz is. (however, i am NOT an ethernet techie, nor do I profess to know if this is due to my ignorance at implementing either program).
Find out about my new childrens book: SS Death Camp Criminal Batallion Go To Monte Carlo For The Massacre
Mike makes the point that due to the increase in the intensity of compettion between the different p2p clients and networks that each network will have a limit to how big they can grow.
I have used Shareaza 1.7 beta and am very impressed with it's performance (it tells you when you are connected to a G1 hub or G2 hub so it's very easy to see the difference). I strongly believe that if Kazaa gets litigated out of existance that the best alternative for Kazaa users is Shareaza. Shareaza could very soon be king of the hill.
The problem ... probably is power, money, image, ...
... BearShare and LimeWire ... are not completely free ... both are full of ad/spyware (in free version). .... has created so a great, new, advanced, ecc... in so little time. ... this new protocol ... G2... has been the TOP!
Do you know certainly that both servents
Probably is not good for BS e LW that a young programmer
And the last thing
What I don't understand is why everyone actually talks about `gnutella2' here. There are many different P2P protocols
available. This guy named his gnutella2 and now we should believe it actually is the second version of the gnutella protocol?
Shouldn't we have a discussion about what makes a good protocol before adopting it as a (pseudo)standard?
In this context I'm afraid the commercial vendors might have a point.
There's no honor amongst thieves.
What right does anyone have to take a commercial stake in the theft of Intellectual Property? This is common theivery. Nothing more.
At lest the 'keep it free' hackers are honest about it.
You know, the saddest thing about that is that I actually believe that you're right...
So, how much does one have to pay to move to Russia these days? And do they have decent and cheap internet connections?
In Slashdot Russia, you are free!
Free vs. Commercial...?
And when has commercial ever won out to free when it comes to file sharing, music specifically? Doesn't mean they're not welcome to try, but if history is any indication, somebody is on the wrong side of the profit-8ball (spyware and banner adverts not withstanding, of course...)
You need a FREE iPod Nano
Shazaa is so feature-rich and works so well because:
***The developer(s) don't wait for committee to implement backwards-compatible extensions to the protocols***
A lot of features that have been proposed and discussed to death on the gdf and here, the Shazaa developer(s) has already made happen!
Some such features:
1. Compression of gnutella peer/ultrapeer/leaf traffic a la zlib. (my little cablemodem that used to be able to support up to 110 connections now supports up to 290 connections as ultrapeer with compressed streams.)
2. Tigertree hashing - tigertree, as well as e-donkey2k, sha1 and md5 hashes (i believe) are all supported. Not sure if shazaa actually verifies each chunk against the tigertree, but it _should_.
3. Ultrapeer "crawling" via udp queries.
4. support for gnutella: , ed2k: , and magnet: urls, all of which are also integrated into the shell.
The moral:
**As long as you don't break the existing stuff,**
If standards groups can't decide on standards, go ahead and add your own improvements. Let the improvements be accepted or rejected by the natural meritocratic movements of the open-source/open-standards worlds.
Lots of neat-o technology has been wasted effort because standards groups couldn't agree on the standard before the technology was outdated. (e.g. ip/lan.e over atm).
The makers of those other two *crippled*,*crapwar-burdened* semi-commercial clients are probably upset because their client doesn't have these nifty new features. And the best part: Shareaza hasn't (yet) broken the existing gnetwork.
(I have no problem with commercial products. they're great. support is great. my problem is with "free"ware that bundles crap-ware for the uneducated masses.).
Gnucleus and Shareaza have been the best gnutella peer apps on the windows side because they
1) implement new features and new standards promptly,
2) don't abuse the gnet, and
3) don't carry any excess baggage.
and for the moment, this long-time-gnucleus-faithful-user has gone shareaza untill gnucleus implements these new features. and shareaza is ooohhh-soo-stable.
Again, the point:
**As long as you don't break the existing stuff,**
implement your own improvements to the specs. Let the improvements be accepted or rejected by the natural meritocratic movements of the open-source and open-standards worlds.
Committees are good when they are productive. In this case, the gnutella standards have been outgrown in some respects by a relative new-comer with great ideas, fast fingers, and healthy respect for existing standards and infrastructure.
mmmm. I'm sure the shutdown of Russia last independent TV station makes them free, especially when the shutdown was allegedly ordered by their president, Putin.
1. Compression of gnutella peer/ultrapeer/leaf traffic a la zlib. (my little cablemodem that used to be able to support up to 110 connections now supports up to 290 connections as ultrapeer with compressed streams.)
Proposed and implemented first by gtk-gnutella. However LimeWire is also using some form of compression.
2. Tigertree hashing - tigertree, as well as e-donkey2k, sha1 and md5 hashes (i believe) are all supported. Not sure if shazaa actually verifies each chunk against the tigertree, but it _should_.
md4/md5 hashes won't be used by others because it creates a huge redundancy. If you have two files, one with a md4 has the other one with a sha-1 hash you can't make sure if they have the same content or not. As far as tigertree hashing is concerned, nobody ever said it wouldn't be implemented after it was proposed by Gordon Mohr. LimeWire has it on their to-do list for example.
3. Ultrapeer "crawling" via udp queries. Even that was decided to be used before Gnutella2 was released.
My problem is, that Mike Stokes knew those features would be implemented but he didn't take part in the discussion, he kept his ideas for himself to be the first one implementing them. The GDF was productive (it produces the proposals more quickly then the GDF members are implementing them).
Shareaza hasn't (yet) broken the existing gnetwork.
The way you say it, it sounds like that is just a matter of time. - By the way, Shareaza is sending corrupt alternate locations, so it is breaking the network.
I've seen the light. I've been playing around with Gift / OpenFT lately, and the performance blows the doors off of anything *tella based, plus the protocol is open, well documented, and the clients are spyware free.
What I'm trying to understand is why does everybody and their brother build a brand new P2P network (or try to)? What's the point? There's exactly $0 to be made off of it. More network just mean that each one is not as good, since files are spread out across multiple networks, not just one. Kazaalite works just fine. Why switch? This is another geek vs. businessman thing where a bunch of geeks are creating things for no apparent reason whatsoever other than the fact they may think it's "cool".
Load up youre boot codes and account lockouts and give em hell :D
I'm not a Shareaza fan, But I think Mike is within his rights to call his protocol Gnutella2 if he wishes.
I've been following this thing for a while now and this is my view. Gnutella was made by a group of developers at nullsoft, right? They never trademarked the name and eventually abandoned the technology all together, I believe.
GDF is an ad hoc group put together to continue the development, but have no special rights concerning gnutella.
Love him or Hate him, I think Mike is perfectly in his rights to call his protocol Gnutella2. It's not a very nice thing to do, but he is within his rights.
The GDF should accept this, realize that at any time someone can create a 'Gnutellan' and all the GDF need to do is that when describing their protocols, specify the version that they created and/or endorse. eg 0.6, etc.
Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW
They've clearly stated that they will not support the G2 but along with KAZAA have settled on the bfip02 protocol. And why isn't anybody documenting the feud between Limewire and Bearshare over xf88?
First of all, if this is "open" (free) versus "closed" (commercial), WHERE is the Gnutella 2 specification? "It's coming". I mean that's one of the oldest notions in the free software community, it is NOT open source (or protocol) until the source (or protocol) is actually open! When (if) the specs come out, I'll believe it.
Currently the Gnutella "1" (aka v0.6) specs are published, and functioning in many clients, and the Gnutella 2 protocol is not to be found anywhere. It's true that Shareaza does not (yet) have ads and Limewire and Bearshare do, but Shareaza's source is closed, unlike Limewire's. Calling Shareaza open and free and Limewire closed and commercial is kind of silly, especially since Shareaza source is closed and Shareaza G2 protocol is (currently) closed.
Second of all, Gnutella is a coalition of the most popular Gnutella developers - Limewire, Bearshare, Gnucleus, Xolox, GTK-Gnutella, Morpheus (sort of) and so forth. Currently, they call the Gnutella version they have version 0.6. Along comes a new client Shareaza, and they try to hijack the Gnutella name and call it "Gnutella 2".
I hope Mike comes to his senses. Shareaza is a decent p2p client, and has been a positive thing for Gnutella, and he can do what he wants, but I am uninterested in any new protocol until protocol specifications are published, and trying to seize the Gnutella name is kind of silly as well, especially since the protocol he wrote (and has yet to share specifications of) is so radically different than Gnutella. He can switch to his new protocol if he wants, but he should stop calling it an open protocol until he publishes the specifications, and he should consider a name aside from "Gnutella 2".
This past summer I joined the RFC-Gnutella project, whose goal should be obvious from its name. They already had some preliminary drafts that still required tons of work, and I stated that I would go through the latest one and try to not only make it more presentable (fixing spelling and grammar and such) but also try to suggest any improvements I could think of to the actual protocol outlined in the draft. After taking a few months to go through just the first part of the protocol with a fine-toothed comb, I submitted everything. When it came to my suggestions regarding the protocol itself, however, the response was basically 'we're only documenting what existing vendors do, not doing anything new (or better) or changing anything.' If you look at the mailing list archives I'm sure my posts are still there. Unless there have been posts that just haven't been getting to me, the last one on the whole list should be the one from me months ago telling them that I wanted to make the protocol as good as possible, not be someone's secretary and document what they already did for them, so I was no longer interested. I also mentioned that I might possibly implement my ideas in the future, although I haven't done so yet and didn't throw out any names like Gnutella2. But given a mindset like what I encountered, it is not surprising that someone wishing to change the protocol (for better or for worse, hopefully for the former) who is not one of the big established names like BearShare or LimeWire would have to go out on their own, not that I agree with all this Gnutella2 crap. Interestingly, the last update to the RFC-Gnutella draft was about six months ago now, and the last post to the mailing list (mine if I'm not mistaken) wasn't long after that. Standardization doesn't seem to be a very high priority around there. Who needs good standards, or even standards, when you're in a position that whatever you do is 'the standard.'
GNU Internet File Transfer
http://gift.sourceforge.net/
" What is giFT, you ask? giFT is a modular daemon capable of abstracting the communication between the end user and specific filesharing protocols (peer-to-peer or otherwise). The giFT project differs from many other similar projects in that it is a distribution of a standalone (platform-independent) daemon, a library for client/frontend development, and our own homegrown network OpenFT. "
This is a great network, where you find many oggs, downloads actually work (up to 600kb/s!!) and finding files is really fast. Lots of altruists are using it. Plus: You have to compile it from CVS, which prevents idiots from using the network. On the average each user shares 8 GB!
Moritz
The anti-G2 lot isn't just lacking reason, they're contradicting it. They would cut off their nose to spite their face (or Mike Stokes). This is the mentality we're dealing with:
"...as long as gnutella2.com exists in its current form, you are all fifty cent whores that got pimped by Slimy Mike."
Childish and spiteful. This is not the attitude with which to reach compromise and solve problems. Name calling? Are we freakin' twelve?
In the end, the G2 opponents are being obstinately selfish, and the heated, illogical emotion they're injecting into this discussion is hurting far more than helping the community by delaying the widespread implementation and deployment of a superior protocol that has already been tested and used effectively in public hands.
I don't care what anyone personally thinks of Mike, his opinions, or how he's handled the unleashing of Shareaza on the world. The only working reason in this argument is the Gnutella2 mark, and the G2 opponents seem to be desperately clinging to it, as if this is the only way they can oppose G2 without showing their true feelings, which I suspect have to do either with personal conflicts such as Shareaza stepping on the feet of other Gnutella players. Surely its a sign that the Loud Voices complain that G2 will only cause a schism, but then turn around and talk about Gnutella3 as a way of battling G2. Would I be wrong to construe this as an indicator of where certain peoples' intentions really lie?
The G2 opponents are so busy thinking of creative ways to sanction Shareaza and Mike Stokes that they've not given a single thought to what course of action would most benefit the community of users in this situation. As a Gnutella user and developer, I say this spurious, wasteful behaviour must stop now before it gets any worse. I suggest they regain their emotional composure and grow the hell up.
For me, this is an awkward situation. I'm a proponent of all things open and Free, and I should support the GDF in this conflict else violate my principles. But my principles also encompass the proper behavior of a rationally thinking human being who wants to successfully communicate with others of his kind. In this regard, I find the behaviour of some GDF key players to be so repulsive that I like myself less when I support a protocol backed by propaganda-spewing, egotistical drama queens than when I support a protocol that's only quasi-open, or less, as is currently the case. (I _really_ hope Mike opens up G2. It would be such a graceful way of pulling the rug out from under these fools, and beyond that I don't know how long I can endure taking sides here without having an ethical melt-down.)
Niko
PS
Replace the phrase 'G2 opponents' with the name 'Vinnie', who seems to think calling people 'slimey' and 'imbicile' demonstrate one's argumentative superiority. His contradictions of logic, hypocrisy, personal attacks on the character of those making neutral observations or expressing neutral opinions, all serve as wonderful examples of how not to effectively influence people or raise support for a cause. He's like a politician who's election campaign consists of insulting the mothers of his constituents.
> All of this is a moot point. Mike wont change the name, no one here
> can make him. Get over it. This is so rediculously unimportant in
> the scheme of things I hate to see so much list traffic dedicated to
> it.
Amen.
I feel that this article is very one-sided, but as a user I could care less about this quarelling over protocol, the thing is: shareaza works well, it's not perfect but it works better than limewire and gnucleus..
So I hope the improvements will be used by every Gnutella clients..
"John Marshall has made his decision. Now let's see him enforce it."
--sdem
Comment removed based on user account deletion
Gnutella Developers Front?
=p
is that it shows your ip address, therefore, it handily identifies you, not a surprise considering who the owner of bearshare is.
What are the privacy implications of Guid? Can this be spoofed by editing the file?
Is it mandatory to show your ip address in any of the other clients? All of them?
Which of the other clients are semi-secure? I'm aware that Kazaa can show and make accessible some or all of the files on a networked computer. Which of the other clients are more secure?
Which are recommended, and why are they recommended over the others (assuming you've had experience with them. Include security concerns please.
Thanks in advance!
Which of the Gnutella clients are recommended for Gnu/Linux?
Do all of the Gnutella clients for Gnu/Linux make your ip address readily (ie: easy to record through a MPAA/RIAA script) available?
Is there a global unique identifier under Gnu/Linux? On AMD Athlon or Duron first generation chips? I'm aware of the ip address.
If there is, how can I block its transmission or change it?
What are the security implications of installing and running a Gnutella client?
I am running a workstation install (I picked the applications, no mail server, no time server, no apache, no ftp) of SUSE 8.0. The workstation is firewalled with a Linkie, NAT, to a static IP on a dsl line. The Linkie gives me a network ip via dhcp. I know that when I run bearshare under windows (safer, as windows doesn't "see" my important drives or files), port 6346 is constantly hit (zonealarm), as well as other ports less frequently. So even though I am firewalled with a linkie, other gnutella users do see my workstation.
How can I better secure my Gnu/Linux install, and run Gnutella under Gnu/Linux, or should I really forget it? I'm sick of the half dozen to dozen freezups and bsods per day under windows(98SE), and I'm not upgrading windows anymore. Not stealing it, not sending my money to washington. I'm thoroughly satisfied with Gnu/Linux and am not going back. So how can I best run Gnutella while practicing safe security?
TIA!
The truth is that the commercial developers are mad that Shareaza is freeware and has better features. The commercial clients suck in comparison to Shareaza 1.7b and Gnucleus.
giFT just has not yet had a stable release, even though it works very good already. In the long run, I expect it to be able to support the 10s of thousands of users kazaa or gnutella have. In fact just try it, you'd be surprised.
/..
Also, from the fact that you use kazaa, I presume, that you use windows, which is not an option for me. In fact it makes you look like a fool on
Moritz
Mike has said on numerous occasions that he will release the G2 protocol when it is finished. Since the protocol is still in beta and being changed, it's still not finshed. When he works out the bugs and makes it as good as it can be, it will be released.
If the proposed protocol is entirely new, why unilaterally declare it the new Gnutella protocol by calling it Gnutella2? What if I propose something that is called Gnutella3 and is crap, from a technical point of view (I don't suggest Gnutella2 is)?
If the protocol is really that good, why not give it an entirely new name and let it become popular by its technical merits?
Just as the Limewire and Bearshare developers shouldn't be the ones to decide what becomes the next Gnutella, nobody else should do that on their own.
I strongly doubt that "Gnutella" is trademarked as a P2P name by anyone involved, so lawsuits are not an issue.
May we never see th
If you had read the venom pouring forth from some members of the_gdf you'd realize "bitter" is a rather severe understatement. There are definitely some egotistical kids involved in all this, but I think your labelling has been misdirected.
I've worked on gtk-gnutella with Raphael Manfretti, and while I haven't been in touch with him for a bit, your comment sort of stopped me cold.
Raphael and the other main developers have put *huge* amounts of time into developing and *carefully documenting* a protocol that's pretty backwards compatible. They've been in contact with each other to ensure that their clients work well, and are one of the more impressive examples of competitors working together for everyone's good.
Now, after all this work to avoid protocol fragmentation, one guy makes a new protocol. He uses some work from existing members, and refuses to publish any specifications. He then *takes* the name from this project that has seen *so* much work to be open (because he wants to grab a bit more PR and a few more $$$), and uses it.
Now, these developers are, more than understandably, frusterated. This leads to lots of end-user confusion. It's bad for *everyone involved*. Had Make said "I'm making a new protocol and calling it Sharella" or something, it would have been okay. But he created incompatibility, *he* refused to publish specs to let other developers remedy that, and *he* is out trying to profit off the users of the network.
So, I have to disagree. I've seen a lot of Raph's writing, and while sometimes he turns something down, he acts a lot more mature than, say, Linus does.
Your criticism of him is unfounded.
May we never see th
The more pretentious a corporate name, the smaller the organization. (For ...)
instance, The Murphy Center for Codification of Human and Organizational Law,
contrasted to IBM, GM, AT&T
- this post brought to you by the Automated Last Post Generator...