That would be HO2 (which isn't a stable molecule) rather than H2O (which is water).
Water is two Hydrogen atoms and one Oxygen.
Re:this all sounds great... but it's not a market
on
The Open Code Market
·
· Score: 2, Insightful
I disagree with the nonrivalous consumption part.
The true product in this market is not the software, but the developer time. If a developer is working on one commission, other consumers cannot also be getting work done from that developer on their commissions. So, the consumption here is rivalous.
The advantage for moon based solar power is raw materials. Building solar panels out of lunar materials means that you don't have to launch nearly as much.
Of course the ultimate is to construct earth orbiting satellites from lunar materials, since then you only have to conquer the moon's gravity and not the Earth's.
Re:Give whatever you feel they deserve.
on
Christmas Bonuses?
·
· Score: 2, Informative
I wouldn't call that a double standard. Power tools are generally a hobby for those husbands who recieve them as gifts, whereas vacuuming is a chore.
If it was considered OK to get the husband an iron so that he could iron his own pants/shirts, then yes, it would be a double standard.
Of course if there was someone who made a hobby out of vacuuming, a nice sporty vacuum cleaner would be an appropriate gift.
Brief interruptions, such as those caused by birds or other objects flying into the beam would not cause the plane to crash. No need for batteries, just glide past the interruption, and as long as you can reacquire the beam you won't have any problems.
There is also work (from Compaq days) in porting OpenVMS to Itanium.
One thing that confuses me about the Register article is where they got the information that HP is the sponsor of this roadshow. The SCO site lists Microlite as the sponsor.
The source for VistA, the system used by the VA, is about 99.9% public domain. Hard to read, but freely available. Check out the Hard Hats site for more info.
In the case you are describing, the "preferred form" of the source is the one that produces the optimized driver. In other words, that code which was derived from the original GPL driver source.
The theoretical obfuscating compiler wouldn't need to be included, nor would its source. Just the source used to create the optimized driver. The steps needed to make the final binary in your scenario go like this: 1) modify GPL driver source 2) compile obfuscating compiler with modified source 3) use obfuscating compiler to compile vanilla source 4) distribute resulting binary and vanilla source
This scenario doesn't work because the vanilla source is no longer the "preferred form" of the source. In the view of the GPL steps 2 and 3 above merge into "compile modified source", so the source that needs to be distributed is that from step 1.
What that "preferred form" clause does is eliminate obfuscation tricks. What it doesn't do is open up the obfuscation technology. It just makes using the obfuscation technology pointless.
If Red Hat decided that it wanted to use Intel's compiler to compile its distribution, it would not be violating the GPL if it did not include either that compiler or the source for that compiler with its distribution.
You may be reading the GPL license correctly, but I think you are missing the point of the posts to which you are replying.
femto says
If a company doesn't like the GPL, what's wrong with approaching the authors and saying 'Look, we can't live with this, can we negotiate some other license?'
The we he uses is referring to the original authors of the particular piece of GPL'd software. The we that you use in reply seems to be referring to 'the OSS community'. The reply of Rogerborg
Don't presume to tell me how I can and can't license my copyrighted code, and I won't tell you how to license yours. It's possible to release code under GPL and sell it, for example, which is win-win-win (author, purchaser, everyone else) as far as I can see.
seems to agree with the we as original authors interpretation.
Your statement
There is only one person telling how to license your copyrighted code, and that is the orginal developer of the software.
is what leads me to believe that you are just misinterpreting the we from femto, as well as missing that Rogerborg is referring to himself as the original developer.
Allowed or not, motorcyclists always seem to be doing it, at least here in the Bay Area. Mostly just in heavy traffic and at stoplights. It always pisses me off, but that is probably just due to jealousy.
REI still does something like this. All its sale items end with.93 (or something like that), I guess so that it would be obvious on returns that the item was a sale item.
"creating fluctuations in even the most simplistic equations" sounds very odd given the way we use the word "equation" - an equation can't fluctuate. Presumably he is using this as a technical term to refer specifically to the type of equations (or functions, more likely) needed to instantiate an environment such as the Matrix.
This sounds like chaos theory. There are extremely simple equations that under certain conditions produce chaotic results. Example: Xnext = A*Xcurr*(1-Xcurr) for A between ~3.6 and 4 and X between 0 and 1.
Chaos theory is why we can't accurately predict the weather beyond about 20 days. I would think that models of humanity would be similarly difficult to make long-term predictions from, and so the reference to chaos theory seems apropos.
That doesn't mean you couldn't still buy a crippled product, it just means that you can't buy a product that prevents you from turning around and selling that same crippled product to someone else.
So, while you could buy a product that requires you to use a special player while standing on your head in your backyard, you couldn't buy one that self-destructs if it senses that you are thinking of letting it go.
The simple way of looking at it is: You bought it, you can sell it. This wouldn't mean that you could sell copies of it, just the original it.
Not necessarily. If the talks are revolving around using this technology to distribute full resolution movies to digitally equipped movie theaters (both digital projectors and a ultrafat pipe) around the world, then it makes perfect sense.
I would tend to agree that if they are talking about taking the video to the homes of consumers then they are just wasting their time.
What about XML and XSLT? With one stylesheet for publication and others for reading on various platforms you get best of both worlds. If you have id attributes on all your elements you can get as anal about your layout as you like in your publication stylesheet, and still have the content be fully adaptable unmodified by simply using a different stylesheet.
The trick is having everyone using the same schema so that those adaptible stylesheets can be used for multiple documents. For publishers, the trick would be getting those pesky authors to use it.
The Open eBook is one attempt at a standard, DocBook is another. DocBook is notably used by O'Reilly to produce paper and electronic versions of their books.
Small nitpick, Carmina Burana is more than just 'O Fortuna', which is the song that always ends up in movie trailers. 'O Fortuna' was also used within the movie 'Excalibur'. Other songs from Carmina Burana may have been used in other places, but none come to mind.
The VistA source is GPL compatible because it is Public Domain.
There are parts of the VistA system which are not included in the FOIA release. The poster's primary interest (medication instructions) would appear to be one of those bits. The bits which aren't covered are primarily information copyrighted by other organizations (like the AMA).
If you aren't already an experienced M programmer, I would recommend having a large bottle of your favorite painkiller handy for when you review the code, it is pretty hard to read.
On the bright side, once you do understand M, you are pretty much guaranteed a job at a VA.
My assumption (given the topic of the article) was that he was talking about Apple creating a service to supply the music catalog from Universal Music. No rights hassles, as they would just be supplying music that they own.
Slashdot Mirror
That would be HO2 (which isn't a stable molecule) rather than H2O (which is water).
Water is two Hydrogen atoms and one Oxygen.
I disagree with the nonrivalous consumption part.
The true product in this market is not the software, but the developer time. If a developer is working on one commission, other consumers cannot also be getting work done from that developer on their commissions. So, the consumption here is rivalous.
The nonexcludability portion I do agree with.
The advantage for moon based solar power is raw materials. Building solar panels out of lunar materials means that you don't have to launch nearly as much.
Of course the ultimate is to construct earth orbiting satellites from lunar materials, since then you only have to conquer the moon's gravity and not the Earth's.
I wouldn't call that a double standard. Power tools are generally a hobby for those husbands who recieve them as gifts, whereas vacuuming is a chore.
If it was considered OK to get the husband an iron so that he could iron his own pants/shirts, then yes, it would be a double standard.
Of course if there was someone who made a hobby out of vacuuming, a nice sporty vacuum cleaner would be an appropriate gift.
That way you can ask:
Brief interruptions, such as those caused by birds or other objects flying into the beam would not cause the plane to crash. No need for batteries, just glide past the interruption, and as long as you can reacquire the beam you won't have any problems.
There is also work (from Compaq days) in porting OpenVMS to Itanium.
One thing that confuses me about the Register article is where they got the information that HP is the sponsor of this roadshow. The SCO site lists Microlite as the sponsor.
A few helpful links from Google.
The source for VistA, the system used by the VA, is about 99.9% public domain. Hard to read, but freely available. Check out the Hard Hats site for more info.
IBM has pretty decent documentation on their stuff, at least the AS/400 docs were good.
Go here for the zSeries and S390 docs.
That policy has been changed as of the end of 2001.
See here.
In the case you are describing, the "preferred form" of the source is the one that produces the optimized driver. In other words, that code which was derived from the original GPL driver source.
The theoretical obfuscating compiler wouldn't need to be included, nor would its source. Just the source used to create the optimized driver. The steps needed to make the final binary in your scenario go like this:
1) modify GPL driver source
2) compile obfuscating compiler with modified source
3) use obfuscating compiler to compile vanilla source
4) distribute resulting binary and vanilla source
This scenario doesn't work because the vanilla source is no longer the "preferred form" of the source. In the view of the GPL steps 2 and 3 above merge into "compile modified source", so the source that needs to be distributed is that from step 1.
What that "preferred form" clause does is eliminate obfuscation tricks. What it doesn't do is open up the obfuscation technology. It just makes using the obfuscation technology pointless.
If Red Hat decided that it wanted to use Intel's compiler to compile its distribution, it would not be violating the GPL if it did not include either that compiler or the source for that compiler with its distribution.
femto says
The we he uses is referring to the original authors of the particular piece of GPL'd software. The we that you use in reply seems to be referring to 'the OSS community'. The reply of Rogerborg
seems to agree with the we as original authors interpretation.
Your statement
is what leads me to believe that you are just misinterpreting the we from femto, as well as missing that Rogerborg is referring to himself as the original developer.
Allowed or not, motorcyclists always seem to be doing it, at least here in the Bay Area. Mostly just in heavy traffic and at stoplights. It always pisses me off, but that is probably just due to jealousy.
REI still does something like this. All its sale items end with .93 (or something like that), I guess so that it would be obvious on returns that the item was a sale item.
This sounds like chaos theory. There are extremely simple equations that under certain conditions produce chaotic results. Example: Xnext = A*Xcurr*(1-Xcurr) for A between ~3.6 and 4 and X between 0 and 1.
Chaos theory is why we can't accurately predict the weather beyond about 20 days. I would think that models of humanity would be similarly difficult to make long-term predictions from, and so the reference to chaos theory seems apropos.
.vbs files are for VBScript.
VBScript != VB just like JavaScript != Java
That doesn't mean you couldn't still buy a crippled product, it just means that you can't buy a product that prevents you from turning around and selling that same crippled product to someone else.
So, while you could buy a product that requires you to use a special player while standing on your head in your backyard, you couldn't buy one that self-destructs if it senses that you are thinking of letting it go.
The simple way of looking at it is:
You bought it, you can sell it.
This wouldn't mean that you could sell copies of it, just the original it.
Not necessarily. If the talks are revolving around using this technology to distribute full resolution movies to digitally equipped movie theaters (both digital projectors and a ultrafat pipe) around the world, then it makes perfect sense.
I would tend to agree that if they are talking about taking the video to the homes of consumers then they are just wasting their time.
What about XML and XSLT? With one stylesheet for publication and others for reading on various platforms you get best of both worlds. If you have id attributes on all your elements you can get as anal about your layout as you like in your publication stylesheet, and still have the content be fully adaptable unmodified by simply using a different stylesheet.
The trick is having everyone using the same schema so that those adaptible stylesheets can be used for multiple documents. For publishers, the trick would be getting those pesky authors to use it.
The Open eBook is one attempt at a standard, DocBook is another. DocBook is notably used by O'Reilly to produce paper and electronic versions of their books.
See here for a good assessment of why the "worldwide" scope isn't really overreaching.
Small nitpick, Carmina Burana is more than just 'O Fortuna', which is the song that always ends up in movie trailers. 'O Fortuna' was also used within the movie 'Excalibur'. Other songs from Carmina Burana may have been used in other places, but none come to mind.
The VistA source is GPL compatible because it is Public Domain.
There are parts of the VistA system which are not included in the FOIA release. The poster's primary interest (medication instructions) would appear to be one of those bits. The bits which aren't covered are primarily information copyrighted by other organizations (like the AMA).
If you aren't already an experienced M programmer, I would recommend having a large bottle of your favorite painkiller handy for when you review the code, it is pretty hard to read.
On the bright side, once you do understand M, you are pretty much guaranteed a job at a VA.
My assumption (given the topic of the article) was that he was talking about Apple creating a service to supply the music catalog from Universal Music. No rights hassles, as they would just be supplying music that they own.
True, but how much surfing can you do without power anyway?