Google's search engine is so synonymous with "search the web" that we call searching the web "googling". I'm not saying that Google is guilty, but I am saying there is enough to build an antitrust case on (and IBM did win its antitrust case, so it's not a death sentence).
Microsoft didn't own operating systems, but they did use their near-total market share to try to take over the browser market, and the EU pegged them for it.
No, because GM and Chrysler have their own affiliated car dealerships. But if Ford Motor Company owned 90% of the car dealerships, it would create an unfair marketplace for car manufacturers, because Ford would be using their dominance in the car dealership industry to give themselves an unfair advantage in the car manufacturing industry.
Re:The War Between Intel Core and ARM
on
Apple, ARM, and Intel
·
· Score: 4, Informative
The war between CORE and ARM raged across thousands of worlds, ravaging the galaxy. Neither would waver in their belief in their own supremacy. For each side, the only acceptable outcome is the complete elimination of the other.
At $dayjob, we decide to release and our process takes about an hour. All the automated tests are run by Jenkins CI, and are run again during the release on every box being deployed to in order to ensure stability. We tend to deploy to User-Acceptance Testing boxes before full production boxes.
At the game company, we wrote a system that works like:
1) Tag release in git 2) Release is pushed to beta servers. Beta players get immediate updates. 3) Click button in Jenkins to run stable release
Completely automated, even down to restarting the servers in a staggered fashion to ensure that users always have a game to connect to (even if they have to disconnect in 20 minutes to receive the client update).
Automated testing, Continual Integration, and automated release processes (including cfengine3 and custom Perl scripts working with Git) come together to produce a painless release process. Since it's easy, we can do it whenever we want. As soon as it starts releasing bad code, we'll have to put process in place to ensure bad code does not reach our stable users.
I'm more concerned about orphaned works and the length of copyright causing a work to be completely destroyed before it can be preserved. I understand the desire to keep copyright, and I understand the idea that Google is infringing by creating these digital copies and then providing excerpts for users, but the wealth of knowledge that gets lost because of copyrights that last essentially forever is a real problem that needs a real solution.
Perhaps it's stupid to entrust that burden to a corporation, and it should be the job of a public or non-profit institution, but this knowledge must be preserved.
1) Purpose and Character: It seems to me the creator of the derived work is using the work to supercede the original. In my opinion, it is not transformative, the work is being used for the facts it represents. The original work inside the derived work is being used for its original purpose.
2) Nature of the copied work: The work appears to be informational, though not so important to society as to invalidate its copyright. It is itself not a fact or an idea, but an artistic representation of them.
3) Amount and Substantiality: The derived work contains a large portion of the original work. It's not merely a sample, and even that would apparently not definitively protect it under fair use.
4) Effect upon work's value: Here's a questionable one. What is the value of a work given freely? The religious speech of the derived work cannot be used to claim adverse effect, so this argument might actually work.
The slippery-slope argument you attempt is no defense here. "It is because it is" is also not a defense. For what reasons could the use of the original work be considered fair use other than what I've attempted to present?
I am still not a lawyer. This is still not legal advice. I do think I missed my calling.
It is absolutely okay for the person to say whatever they want. It is not okay to steal the greater portion of someone else's work to say it. If it were a small picture, or representative clip, sure, but it's a large portion of the original video, in between two other videos. One could make the argument that they are using the work to comment on the work, but they are not commenting on the work itself, they are commenting on the facts the work expresses.
Fair use is vague, of course, but this derivative work would have a very hard time winning a suit with that argument.
We were already omnivores, this allowed us to not be required to eat certain foods (fish and shellfish), so we could survive away from the sources for those.
This is scary to me, being wired up and used as a machine. Though I suppose it's actually no worse than other kinds of human slavery, and probably quite a bit better than some.
Except the internship is relevant to your desired career, and there are federal rules for unpaid workers that say basically "This person has to provide a net cost to productivity in order to qualify for unpaid work." Otherwise, they have to be a paid intern.
Except if the OS wasn't there, you'd have to create it. Every layer of abstraction the OS provides is another layer that app developers do not need to invent themselves. Remember DOS games that made you choose your audio card and video card? The OS is the huge base that lets you build your app pyramids.
I've had some self-taught programmer interns that seem to lack some of the critical problem solving skills that need to exist before the programming can begin. I've been looking for a book exactly like this: How to approach a programming problem. Is this a good gift to give to someone who really wants to be a programmer?
Valve as a company is built to experiment. They were experimenting before they had metric fucktons of money (a metric fuckton is 1.7 imperial fucktons). Turning TF2 into "My Pretty Mercenary" (accessorize! explodize!) was an experiment. Steam itself was an experiment. Their experiments have frequently paid off, and now they've got the ability to do even more radical experiments.
I own a MBPR, and it is not slow. I imagine they went with the "Pro" name because it does not have the Air's 1.6Ghz 2-core processor, it has the Pro's 2.3Ghz 4-core processor.
... well, I'm not that shocked.
I wonder how Iran's doing these days...
Google's search engine is so synonymous with "search the web" that we call searching the web "googling". I'm not saying that Google is guilty, but I am saying there is enough to build an antitrust case on (and IBM did win its antitrust case, so it's not a death sentence).
Microsoft didn't own operating systems, but they did use their near-total market share to try to take over the browser market, and the EU pegged them for it.
No, because GM and Chrysler have their own affiliated car dealerships. But if Ford Motor Company owned 90% of the car dealerships, it would create an unfair marketplace for car manufacturers, because Ford would be using their dominance in the car dealership industry to give themselves an unfair advantage in the car manufacturing industry.
The two factions of Total Annihilation were the Core and the Arm: http://en.wikipedia.org/wiki/Total_Annihilation
The war between CORE and ARM raged across thousands of worlds, ravaging the galaxy. Neither would waver in their belief in their own supremacy. For each side, the only acceptable outcome is the complete elimination of the other.
You are experiencing a car accident! Do you require assistance?
At $dayjob, we decide to release and our process takes about an hour. All the automated tests are run by Jenkins CI, and are run again during the release on every box being deployed to in order to ensure stability. We tend to deploy to User-Acceptance Testing boxes before full production boxes.
At the game company, we wrote a system that works like:
1) Tag release in git
2) Release is pushed to beta servers. Beta players get immediate updates.
3) Click button in Jenkins to run stable release
Completely automated, even down to restarting the servers in a staggered fashion to ensure that users always have a game to connect to (even if they have to disconnect in 20 minutes to receive the client update).
Automated testing, Continual Integration, and automated release processes (including cfengine3 and custom Perl scripts working with Git) come together to produce a painless release process. Since it's easy, we can do it whenever we want. As soon as it starts releasing bad code, we'll have to put process in place to ensure bad code does not reach our stable users.
I'm more concerned about orphaned works and the length of copyright causing a work to be completely destroyed before it can be preserved. I understand the desire to keep copyright, and I understand the idea that Google is infringing by creating these digital copies and then providing excerpts for users, but the wealth of knowledge that gets lost because of copyrights that last essentially forever is a real problem that needs a real solution.
Perhaps it's stupid to entrust that burden to a corporation, and it should be the job of a public or non-profit institution, but this knowledge must be preserved.
Taking the US legal tests for fair use:
1) Purpose and Character: It seems to me the creator of the derived work is using the work to supercede the original. In my opinion, it is not transformative, the work is being used for the facts it represents. The original work inside the derived work is being used for its original purpose.
2) Nature of the copied work: The work appears to be informational, though not so important to society as to invalidate its copyright. It is itself not a fact or an idea, but an artistic representation of them.
3) Amount and Substantiality: The derived work contains a large portion of the original work. It's not merely a sample, and even that would apparently not definitively protect it under fair use.
4) Effect upon work's value: Here's a questionable one. What is the value of a work given freely? The religious speech of the derived work cannot be used to claim adverse effect, so this argument might actually work.
The slippery-slope argument you attempt is no defense here. "It is because it is" is also not a defense. For what reasons could the use of the original work be considered fair use other than what I've attempted to present?
I am still not a lawyer. This is still not legal advice. I do think I missed my calling.
It is absolutely okay for the person to say whatever they want. It is not okay to steal the greater portion of someone else's work to say it. If it were a small picture, or representative clip, sure, but it's a large portion of the original video, in between two other videos. One could make the argument that they are using the work to comment on the work, but they are not commenting on the work itself, they are commenting on the facts the work expresses.
Fair use is vague, of course, but this derivative work would have a very hard time winning a suit with that argument.
I am not a lawyer. This was not legal advice.
We were already omnivores, this allowed us to not be required to eat certain foods (fish and shellfish), so we could survive away from the sources for those.
From prototype to full production is a major undertaking. Just ask the Raspberry Pi folks.
History textbooks</sarcasm>
This is scary to me, being wired up and used as a machine. Though I suppose it's actually no worse than other kinds of human slavery, and probably quite a bit better than some.
If Russia can help it, not at all.
We've had the hypospray for some time, it's just not good for everyday use. http://en.wikipedia.org/wiki/Jet_injector
Except the internship is relevant to your desired career, and there are federal rules for unpaid workers that say basically "This person has to provide a net cost to productivity in order to qualify for unpaid work." Otherwise, they have to be a paid intern.
Except if the OS wasn't there, you'd have to create it. Every layer of abstraction the OS provides is another layer that app developers do not need to invent themselves. Remember DOS games that made you choose your audio card and video card? The OS is the huge base that lets you build your app pyramids.
We have a planet with a comfortable capacity of 5 billion
[citation needed]
I read it as him creating the source that wikipedia can then cite, solving the problem.
You mean instead "leveraging their position to unfairly stifle competition," correct?
I've had some self-taught programmer interns that seem to lack some of the critical problem solving skills that need to exist before the programming can begin. I've been looking for a book exactly like this: How to approach a programming problem. Is this a good gift to give to someone who really wants to be a programmer?
Valve as a company is built to experiment. They were experimenting before they had metric fucktons of money (a metric fuckton is 1.7 imperial fucktons). Turning TF2 into "My Pretty Mercenary" (accessorize! explodize!) was an experiment. Steam itself was an experiment. Their experiments have frequently paid off, and now they've got the ability to do even more radical experiments.
I own a MBPR, and it is not slow. I imagine they went with the "Pro" name because it does not have the Air's 1.6Ghz 2-core processor, it has the Pro's 2.3Ghz 4-core processor.