OS X's core, Darwin, is licensed under the 3-clause BSD, and Apple releases both binaries and sources to the general public. If this Linux Kernel view was generated by any means, I imagine the same could be done for Darwin.
While it certainly doesn't require belief, it does require a measure of trust. While many scientific concepts make sense (I hesitate to say that they're intuitive), many are beyond the imagination or capacity of Average Joes to understand, even if they use the benefits of technology day-to-day. Such is the case with silicon microprocessors, for most people; V=IR is the upper limit of most peoples' understanding of basic electronics.
I wish the GPL was more permissive, myself; while it needn't be as open as BSD and MIT licenses, it'd be nice to allow for similar but incompatible licenses like the CDDL to link with it.
In before "Use LGPL": we'll never see ZFS in the Linux kernel because of the above problem, unless Sun decides to get rid of the clauses that make you immune to patent suit from them.
Funny; in my mind, interoperability also includes providing back compatibility for MSN, the "legacy" protocol which happens to be the most widely deployed instant messaging protocol.
A devil's advocate might posit that putting effort into developing XMPP (taking pains to point out your spelling error "XMMP") is more of a waste than trying to track MSN's upgrades, because of the deployment size, but as someone who runs ejabberd in his basement...:)
Alright, maybe you'll understand it like this: Imagine a set of n specific choices. Developers should provide n+1 choices, where the added "choice" is merely a lowest common denominator for users who don't care.
Additionally, I find your US/Muslim analogy amusing. I'm not in the States anymore because they don't provide ENOUGH choices and freedom.
Your hammer analogy sucks, here. If your hammer were Linux, there would be such community contention that you have to choose between steel or "beta" titanium heads, choose whether you wanted a wooden or artificial handle, choose what wood or plastic/metal you wanted for said handle, choose not only the generalized grip shape but the specific dimensions of it, et cetera. Oh, and don't forget that if you decided to change any one part, you'd have to change to the other rival set of (nigh identical) parts.
Choice is great, but something that a majority of Linux developers don't realize is that LACK OF CHOICE is in itself a choice.
Nobody knew that nukes were so close to being deployed until, you know, they were deployed. For all we know the NSA has worked out something faster than General number field sieve for integer factorization, or has quantum computers developed enough to the point that they can find cribs, or use related-key attacks, on otherwise infeasible problems. Incidentally, this addresses your point on computing power, which is overstated already because the NSA will KNOW who to tap, most of the time.
Hell, and it's not like OpenSSL and various other crypto implementations haven't been completely vulnerable to side-channel and timing attacks, either. Auditable GPL code in the hands of a malicious, well-funded organization of mathematicians is a scary thought.
While I've never been a good fan of Java, I audited a course in it to pick up the basis, and it seems to me that all the students in the class were given decent ground to build upon, particularly for C. Java isn't inately a bad language for understanding hardware; it's got the potential, and I suppose some teachers abuse it.
Ideally, I suppose, there would be a network of trust, using encryption and signature algorithms to guaranee delivery, and users would simply boycott ISPs who did subversive shit. Realistically, ad insertion will become completely commonplace, only nominally regulated, and internally endorsed by various US governmental functions.
The funniest part is that I'm almost certain cameras were covered in the in-game tutorials. Hah! Of course it's a high learning curve if you skip them!
Well, they've had some far better opportunities than this. They keep reuniting for one-off events, but never for good, and I admire them for that, at least. Lord knows the last thing we need is ANOTHER revived and lame old band.
The discussion here is seriously missing something. THANKS! A big thanks to all the people who worked their asses off, both within AMD and in the open community, trying to negotiate with manufacturers and patent holders to make this possible!
I remember a few releases back Erlang started including "HiPE", which does native and JIT compiling on various architectures, but there is a dearth of information for something so vital and I regret that I can't provide you with a link.
Wait, what? Is there something innately bad about proprietary code? (Badly written, not evil. I'm not touching that debate with a ten foot pole.) Shitty code coming from pork-barrel contractors doesn't preclude the possibility of some software companies actually, you know, caring about the products they make. Hell, sometimes said products get open-sourced later in life!
At the same time, when the majority directly influence the government into doing disgusting things (interring the Japanese, among other things), nothing can protect those victims from tyranny.
Slashdot Mirror
I thought that DJBDNS shipped with "dnscache"?
OS X's core, Darwin, is licensed under the 3-clause BSD, and Apple releases both binaries and sources to the general public.
If this Linux Kernel view was generated by any means, I imagine the same could be done for Darwin.
While it certainly doesn't require belief, it does require a measure of trust.
While many scientific concepts make sense (I hesitate to say that they're intuitive), many are beyond the imagination or capacity of Average Joes to understand, even if they use the benefits of technology day-to-day.
Such is the case with silicon microprocessors, for most people; V=IR is the upper limit of most peoples' understanding of basic electronics.
I wish the GPL was more permissive, myself; while it needn't be as open as BSD and MIT licenses, it'd be nice to allow for similar but incompatible licenses like the CDDL to link with it.
In before "Use LGPL": we'll never see ZFS in the Linux kernel because of the above problem, unless Sun decides to get rid of the clauses that make you immune to patent suit from them.
Funny; in my mind, interoperability also includes providing back compatibility for MSN, the "legacy" protocol which happens to be the most widely deployed instant messaging protocol.
:)
A devil's advocate might posit that putting effort into developing XMPP (taking pains to point out your spelling error "XMMP") is more of a waste than trying to track MSN's upgrades, because of the deployment size, but as someone who runs ejabberd in his basement...
If by "private" you mean "broadcast in plain text". :)
Alright, maybe you'll understand it like this:
Imagine a set of n specific choices. Developers should provide n+1 choices, where the added "choice" is merely a lowest common denominator for users who don't care.
Additionally, I find your US/Muslim analogy amusing. I'm not in the States anymore because they don't provide ENOUGH choices and freedom.
Your hammer analogy sucks, here.
If your hammer were Linux, there would be such community contention that you have to choose between steel or "beta" titanium heads, choose whether you wanted a wooden or artificial handle, choose what wood or plastic/metal you wanted for said handle, choose not only the generalized grip shape but the specific dimensions of it, et cetera. Oh, and don't forget that if you decided to change any one part, you'd have to change to the other rival set of (nigh identical) parts.
Choice is great, but something that a majority of Linux developers don't realize is that LACK OF CHOICE is in itself a choice.
Don't forget to factor in compression ratio increases, please.
Nobody knew that nukes were so close to being deployed until, you know, they were deployed.
For all we know the NSA has worked out something faster than General number field sieve for integer factorization, or has quantum computers developed enough to the point that they can find cribs, or use related-key attacks, on otherwise infeasible problems. Incidentally, this addresses your point on computing power, which is overstated already because the NSA will KNOW who to tap, most of the time.
Hell, and it's not like OpenSSL and various other crypto implementations haven't been completely vulnerable to side-channel and timing attacks, either. Auditable GPL code in the hands of a malicious, well-funded organization of mathematicians is a scary thought.
It's a moot point, if you live anywhere with key escrow laws.
I'm looking at you, Britain.
You could also virtualize over a network file system. Removes the need for 1:1 identical machines. :)
While I've never been a good fan of Java, I audited a course in it to pick up the basis, and it seems to me that all the students in the class were given decent ground to build upon, particularly for C. Java isn't inately a bad language for understanding hardware; it's got the potential, and I suppose some teachers abuse it.
Ideally, I suppose, there would be a network of trust, using encryption and signature algorithms to guaranee delivery, and users would simply boycott ISPs who did subversive shit.
Realistically, ad insertion will become completely commonplace, only nominally regulated, and internally endorsed by various US governmental functions.
Your $250K car is really worth a $4M elevator?
Nah, you can do Marathon in Aleph One.
Thanks, that'll allow me to play PPC MacOS games.
The thing is, the old DVD Player didn't listen to those messages, which made me love it to pieces.
The funniest part is that I'm almost certain cameras were covered in the in-game tutorials. Hah! Of course it's a high learning curve if you skip them!
Well, they've had some far better opportunities than this. They keep reuniting for one-off events, but never for good, and I admire them for that, at least.
Lord knows the last thing we need is ANOTHER revived and lame old band.
The discussion here is seriously missing something.
THANKS!
A big thanks to all the people who worked their asses off, both within AMD and in the open community, trying to negotiate with manufacturers and patent holders to make this possible!
I remember a few releases back Erlang started including "HiPE", which does native and JIT compiling on various architectures, but there is a dearth of information for something so vital and I regret that I can't provide you with a link.
Wait, what? Is there something innately bad about proprietary code? (Badly written, not evil. I'm not touching that debate with a ten foot pole.)
Shitty code coming from pork-barrel contractors doesn't preclude the possibility of some software companies actually, you know, caring about the products they make. Hell, sometimes said products get open-sourced later in life!
So instead of fines, you'd prefer tax increases across the board?
At the same time, when the majority directly influence the government into doing disgusting things (interring the Japanese, among other things), nothing can protect those victims from tyranny.