When the U.S. astronauts visited Mir, they brought their Fisher Space Pens. Those were no doubt the most reliable pieces of equipment on the space station.
People often equate "making it easy" with "dumbing it down". I used to have to toggle in the address, 0173000 in octal, and then push "load" and "run" to boot my computer. These days it's a good deal easier. I don't feel I've lost anything.
Perhaps we should be working on easy-to-use interfaces that are intended for a higher target IQ and a bit more study?
An airplane has hit the empire state building. The building survived. If you hit a cable of carbon nanotubules with an aircraft, it would most likely cut through the aircraft.
The system that serves technocrat.net has been running 2.4.0-test1 for 98 days without a reboot. It's a dual-processor Pentium III 600 system with 256M RAM, running multiple Zope processes to serve the weblog and two SETI@home processes set to the lowest priority to keep the CPUs busy when they would otherwise be idle.
I'm about to install a more recent kernel and reboot that system. 2.4.0-test1 had lots of flaws, but it happened I don't exercise any of them and the later releases are much more stable.
If you think putting this mod in 2.4.0 is a bad idea, consider that operating systems other than QNX and Linux try to provide real-time services and are probably less stable than either in their full release versions. We've got to get the code in if we're going to get it tested, and there's really no good test but actual use. Developing something this intimate with kernel internals for 2.2.17 would waste a good deal of developer time.
The way Linux is licensed makes Linus unnecessary to its future development. Anyone can take it and check it into CVS, modify it as they wish, and build their own group of people to maintain it. What keeps Linus in control right now is the respect that people hold for him. Once he moves on, there will be another group. Given the way that anyone can use anyone else's modification under the GPL, code-forks naturally converge.
Anyway, Linux only has a few years of development left. The system we run 10 years from now will be Free Software and will contain a lot of the same tools, but might well have a different kernel. I'm surprised that people don't consider this more.
Geez. The fight is over, everybody. I think Richard's editorial was unfortunate, and frankly KDE didn't have to respond at all. Now that there are no longer licensing problems, it is really time to put a lid on it. Let's not yield to the temptation to fan these flames any longer.
You are correct. I am generally not the one to first see the issues, they are almost always brought to my attention by other people. What I do is write about them. A lot of hackers out there have trouble putting their feelings in words, and that's something I can do to contribute to the community. However, I'd hardly rate my response to Linus on KDE licensing as one of my better pieces. If you want to see something I'm proud of, look at the Debian social contract (and give the Debian developers who participated credit too).
Is my license really any less credible than the GPL or any other license slapped on any piece of software?
Would you let a lawyer do your programming?:-)
Licenses written by programmers who have no idea how to write valid licenses end up being harmful to other programmers who have no valid way to apply them.
You really have two choices: use one of the existing ones, or run it by an attorney.
I think it's meant to be dual-licensing, either NASM or GPL. But he doesn't really say that unambiguously. A few sentences worded differently would fix it. I'd suggest starting the license with "You may choose one of two licenses to apply to this software: the NASM license, below, or the GNU General Public License in the file GPL in this directory."
Bruce
Binaries are the problem.
on
Qt Going GPL
·
· Score: 1
I'm most concerned with binaries. Even if he doesn't distribute any, someone will, and there's a real GPL problem there.
Thanks
Bruce
Re:Geez! Can we please kiss and make up already!
on
Qt Going GPL
·
· Score: 3
I am not apoligizing for waving the red flag. It needed to be waved and the result has been excellent. When you ask people to make changes, and they make them, it's right to say thank-you and cease hostilities. What I am objecting to is that people who don't even understand what is going on have continued to fight long after the fight is over.
Bruce
Re:Bruce Perence's first -1 redundant.
on
Qt Going GPL
·
· Score: 1
Sound effect: loud raspberry. Anyway, I pushed the "No Score +1 Bonus" when I posted it.
Re:A GPL Windows/QT could fork from the free codeb
on
Qt Going GPL
·
· Score: 3
This is questionable from a GPL-compliance standpoint, until you have a GPL or LGPL Qt that runs on Windows.
Bruce
Geez! Can we please kiss and make up already!
on
Qt Going GPL
·
· Score: 4
OK, I'm responsible for stirring this up long ago. But I endorsed the QPL, publicly thanked Troll Tech, and called off hostilities a long time ago. Yes, we had a license conflict issue that has now been dealt with.
Troll Tech has done everything necessary to accomodate the requests of the free software community. They have my sincere thanks, and should have yours, too.
Consider how little a nudge it would take to make it hit us right on. I'm afraid I don't have the math for orbital mechanics, but my guess is that out by the apogee of its orbit it would take a very small angular change. How much force would it take? Are we talking about a small asteroid impact, a pass by a massive object warping its orbit, or what?
Yes, I am sure that people are still going over that. It's something we should take note of in popular discussions like Slashdot: we have good reason to think that they are from Mars, but no proof. The case for the lunar ones is a lot more sure.
The company should not be forced to be your phone company or your internet provider. If you could only speak through the workplace, it would be different.
IANAL. Postulate that some employee committs an offensive action and the company is sued. I go to court and prove that I took all reasonable precautions to prevent the employee from carrying out an offensive action. Am I still liable? Maybe. Does my insurance cover it? Probably. Is my insurance company happy? Not entirely, but they have no real complaint since I took all reasonable precautions.
You can't eliminate risk. You thus work to mitigate it as much as possible.
It's not meant to be a non-compete, but I see your point. The particular situation that came up is that we found a really good deal that essentially nobody knew about, that got worse if more businesses participated. One of the employees wanted to take advantage of the deal for his own business in a way that would sour it for us. So, I asked him not to do that, and he agreed not to. But you are right that it should not read as a conventional employee non-compete, and I will fix that.
Slashdot Mirror
Aw, you've caught me. Yes, I really am the 15 highest-moderated posters on Slashdot. I have a login for each of my personalities. Not :-)
Bruce
Perhaps we should be working on easy-to-use interfaces that are intended for a higher target IQ and a bit more study?
Thanks
Bruce
Thanks
Bruce
An airplane has hit the empire state building. The building survived. If you hit a cable of carbon nanotubules with an aircraft, it would most likely cut through the aircraft.
I'm about to install a more recent kernel and reboot that system. 2.4.0-test1 had lots of flaws, but it happened I don't exercise any of them and the later releases are much more stable.
If you think putting this mod in 2.4.0 is a bad idea, consider that operating systems other than QNX and Linux try to provide real-time services and are probably less stable than either in their full release versions. We've got to get the code in if we're going to get it tested, and there's really no good test but actual use. Developing something this intimate with kernel internals for 2.2.17 would waste a good deal of developer time.
Thanks
Bruce
Anyway, Linux only has a few years of development left. The system we run 10 years from now will be Free Software and will contain a lot of the same tools, but might well have a different kernel. I'm surprised that people don't consider this more.
Thanks
Bruce
Patent number, please?
Turn the other cheek. Decline to fight. It does not diminish you.
Thanks
Bruce
Bruce
Would you let a lawyer do your programming? :-)
Licenses written by programmers who have no idea how to write valid licenses end up being harmful to other programmers who have no valid way to apply them.
You really have two choices: use one of the existing ones, or run it by an attorney.
Thanks
Bruce
Bruce
Thanks
Bruce
Bruce
Sound effect: loud raspberry. Anyway, I pushed the "No Score +1 Bonus" when I posted it.
Bruce
Troll Tech has done everything necessary to accomodate the requests of the free software community. They have my sincere thanks, and should have yours, too.
Thanks
Bruce
Bruce
Thanks
Bruce
Thanks
Bruce
Bruce
Bruce
You can't eliminate risk. You thus work to mitigate it as much as possible.
Thanks
Bruce
Thanks
Bruce