The market rules when providers compete to give customers what they want for some negotiated price. This still happens when one of the deliverables that the customer wants is the source code under the terms of some license they stipulate in the request for bids. If the customer is a government agency, and one of the deliverables that they request is source under the terms of the GPL, providers may still compete for this contract. The price may go up, since each provider knows that they won't get the comfort of locking the customer in as a dependant. The customer may believe that this increased cost is worth it in the long term, because it leaves them free to choose to contract with another provider in the future when the system needs maintenance.
"strong armed"!? You're talking about a customer/provider relationship. Either the provider wants the contract for what the customer requested, or it does not.
The devoted window managers that you mentioned only replicate the chrome, but the appreciation for NeXTstep goes much deeper than that. While ahead of the hardware of the day, it's architectutre was an excellent balance for end users and software developers, while allowing the vendor to be responsive in dying market for system software. That it survived to become OSX is a testament to its design and implementation.
I don't get why the tacit assumption is that Apple would switch to Intel. What if they merely added Intel machines to their hardware line and used the same fat-binary approach that NeXTstep used to run on sparc, pa-risc, x86, and m68k processors? This way they could continue to use the G4 for low-power situations like the notebook line.
I don't think Apple can change to Intel chips because that would require new versions of all the software. They've just asked all their customers to replace old OS9 software with OS X software. If they came back in 2 years and said everyone should replace all their software again, their customers would start to get rather irritated by it...
Perhaps, but what if doing so were as easy as clicking a checkbox that included x86 instructions in the fat binary? NeXTstep had this for four different achitectures (sparc, pa-risc, x86, and m68k) and it worked beautifully.
the basis for theft being considered "bad" is that it deprives the victim of the object you've taken. This is true for someone taking your television set , or your domain. It is not true for a song, or software...because when it's taken you still have your copy. I don't pirate songs or software. I'd rathar pay the author, and I do. But you can't use the same philosophical underpinnings for both kinds of "theft". I have yet to hear a good argument for why it's "bad" to copy a song. Perhaps you could provide one?
I agree with blakestah on all counts. I use debian unstable at work, and I've never had any problems keeping it current. I've found it to be way better than the "stable" versions of RedHat I've seen around here, easily.
At home, I use OSX. It's a dream. If the free software community could pull together and make something like Quartz (call it X12 if you want to) that would be the right direction to go, architecturally.
What is the jargon in PR circles when an interesting story like this one breaks, and you announce an even bigger story to hope that the more interesting one goes unnoticed?
I understand what you're saying. Still, it's clear to me from following the link that the contributors to freecraft know this already, and that they know that they're lacking the requisite skills to address the situation...else they wouldn't be putting out such a loud call for graphical artists.
If you want to do a 2d overhead or iso game, fine, but you need to take the time to make it look good...
One could finish this sencence with "...before it goes into shrinkwrap." This would make your comment sensible, because with commercial software you have the expectation that eye-candy consumers need motivation to buy. In the free software world, however, you do exactly what you have time to do, and you always release it, warts and all, so that it's available for download/play by anybody who wants to. Release early, release often. If you have high standards and don't want to touch it, that's fine. But you must understand that you sound silly telling open source projects that they "must do foo" before they release it. Ok, so you didn't explicitly say "before they release it", but you imply it strongly.
How many public K-12 schools need to go into how an OS works? How many elementary and middle school students can take programming classes, so they can get into OS design and implementation in high school?
There are many aspects of learning about computers that can be considered "learning how it ticks" that are nowhere near learning about process scheduling and memory management. Take, for example, the command line. I'm teaching my 12 year old to program in java on OSX. I'm not using any of the fancy GUI development tools. Instead, I've got Terminal.app configured so that it gives a Matrix-esque translucent green-phosphor appearance, and I'm having him learn to use a handful of simple commands and the bare minimum emacs commands (^X^C to get out of it). He compiles on the command line. He invokes his programs on the command line. He's learned more in the 3 weeks that we've been at it than he has in his entire life of pointing and clicking -- and he's been using computers since he was 4. And he's hardly past HelloWorld yet. Schools could benefit from seeing the value of teaching kids to interact with computers through the language of the CLI instead of the point-and-grunt semantics of the GUI.
It was also illegal for you to conduct your own repairs, even if the works were right behind a panel in the wall of your own apartment. There was a scene where the official repairmen finally arrived (a short-fat/tall-skinny pair like Laurel & Hardy) almost catching the rogue repairman in the act, and they were very dubious about the plumbing just "fixing itself". (The source is closed; though shalt not touch...) Add to that the constant restaurant bombs and the botulism toxins that people are injecting to look younger, and you have a movie that was frighteningly accurate prediction of the future.
Slashdot Mirror
The market rules when providers compete to give customers what they want for some negotiated price. This still happens when one of the deliverables that the customer wants is the source code under the terms of some license they stipulate in the request for bids. If the customer is a government agency, and one of the deliverables that they request is source under the terms of the GPL, providers may still compete for this contract. The price may go up, since each provider knows that they won't get the comfort of locking the customer in as a dependant. The customer may believe that this increased cost is worth it in the long term, because it leaves them free to choose to contract with another provider in the future when the system needs maintenance.
"strong armed"!? You're talking about a customer/provider relationship. Either the provider wants the contract for what the customer requested, or it does not.
The devoted window managers that you mentioned only replicate the chrome, but the appreciation for NeXTstep goes much deeper than that. While ahead of the hardware of the day, it's architectutre was an excellent balance for end users and software developers, while allowing the vendor to be responsive in dying market for system software. That it survived to become OSX is a testament to its design and implementation.
There are a few pages of good discussion here.
I don't get why the tacit assumption is that Apple would switch to Intel. What if they merely added Intel machines to their hardware line and used the same fat-binary approach that NeXTstep used to run on sparc, pa-risc, x86, and m68k processors? This way they could continue to use the G4 for low-power situations like the notebook line.
Perhaps, but what if doing so were as easy as clicking a checkbox that included x86 instructions in the fat binary? NeXTstep had this for four different achitectures (sparc, pa-risc, x86, and m68k) and it worked beautifully.
Shame this post was moderated as 'off topic'. Did the moderator read the topic?
And before that with NeXT's OpenStep, which is now MacOSX. It's amazing to me that people will look at .NET and think this is something MS invented.
+1 Funny.
the basis for theft being considered "bad" is that it deprives the victim of the object you've taken. This is true for someone taking your television set , or your domain. It is not true for a song, or software...because when it's taken you still have your copy. I don't pirate songs or software. I'd rathar pay the author, and I do. But you can't use the same philosophical underpinnings for both kinds of "theft". I have yet to hear a good argument for why it's "bad" to copy a song. Perhaps you could provide one?
Can I raise a practical question at this point? Does this mean we have to go back to blotting out the "i" with an asterisk again when we write un*x?
I agree with blakestah on all counts. I use debian unstable at work, and I've never had any problems keeping it current. I've found it to be way better than the "stable" versions of RedHat I've seen around here, easily.
At home, I use OSX. It's a dream. If the free software community could pull together and make something like Quartz (call it X12 if you want to) that would be the right direction to go, architecturally.
they could probably set up an array of 1024 of those cash-sucking vortices in parallel and still not risk depleting their pile of cash.
the one that was made in USSR was not a "remake"...it was the original film adaptation.
The worst kind of theft? Even worse than the kind of theft that deprives the victim of the object you've taken? The stuff folks will believe...
What is the jargon in PR circles when an interesting story like this one breaks, and you announce an even bigger story to hope that the more interesting one goes unnoticed?
I understand what you're saying. Still, it's clear to me from following the link that the contributors to freecraft know this already, and that they know that they're lacking the requisite skills to address the situation...else they wouldn't be putting out such a loud call for graphical artists.
One could finish this sencence with "...before it goes into shrinkwrap." This would make your comment sensible, because with commercial software you have the expectation that eye-candy consumers need motivation to buy. In the free software world, however, you do exactly what you have time to do, and you always release it, warts and all, so that it's available for download/play by anybody who wants to. Release early, release often. If you have high standards and don't want to touch it, that's fine. But you must understand that you sound silly telling open source projects that they "must do foo" before they release it. Ok, so you didn't explicitly say "before they release it", but you imply it strongly.
Read eddy's post on this. It answers this question clearly.
Alternatively, you'd get a free linux firewall/webserver.
That's an interesting link. I'm left thinking that anything would make a better logo than something called a Nut Device, though.
for the love of pete mod that post Insightful.
There are many aspects of learning about computers that can be considered "learning how it ticks" that are nowhere near learning about process scheduling and memory management. Take, for example, the command line. I'm teaching my 12 year old to program in java on OSX. I'm not using any of the fancy GUI development tools. Instead, I've got Terminal.app configured so that it gives a Matrix-esque translucent green-phosphor appearance, and I'm having him learn to use a handful of simple commands and the bare minimum emacs commands (^X^C to get out of it). He compiles on the command line. He invokes his programs on the command line. He's learned more in the 3 weeks that we've been at it than he has in his entire life of pointing and clicking -- and he's been using computers since he was 4. And he's hardly past HelloWorld yet. Schools could benefit from seeing the value of teaching kids to interact with computers through the language of the CLI instead of the point-and-grunt semantics of the GUI.
It was also illegal for you to conduct your own repairs, even if the works were right behind a panel in the wall of your own apartment. There was a scene where the official repairmen finally arrived (a short-fat/tall-skinny pair like Laurel & Hardy) almost catching the rogue repairman in the act, and they were very dubious about the plumbing just "fixing itself". (The source is closed; though shalt not touch...) Add to that the constant restaurant bombs and the botulism toxins that people are injecting to look younger, and you have a movie that was frighteningly accurate prediction of the future.
security model