D
Deleted member 13721
Guest
Caught up in? the misunderstanding? or something else?
I misunderstood your stance on the matter, which drew my ire, which you didn't actually deserve. I apologize.
Caught up in? the misunderstanding? or something else?
It's an opinion probably shared by many, but it's not my say, while it is irritating. Also, I understand that FreeBSD is not a charity, every company and person (including myself) gets something out of it first, then they give back what they like. I don't mind if people are unable to put something back, but I think they should at least appreciate it, while they aren't required to.FreeBSD can use more people, but this also means the project will unfortunately accept unappreciative actions towards FreeBSD's community. That will have to be accepted by me, because widespread use can do more good than irritation.
That's an interesting story. They allowed use of FreeBSD, without getting some kind of authorization, or was it a private library?Ahh.. I've been using FreeBSD since 3.1. It started when I was in the Navy back in 1998. They put me in charge of the ships library computer network, which consisted of 2x Pentium 166MHz systems and a crashed NT4 server. They didn't have the software, nor could not find the license keys to reinstall it.
So, I goofed around the internet for a few days and bumped into FreeBSD...
I ended up turning it into an on-demand dial-up router and a file server. The network was rather secure as well and was utilized by both enlisted and officers alike.
That being on a navy ship, it is hard not to read that as "pirate" library I must clean my glasses, it seems.That's an interesting story. They allowed use of FreeBSD, without getting some kind of authorization, or was it a private library?
It was a public library, but completely separate from the main network.That's an interesting story. They allowed use of FreeBSD, without getting some kind of authorization, or was it a private library?
You are right. Components fragmentation AND lack of standardization is Linux's biggest plague. While modularity can give some advantages and flexibility, lack of standards across components could ends in poor integration between them.The big issue that I have with Linux is that it is a kernel with a bunch of addons. FreeBSD is a complete and integrated operating system, like Windows and Max OS-X is. The piecemeal nature of Linux, however, is its biggest advantage and its biggest Achilles's heel. Linux is highly modular, which is a great because you can pick and choose that stuff that you want and need in the base OS. However, that flexibility comes with a high price: You have to update those individual parts separately, and the new versions may or may not play nice with each other. It's a roll of the dice. The 200+ distros do help alot, but it is still a fragmented mess because everyone has a different way of doing things. I don't need 12 different tools that all do the same thing. But different distros use different tools to do the exact same thing. I see this problem even in cygwin.
FreeBSD offers stability, a complete and unified OS, regular updates that make sense, good performance, good security, and a generally unified community. Linux, on the other hand, is a fragmented mess because everyone has a different way of doing things. At least this is my personal opinion.
1985, Gibson founded Gibson Research Corporation, best known for its SpinRite software.