Comment Re:Both sides equally (albeit differently) at faul (Score 1) 189
Except that Apple had no way to intimidated GT. GT did not have any need for Apple, and they could simply have walked away from Apple, and continued their business as before.
Except that Apple had no way to intimidated GT. GT did not have any need for Apple, and they could simply have walked away from Apple, and continued their business as before.
I newer understood the "not installing a backup power supply for each furnace" situation.
Who owned and was responsible for the factory? The story has always been that GT produced Sapphire, and that apple maybe wanted to buy it.
So why did GT let apple control anything at all, about their factories?
From the article " after five months Apple demanded a major change in terms, requiring GT to supply the sapphire itself. In fact, Apple wanted GT to build the world’s largest factory to produce the stuff"
So If Apple wanted GT to supply the sapphire, why did they have any say in the day to day running of the factories. Sounds like GT gave far to much factory control to Apple for no reason at all.
Sorry, but that is not what the halting problem say.
The halting problems state that "For any interesting property(In this example: "Is this robot code safe to run") there exists programs with this property, but where you can not prove that the program has the property.
That is: There exists robot programs which are safe to run, but where we can newer prove that they are safe.
And the general solution is to only run programs where we can prove that they are safe. This mean that we do reject safe programs because we can't prove that they are safe*, but it does not in any way change the programs which we can express. That is: For any program which is safe, but where safety cant' be proved, there exists a program which behave in exactly the same way for all input, but which is safe.**
*If we can't prove that a program is safe, then it is either because no such prof exists, or it is because we are not good enough to prove it.
**No this does not contradict the halting problem, due to the assumption that the program is safe. If the program is not safe, then the transformation will convert the program to a safe program which obviously will not do the same
Or if you don't have a Windows 7 installed.
Sorry, you are wrong here. The chips with pid0 works fine with Linux, so there is no reason, the vendor could not make a working Windows driver.
Why not? Both Postgresql and Openoffice does that.
Nobody ever said that Microsoft could not ship their own version of the JRE, and Microsoft newer made their own JRE.
Microsoft distributed a modified version of suns jre, based on source code licensed from Sun. And it was sourcecode licerse, which gave Microsoft problems. If they had just made their own jre, anything would have been fine(Except for the fact that they might not have called it Java(tm)
Sorry, but that is just wrong. He wrote a better(Or worse, depending on who you ask. I would say better) init system, but the decision to use it and thus to wrack your* init system was taken by the different Linux distributions.
*And no it's not your init system. Using something does not make it yours. It would only be yours if you had your own distribution, and in that case you could continue to use what ever backward init system you wanted.
If you have a debt of more then 578M, and no way to earn more money.
How it it "semantic nonsense" ?
The design is responsive, in that it respond to changes in the size of the viewport(Screen/Window size). Makes perfect sense to me
He said it did work, it's just not as effective as other existing compression solutions.
Is it because Windows is to slow on the low end hardware that they need to offer an Android phone?
The phone don't have access to Play store, so it can't be due to the many Android Apps they are doing it.
Is this not the same thing as fashion? Why is anyone surprised by the same effect, just because it's online?
When Eclipse is crashing with a segmentation fault, it is almost always in swt. So the problem is with the native code which swt calls in order to interface with the underlying operation system.
That can only be solved by writing the entire Operation system in a safe language, but nobody is working on that.
I have newer seen Eclipse segfault outsite swt code.
Yeps. I can confirm that. On linux it just works with Eclipse, and my emulator is running my software faster then the Android device I am testing on. (But I am testing on an old Android 2.3 device. I am sure a new Android device would beat my emulator).
Living on Earth may be expensive, but it includes an annual free trip around the Sun.