You will also want someway to prevent the pins from conducting heat to the motherboard.
is probably very difficult. I don't think there are any excellent electrical conductiors that are poor heat conductors. Keep in mind the voltages involved here, resistance needs to be as close to zero as possible.
Imagine a processor that will run at many times the current CPU upper temps and not blink.
Yeah, but imagine the smell those burning dust bunnies will make.
Seriously though, if you are going to have something that hot, you'd need to completely change the entire mainboard design. The PCB would have to be made of more heat resistant materials (which would be trivial if the envirofreaks didn't effectively ban asbestos), and all the surrounding chips would have to be rated to deal with the oven-like heat of the CPU.
Not to mention, heat comes from power usage. We are already pushing 50-70 watts for current CPUs. Imagine having to buy a 2kw power supply for your computer. You'd need to plug it in to a special circuit like a stove or a dryer. Then imagine running the air conditioning in the summer overtime, to compensate for the 2kw heater that is running all the time (and waste money even in the winter, since heat pumps are far more efficient than resistive heat). The costs are not linear at all.
Anyway, my point is, there is an upper limit to heat dissipation possible in personal computers, even if the chip can stand it.
I.E. they explicitly contrast their license with the GPL.
In any case, it's a good thing. Not everything MS says about the GPL is FUD.
The GPL is, in fact, designed to prevent use of GPL'd libraries and software that involves tight integration (i.e. linked) with non-free software. This isn't a side-effect or some secret conspiracy, it's the purpose of the GPL, to provide exclusive advantages to the free software community that aren't available to non-free developers.
The FSF is really honest about this too. The only FUD is that MS presents it as if it was some dirty secret of the open source community.
The only side-effect is really the unfortunate use of GPL incompatible licenses by developers with good intentions. This is another reason the FAQs run kinda long, because there are so many licenses out there, and not all of them are able to be combined with GPL code.
To respond to you post more directly, I think you grossly misunderstand what fair use is all about. It's a very limited provision of copyright law, in short, allowing use of limited sections of a copyrighted work for research, acedemics, news reporting, education, and things of that sort. It's doubtful that any linking would fall under fair use, but I don't think it's ever come up in court.
On the other hand, your conclusions are right, but for the wrong reason.:)
The GPL does not kick in unless you distribute GPL code or resulting binaries in some way. So for your own use, you are free to do what you like with GPL code. You just can't distribute it without worrying about compliance with the GPL.
On the other other hand, MS EULAs do indeed put conditions on your mere use of their products. MS doesn't have to give you permission to do non-distribution things with their code, same as any license, but the EULA may place additional restrictions on the non-distribution use of their products. They must make a loophole in their EULA if it prohibits something that would be allowed by "default" under copyright law, and they want you to be able to do it. Think of it as a deny-all firewall with exceptions, compared with an allow-all firewall with exceptions.
I actually did know all that. A misunderstanding was that when you said "micro" I assumed you meant "microcomputer" i.e. a PC. I didn't realize you meant microcontroler i.e. PIC or Amtel.
Why do you feel the need to circumvent the sig char limit, and go against the wishes of the people who turn sigs off, just to whine about a rejected story?
You know, the journal system is there for a reason. Bitch there.
You're talking about a guy who named all 268 of his sons "George Foreman".
The hilarious part to this is that he has sold the use of the name "George Foreman", in perpetuity, to Salton, Inc for 110 million dollars.
Dumb boxer ain't so dumb, eh?:) I sold my Salton stock after finding that out. I don't guess his Sons will mind too much that he sold their soul, especially if the republicans get their way with the inheritance tax.
But once the GPL starts talking about "linkage", and trying to claim that Application A linked with GPL'd Library L means A has to be GPLed, while App A linked with GPL'd Operating System O does not,
What are you referring to? How do you "link to an operating system"?
The concept of "linkage" just isn't that clear cut
Sure it is.
it's not always clear when those obligations apply.
No, it's very clear. When you distribute GPL'd code, you must abide by the GPL. If you distribute no GPL'd code, then the GPL doesn't apply to you.
Safest thing to do is assume that if you're anywhere near GPL'd code, then your code needs to be GPL'd as well.
Total FUD. It's completely safe to use GPL'd tools to create any kind of software you want, so long as you don't distribute any GPL'd code.
Most of the FAQs actually explain copyright law, rather than grey areas in the GPL.
There is at least one grey area, such as using a completely server-side modified GPL'd app on the web, that is one thing they are working on for version 3. Linking really isn't one of those grey areas.
There is a currently pending lawsuit to allow his name on the ballot. Otherwise, he has to get >50% vote on a seperate issue on the ballot that asks whether he should be recalled.
At least that's how I understand it piecing it together from various NPR reports.
If you build power supplies, you should know that standard components with smaller operating temperature ranges are much cheaper than mil-spec temperature range components.
I'm sure power supplies would cost a hell of a lot more with parts rated to operate at 125C.
If you use large enough conductors, it wouldn't matter.
Alternatively, a 24 or 48 VDC power system might make the complexity and heat of the internal power supply much less. I hear the telco uses something like that.
To make this work, it'd have to be automatic, such as a central database of PGP keys that could be automatically used just by checking a box when you send email to someone.
My riding mower seems to demonstrate this effect, you can stand 20 feet from the exhaust and feel pretty strong, coherent puffs of air randomly hitting you. It seems to be the same effect.
The Nazi soldiers are just doing what their commanders are telling them to do. The fact that the soldiers may not understand why it's necessary to round up all the jews is not the soldier's worry. They must do as their commander wishes if they wish to avoid punishment. When the case gets to court, it will show how good/bad the Nazi party is.
I think the point is that since SCO distributed the code under the terms of the GPL, it doesn't matter who owns the code, when only considering the merits of SCO's suit. No determination of ownership would be necessary.
For IBM to prevail in their countersuit, they have to take it a step farther and establish ownership.
They could have just as easily done it because margins on hard disks are lower than ever, and drives are increasing in size as fast or faster than ever. The economy not doing as well the last couple years definitely has something to do with it too.
I personally haven't really seen much quality decrease, if there is one, it's pretty slight. Hard disks failed years ago, and they still fail today.
I don't know why the hard disk makers would want to get involved in it really, since data has a value that is very difficult to assess.
Of course, it's much cheaper insurance to run some sort of RAID, and more than one RAID, in more than one physical location, with a cron job to copy the data every now and then.
I'd far rather an operating system that allowed me to use my modem and access the internet than split hairs over the definition of a modem and, ultimately, not.
Then you need to tell that to the manufacturers who won't release specs. You don't see these kinds of problems with other hardware for a good reason, the manufacturers aren't dipshits, they release specs.
Supporting companies who ultimately want to fuck you over is pretty bad karma.
It's still emulating the original functionality of the windows API. It would be a different matter if the Windows API were a standard that could be implemented. Since it's just random stuff some company made up, that they change all the time, Wine is never going to be 100%, it's always going to be playing catch-up. It's always going to be "emulating" the real thing.
Slashdot Mirror
I agree with your assessment, but this
You will also want someway to prevent the pins from conducting heat to the motherboard.
is probably very difficult. I don't think there are any excellent electrical conductiors that are poor heat conductors. Keep in mind the voltages involved here, resistance needs to be as close to zero as possible.
Imagine a processor that will run at many times the current CPU upper temps and not blink.
Yeah, but imagine the smell those burning dust bunnies will make.
Seriously though, if you are going to have something that hot, you'd need to completely change the entire mainboard design. The PCB would have to be made of more heat resistant materials (which would be trivial if the envirofreaks didn't effectively ban asbestos), and all the surrounding chips would have to be rated to deal with the oven-like heat of the CPU.
Not to mention, heat comes from power usage. We are already pushing 50-70 watts for current CPUs. Imagine having to buy a 2kw power supply for your computer. You'd need to plug it in to a special circuit like a stove or a dryer. Then imagine running the air conditioning in the summer overtime, to compensate for the 2kw heater that is running all the time (and waste money even in the winter, since heat pumps are far more efficient than resistive heat). The costs are not linear at all.
Anyway, my point is, there is an upper limit to heat dissipation possible in personal computers, even if the chip can stand it.
The GPL guarantees you to have no restrictions on your use of the software
The FSF does need to be very careful with one thing they are considering for GPL v3, the use of GPL'd web software.
Reading RMS's writing, he is leaning toward considering the case where a program transmits HTML or whatnot over HTTP as redistribution.
It's not unprecedented, since the program (often a script) generally copies parts of itself into the output, as a matter of course (think PHP).
This would mean one would have to be very careful using GPL'd software for this use.
This has the potential to be a very sticky subject.
I.E. they explicitly contrast their license with the GPL.
:)
In any case, it's a good thing. Not everything MS says about the GPL is FUD.
The GPL is, in fact, designed to prevent use of GPL'd libraries and software that involves tight integration (i.e. linked) with non-free software. This isn't a side-effect or some secret conspiracy, it's the purpose of the GPL, to provide exclusive advantages to the free software community that aren't available to non-free developers.
The FSF is really honest about this too. The only FUD is that MS presents it as if it was some dirty secret of the open source community.
The only side-effect is really the unfortunate use of GPL incompatible licenses by developers with good intentions. This is another reason the FAQs run kinda long, because there are so many licenses out there, and not all of them are able to be combined with GPL code.
To respond to you post more directly, I think you grossly misunderstand what fair use is all about. It's a very limited provision of copyright law, in short, allowing use of limited sections of a copyrighted work for research, acedemics, news reporting, education, and things of that sort. It's doubtful that any linking would fall under fair use, but I don't think it's ever come up in court.
On the other hand, your conclusions are right, but for the wrong reason.
The GPL does not kick in unless you distribute GPL code or resulting binaries in some way. So for your own use, you are free to do what you like with GPL code. You just can't distribute it without worrying about compliance with the GPL.
On the other other hand, MS EULAs do indeed put conditions on your mere use of their products. MS doesn't have to give you permission to do non-distribution things with their code, same as any license, but the EULA may place additional restrictions on the non-distribution use of their products. They must make a loophole in their EULA if it prohibits something that would be allowed by "default" under copyright law, and they want you to be able to do it. Think of it as a deny-all firewall with exceptions, compared with an allow-all firewall with exceptions.
Are you are saying he is planning on having more kids? He already has 10, the 5 sons and 5 daughters. All the sons are named George Foreman.
They probably didn't have the money to argue. It's not like they are actually selling many chips these days.
I actually did know all that. A misunderstanding was that when you said "micro" I assumed you meant "microcomputer" i.e. a PC. I didn't realize you meant microcontroler i.e. PIC or Amtel.
connect it to your micro's serial port and that's it!
If you are lucky enough to still have one. Haven't you heard? System board people seem to think RS232 is depricated!
Why do you feel the need to circumvent the sig char limit, and go against the wishes of the people who turn sigs off, just to whine about a rejected story?
You know, the journal system is there for a reason. Bitch there.
You're talking about a guy who named all 268 of his sons "George Foreman".
:) I sold my Salton stock after finding that out. I don't guess his Sons will mind too much that he sold their soul, especially if the republicans get their way with the inheritance tax.
The hilarious part to this is that he has sold the use of the name "George Foreman", in perpetuity, to Salton, Inc for 110 million dollars.
Dumb boxer ain't so dumb, eh?
But once the GPL starts talking about "linkage", and trying to claim that Application A linked with GPL'd Library L means A has to be GPLed, while App A linked with GPL'd Operating System O does not,
What are you referring to? How do you "link to an operating system"?
The concept of "linkage" just isn't that clear cut
Sure it is.
it's not always clear when those obligations apply.
No, it's very clear. When you distribute GPL'd code, you must abide by the GPL. If you distribute no GPL'd code, then the GPL doesn't apply to you.
Safest thing to do is assume that if you're anywhere near GPL'd code, then your code needs to be GPL'd as well.
Total FUD. It's completely safe to use GPL'd tools to create any kind of software you want, so long as you don't distribute any GPL'd code.
Most of the FAQs actually explain copyright law, rather than grey areas in the GPL.
There is at least one grey area, such as using a completely server-side modified GPL'd app on the web, that is one thing they are working on for version 3. Linking really isn't one of those grey areas.
I'm a Fiscal Conservative, Social Liberal.
I guess people are afraid of the L word these days?
The way i understand it, he can't.
There is a currently pending lawsuit to allow his name on the ballot. Otherwise, he has to get >50% vote on a seperate issue on the ballot that asks whether he should be recalled.
At least that's how I understand it piecing it together from various NPR reports.
If you build power supplies, you should know that standard components with smaller operating temperature ranges are much cheaper than mil-spec temperature range components.
I'm sure power supplies would cost a hell of a lot more with parts rated to operate at 125C.
Tigerdirect is sending me a new one. I've got my fingers crossed.
Good, you'll need luck to deal with Tigerdirect. They are considered one of the most scammy retailers out there.
If you use large enough conductors, it wouldn't matter.
Alternatively, a 24 or 48 VDC power system might make the complexity and heat of the internal power supply much less. I hear the telco uses something like that.
To make this work, it'd have to be automatic, such as a central database of PGP keys that could be automatically used just by checking a box when you send email to someone.
insanely huge army
Of slaves.
Rome collapsed from within.
My riding mower seems to demonstrate this effect, you can stand 20 feet from the exhaust and feel pretty strong, coherent puffs of air randomly hitting you. It seems to be the same effect.
The Nazi soldiers are just doing what their commanders are telling them to do. The fact that the soldiers may not understand why it's necessary to round up all the jews is not the soldier's worry. They must do as their commander wishes if they wish to avoid punishment. When the case gets to court, it will show how good/bad the Nazi party is.
Godwin be damned, if the shoe fits...
I think the point is that since SCO distributed the code under the terms of the GPL, it doesn't matter who owns the code, when only considering the merits of SCO's suit. No determination of ownership would be necessary.
For IBM to prevail in their countersuit, they have to take it a step farther and establish ownership.
That's not really a logical conclusion.
They could have just as easily done it because margins on hard disks are lower than ever, and drives are increasing in size as fast or faster than ever. The economy not doing as well the last couple years definitely has something to do with it too.
I personally haven't really seen much quality decrease, if there is one, it's pretty slight. Hard disks failed years ago, and they still fail today.
Insurance companies offer this.
I don't know why the hard disk makers would want to get involved in it really, since data has a value that is very difficult to assess.
Of course, it's much cheaper insurance to run some sort of RAID, and more than one RAID, in more than one physical location, with a cron job to copy the data every now and then.
I'd far rather an operating system that allowed me to use my modem and access the internet than split hairs over the definition of a modem and, ultimately, not.
Then you need to tell that to the manufacturers who won't release specs. You don't see these kinds of problems with other hardware for a good reason, the manufacturers aren't dipshits, they release specs.
Supporting companies who ultimately want to fuck you over is pretty bad karma.
It's still emulating the original functionality of the windows API. It would be a different matter if the Windows API were a standard that could be implemented. Since it's just random stuff some company made up, that they change all the time, Wine is never going to be 100%, it's always going to be playing catch-up. It's always going to be "emulating" the real thing.