A programming language is more than just syntax and semantics. The standard library and other community projects create a platform. Leveraging this platform is essential to productive development. Learning syntax/sematics takes an hour or two. Learning the rest is a long career.
First off, people do modify software on a daily basis. Customization of software is ubiquitous. Open source is an extreme model of customization and it has been successful because it addresses in a very specific way needs that are peculiar to software.
Customization of movies is *not* prevalent. You watch the movie that James Cameron made. Or the movie that Michel Gondry made. There is an entire notion of authorship is important to music / movies / books, and is utterly out of place in software.
Remixing is a practice of quotation, not customization. It is a way of leveraging the audience of another artwork to bring authority to your own, and as such is and will always be a loaded and potentially manipulative practice. Take a close look at Shepard Fairey's legal practices of defending his acts of appropriation as Fair Use, while suing those who appropriate his own work.
Remixing is similar to open source development in the way that it leverages the source work, but the effects are totally different. The audience of remixes remains fragmented. Open source software behaves in a different manner -- forks tend to merge back together, defragmenting the audience and increasing the value of the centralized project.
Here's the real issue. To those who would discard copyright, the question is what is it's replacement?
Without a legal framework to control distribution, content creators have already turned towards pervasive DRM as privatized solution. Sacrificing copyright also means sacrificing fair use. Or re-use of any kind, for that matter.
Thus far engineers are the only ones to directly profit from open source businesses.
The single biggest mistake open source advocates make when envisioning a future is the assumption that successful engineering practices will be successful artist practices. You don't sample a Britney Spears song to make a longer, better Britney Spears song; you sample it for reference. Whereas when you patch emacs, you aren't referencing emacs, you are adding functionality.
Even if an artist subscribes to the free->fame startup model, eventually the steps to monetization involve controlling the distribution of copies. For example, first Danger Mouse released the Grey Album to great acclaim, then formed Gnarls Barkley and released music in traditional commercial channels.
While copyright is bad for engineers, it is a 300 year old legal framework designed to compensate artists. Discarding it for nothing is short sighted at best, and at worst exploitive of artists.
1. take over domain 2. setup catch all email account 3. wait for "we wish you were still our customer" email 4. take over old billing accounts 5. repost site from archive.org 6. start tracking down clients perhaps with search for 'site designed by xxxxxxx' and send bills
You can call me an idiot, but violations of copyright are indeed theft from the artist/author. Supporting copyright law is important -- the GPL is built on copyright, Creative Commons is built on copyright.
What would you call it when a company encloses GPL software within proprietary products without releasing the source?
Just because the rightsholder in this case is Viacom doesn't mean the law is automatically invalid.
Actually it is. In addition to prompt response to takedown notices for infringing content, to qualify as a DMCA safe harbor the ISP must be unaware of infringing content and must not profit from the infringing content. Youtube's defense is sitting on a one legged stool.
we were all hoping to see mac os x join the netbook crowd. it is very nice to have a small bag carry around, and it would be nicer if mac os x was in that bag. unfortunately, windows 7 or ubuntu will have to suffice.
Authors and Publishers (and their estates) prefer their homages to be paid with $$$. Since they aren't Silicon Valley startups publicity doesn't have the same value.
At least US Robotics isn't attacking all business models in media industries. Google's attitude of a.) f*** the publishers and b.) f*** the authors is a curious one for an advertising company. They have no good will or benefit of the doubt in a case like this one.
Most repliers are unsympathetic to this complaint, but if this dataset was hooked up to an online tool which quickly did the look-up it would be a major issue.
This really should be a story about the legal risks of sub contracting... if you ship the work out, then it's very difficult to make sure all your ducks are in a row.
I've done alot of work with ruby in my free time on narf (http://www.narf-lib.org/). I'm not particularly fond of the permissions example either.
ruby is a young community, with a tolerant and diverse set of opinions. Rails isn't the only ruby O-R mapping; there is also lafcadio (http://lafcadio.rubyforge.org/). And Rails isn't the only web enviroment; there is also iowa (http://enigo.com/projects/iowa/index.html), as well as narf.
The english-speaking ruby community is young. Some parts of the language are very mature, and some parts are immature. It's an odd mix. I figure the ruby community now is about ~ to the php version 2-3, with different demographics.
Ruby usage is dispersed among alot of different projects. There are alot of different opinions about the right way to get things done; it's larger than one library.
~ patrick
Re:Wouldn't be much work in Tcl
on
Fault Tolerant Shell
·
· Score: 2, Insightful
> Your example only does a fraction > of what ftsh does.
yawn, so we didn't post a 100-500 line library in our slashdot comment.
the point is, this stuff would be trivial to implement in language like ruby. plus, using a full scripting language you get lots of other useful features like regular expressions, classes, etc, etc
It's a good idea, but it's a library implemented as a language.
Re:Wouldn't be much work in Tcl
on
Fault Tolerant Shell
·
· Score: 2, Insightful
Here's a Ruby one:
def college_try (limit, seq =0)
begin
yield
catch e
# forgot the syntax for getting the block
college_try( limit, seq + 1, block ) if (seq < limit)
end end
college_try( 50 ) {
begin
do some work
catch e
do error clean up here
raise e
ensure
do cleanup that should always run here
end }
Anyways, I agree with the notion that most popular scripting languages have advanced error handling that is up to the task.
Slashdot Mirror
It's basically the equivalent of your boss taking credit for your work, and using the generated revenue to hire his cronies. Lame but not illegal.
There's $12m of "Guild, Union, and Residual Payments" which is $12m more than Pirate Bay ever paid any artist.
Craigslist is invisible to Google and they are doing quite well. The value of Google is a business partner is way overrated.
A programming language is more than just syntax and semantics. The standard library and other community projects create a platform. Leveraging this platform is essential to productive development. Learning syntax/sematics takes an hour or two. Learning the rest is a long career.
They really are different things.
First off, people do modify software on a daily basis. Customization of software is ubiquitous. Open source is an extreme model of customization and it has been successful because it addresses in a very specific way needs that are peculiar to software.
Customization of movies is *not* prevalent. You watch the movie that James Cameron made. Or the movie that Michel Gondry made. There is an entire notion of authorship is important to music / movies / books, and is utterly out of place in software.
Remixing is a practice of quotation, not customization. It is a way of leveraging the audience of another artwork to bring authority to your own, and as such is and will always be a loaded and potentially manipulative practice. Take a close look at Shepard Fairey's legal practices of defending his acts of appropriation as Fair Use, while suing those who appropriate his own work.
Remixing is similar to open source development in the way that it leverages the source work, but the effects are totally different. The audience of remixes remains fragmented. Open source software behaves in a different manner -- forks tend to merge back together, defragmenting the audience and increasing the value of the centralized project.
Here's the real issue. To those who would discard copyright, the question is what is it's replacement?
Without a legal framework to control distribution, content creators have already turned towards pervasive DRM as privatized solution. Sacrificing copyright also means sacrificing fair use. Or re-use of any kind, for that matter.
The law exists to encourage the production of art. Making up numbers and inverting sentence structure is not a counter argument.
Thus far engineers are the only ones to directly profit from open source businesses.
The single biggest mistake open source advocates make when envisioning a future is the assumption that successful engineering practices will be successful artist practices. You don't sample a Britney Spears song to make a longer, better Britney Spears song; you sample it for reference. Whereas when you patch emacs, you aren't referencing emacs, you are adding functionality.
Even if an artist subscribes to the free->fame startup model, eventually the steps to monetization involve controlling the distribution of copies. For example, first Danger Mouse released the Grey Album to great acclaim, then formed Gnarls Barkley and released music in traditional commercial channels.
While copyright is bad for engineers, it is a 300 year old legal framework designed to compensate artists. Discarding it for nothing is short sighted at best, and at worst exploitive of artists.
1. take over domain
2. setup catch all email account
3. wait for "we wish you were still our customer" email
4. take over old billing accounts
5. repost site from archive.org
6. start tracking down clients perhaps with search for 'site designed by xxxxxxx' and send bills
It's a pretty smart scam.
You can call me an idiot, but violations of copyright are indeed theft from the artist/author. Supporting copyright law is important -- the GPL is built on copyright, Creative Commons is built on copyright.
What would you call it when a company encloses GPL software within proprietary products without releasing the source?
Just because the rightsholder in this case is Viacom doesn't mean the law is automatically invalid.
1/27 is not of majority.
Just to say it again -- Theft in the past remains theft.
Actually it is. In addition to prompt response to takedown notices for infringing content, to qualify as a DMCA safe harbor the ISP must be unaware of infringing content and must not profit from the infringing content. Youtube's defense is sitting on a one legged stool.
Thanks for the clean dismissal of 1 of the 27 slides. Obviously the lawsuit has no merit</sarcasm>
Theft a couple years ago remains theft.
we were all hoping to see mac os x join the netbook crowd. it is very nice to have a small bag carry around, and it would be nicer if mac os x was in that bag. unfortunately, windows 7 or ubuntu will have to suffice.
Actually you don't get it, the software is what makes this device nothing more than a giant iPhone. Which is absurd.
Authors and Publishers (and their estates) prefer their homages to be paid with $$$. Since they aren't Silicon Valley startups publicity doesn't have the same value.
At least US Robotics isn't attacking all business models in media industries. Google's attitude of a.) f*** the publishers and b.) f*** the authors is a curious one for an advertising company. They have no good will or benefit of the doubt in a case like this one.
Most repliers are unsympathetic to this complaint, but if this dataset was hooked up to an online tool which quickly did the look-up it would be a major issue.
This really should be a story about the legal risks of sub contracting... if you ship the work out, then it's very difficult to make sure all your ducks are in a row.
You can't put labels on the cards because then they bind in the devices.
Um, yes you can. I use little stickers. This is a pretty trivial problem.
... I could accidently download an exploit by loading an ad (1). IE interface to install the exploit is *so* much more user friendly.
a dserver_attack/
1. http://www.theregister.co.uk/2004/11/21/register_
I've done alot of work with ruby in my free time on narf (http://www.narf-lib.org/). I'm not particularly fond of the permissions example either.
ruby is a young community, with a tolerant and diverse set of opinions. Rails isn't the only ruby O-R mapping; there is also lafcadio (http://lafcadio.rubyforge.org/). And Rails isn't the only web enviroment; there is also iowa (http://enigo.com/projects/iowa/index.html), as well as narf.
The english-speaking ruby community is young. Some parts of the language are very mature, and some parts are immature. It's an odd mix. I figure the ruby community now is about ~ to the php version 2-3, with different demographics.
Ruby usage is dispersed among alot of different projects. There are alot of different opinions about the right way to get things done; it's larger than one library.
~ patrick
> Your example only does a fraction
> of what ftsh does.
yawn, so we didn't post a 100-500 line library in our slashdot comment.
the point is, this stuff would be trivial to implement in language like ruby. plus, using a full scripting language you get lots of other useful features like regular expressions, classes, etc, etc
It's a good idea, but it's a library implemented as a language.
Here's a Ruby one:
def college_try (limit, seq =0)
begin
yield
catch e
# forgot the syntax for getting the block
college_try( limit, seq + 1, block ) if (seq < limit)
end
end
college_try( 50 ) {
begin
do some work
catch e
do error clean up here
raise e
ensure
do cleanup that should always run here
end
}
Anyways, I agree with the notion that most popular scripting languages have advanced error handling that is up to the task.