The big difference is that Microsoft and Sun made an contract where Microsoft were given a license to use suns source code to suns java implementation, in order to optimize it for Windows. Provided that their implementation were a full and exact implementation of Java.
What Google have done is made an independent implementation of the java language* and part of the class library which Sun ship java. It would be the same thing if they had choosen c# instead and then made a (partial) implementation of that.
They might have used Perl,C++,C# or any other language. But they used Java. And the funny thing is that if Google for example had used a Perl instead of java they would most likely still have violated** the same patents as they do now.
*But they may not call it Java, and sun fucked up the naming by calling the language, the library the vm for Java. Different names for different things, please.
**I don't know if the current implementation google uses does violate any patents, but if it does then an implementation using Perl would most likely have violated the same patents, because they are general vm patents which are not java specific.
But the point was that Sicko could not do it. That was why Geret(Spelling?? (The Cardasien tailer/spy/??? who live on ds9) in the end did it without telling Sicko about the real plan.
It would not solve that problem. When a site does down due to the slashdot effect, it is almost always because the webserver itself is overloaded(Or rather the SQL database). Not because there is not enough bandwidth.
I would make this one as "Work as described and designed" but the design might have some bad side effects, so I would contact the original designer and hear if he don't want some code to handle those better.
Yes it was a single sell order which started it all, but what was the malfunction? The sell order did what the developers wanted it to do so there were no malfunction. There may have been an non-optimal sell order but that is all.
The problem is that for any specific budget* the x86-64 solution will give you more aggregate io and more processor hardware then the mainframe. The argument for the mainframe is then that the software might be more easy to write but there don't exists any mainframe which can serve even 1/10 of Facebook so you need to cluster them anyway. And if you need to special cluster magic you might as well have x86-64.
And IBM will not promise you 99.999% uptime if you buy a single mainframe. If you need that kind of uptime you need to buy multiple mainframes and cluster them.
*Counting in either rackspace used or money paid for hardware.
Are you sure it is the bus and not the SATA controller itself. I mean sata is(Should be with a good controller) 3gbit per port. Not a total of 3gbit per controller.
I would share my shared library safely in the same way my Linux* desktop already does that. Just use the mmu to mark all the pages as "read only". Or if you insist on allowing writing to a shared library use cow. Then only he application doing the write will be effected by the change. Just think about it: How does OS/Android prevent my application from writing over the operation system memory and thus take over the system? A shared library is not really any special case there.
No impact on politics? Leders with the same religion as you would like you much more, and almost newer go to war with you. A good way to start was to get an early religion switch to it and then build a road to a neighbour, open border with hin and hope the religion spred to him so he would switch to it. That way you were almost safe from attack from him. In fact different religions were most often the reason for war in civ iv.
Me: But a concept with not of much use without any usefull implementation.
And the Diaspora team is asking for help in developing that implementation. Which is not their current codebase.
This make no sense at all. Do you have any source for them wanting to rewrite their code base? This was not mentioned in the announcment and they plan to release a "user ready" alpha in less then a month, so I don't think they plan a rewrite.
And while it is nice that they are asking for help, they were paid to write the implementation them self.
Hu? They did collect money to make a working implementation. That was in fact their excuse for releasing software of this quality. (Our customers paid, and wanted something they could see/use).
I don't think unproven oss assertion is that "many eyes make bugs shallow". I can accept that. The unproven oss assertion is that many(More then for a similar closed source program) eyes will ever look at the code just because it is open source. I am for example coding c,c++ and Java and running a Fedora Core 13 as my desktop os, but I have newer looked at any any source for any operation system or applications I have been running.
That may be and nobody is arguing about the concept itself. But a concept with not of much use without any usefull implementation.
And hell, the majority of the security issues found appear to be rather simple to fix.
This is exactly why this is so bad. The mistakes are so big and so obvious for any developer with experience in web applications that the developers which worked on Diaspora can not be trusted to write secure code. They have clearly demonstrated that they have absolutely no knowledge of security. They did not just make a security hole due to some obscure implementation detail, they designed and implemented a framework with no security at all.
And security is not something you can add after you write the code. Just ask Microsoft about that.
The only solution I see is to get a new team which know how to write code, and then ask them to take over(Or rewrite) the application.
But is the problem with this specific application or with flash? The tower defence game I used to play a little(Gem crafter) newer took much cpu time when nothing happend. But it can take a lot of cpu time when there are lots of monsters on the map.
Remember You can make a busy loop in any language. Doom does that so even standing still in the game will tax your cpu to 100% rendering that nice 640x480 screen again and again.
It was newer database size which were the problem but the number of queries per second(Aka performance) which could be executed.
You can run a Google size database from MySQL, but you can't use to MySQL* to implement a search solution with performance like Google, without requiring much much much hardware.
Hmm, you are right. Oracle are also claiming that Google copied some of their code and included it with Android. But I could not find any description of exactly what code that would be.
The state of the law is currently that you can't copyright an api so anyone is free to reimplement the methods in any class library as long as the reimplementation don't include any code from the original implementation. This is also the reason that wine(The implementation of most of the windows api for linux) is legal.
The only way to stop anyone from implementing a specific api is if you have a patent which is needed to do any implementation. This is most likely the reason that Sun is suing for patents, and not copyright. Google have not made any copy of code owed by sun.
Slashdot Mirror
What ip exactly have google taken?
They newer claimed it had nothing to do with Java. They just newer claimed it was Java.
Google is not doing exactly the same thing.
The big difference is that Microsoft and Sun made an contract where Microsoft were given a license to use suns source code to suns java implementation, in order to optimize it for Windows. Provided that their implementation were a full and exact implementation of Java.
What Google have done is made an independent implementation of the java language* and part of the class library which Sun ship java. It would be the same thing if they had choosen c# instead and then made a (partial) implementation of that.
They might have used Perl,C++,C# or any other language. But they used Java. And the funny thing is that if Google for example had used a Perl instead of java they would most likely still have violated** the same patents as they do now.
*But they may not call it Java, and sun fucked up the naming by calling the language, the library the vm for Java. Different names for different things, please.
**I don't know if the current implementation google uses does violate any patents, but if it does then an implementation using Perl would most likely have violated the same patents, because they are general vm patents which are not java specific.
Oracle have so much existing software written in Java that they kinda need to keep Java alive.
But the point was that Sicko could not do it. That was why Geret(Spelling?? (The Cardasien tailer/spy/??? who live on ds9) in the end did it without telling Sicko about the real plan.
Damm, I watched to much star trek.
It would not solve that problem. When a site does down due to the slashdot effect, it is almost always because the webserver itself is overloaded(Or rather the SQL database). Not because there is not enough bandwidth.
I would make this one as "Work as described and designed" but the design might have some bad side effects, so I would contact the original designer and hear if he don't want some code to handle those better.
What malfunction?
Yes it was a single sell order which started it all, but what was the malfunction? The sell order did what the developers wanted it to do so there were no malfunction. There may have been an non-optimal sell order but that is all.
But there is one detail you seems to miss:
The scripts seldom changes, and thus can be cached by the browser.
Many images belong to the story on the Frontpage and will thus change each time you visit.
The problem is that for any specific budget* the x86-64 solution will give you more aggregate io and more processor hardware then the mainframe. The argument for the mainframe is then that the software might be more easy to write but there don't exists any mainframe which can serve even 1/10 of Facebook so you need to cluster them anyway. And if you need to special cluster magic you might as well have x86-64.
And IBM will not promise you 99.999% uptime if you buy a single mainframe. If you need that kind of uptime you need to buy multiple mainframes and cluster them.
*Counting in either rackspace used or money paid for hardware.
The first thing I do when installing java on windows is disabling Java Web Start, because it is such a bad implementation of such a bad concept.
Are you sure it is the bus and not the SATA controller itself. I mean sata is(Should be with a good controller) 3gbit per port. Not a total of 3gbit per controller.
I don't understand that last part? In what case would having multiple different versions of java installed and running be a problem?
I currently have 9 different java versions(1.5.x and 1.6.x) installed with no problems at all. (But I seldom use the 1.5 anymore).
I would share my shared library safely in the same way my Linux* desktop already does that. Just use the mmu to mark all the pages as "read only". Or if you insist on allowing writing to a shared library use cow. Then only he application doing the write will be effected by the change. Just think about it: How does OS/Android prevent my application from writing over the operation system memory and thus take over the system? A shared library is not really any special case there.
*Or windows.
No impact on politics? Leders with the same religion as you would like you much more, and almost newer go to war with you. A good way to start was to get an early religion switch to it and then build a road to a neighbour, open border with hin and hope the religion spred to him so he would switch to it. That way you were almost safe from attack from him. In fact different religions were most often the reason for war in civ iv.
Me: But a concept with not of much use without any usefull implementation.
And the Diaspora team is asking for help in developing that implementation. Which is not their current codebase.
This make no sense at all. Do you have any source for them wanting to rewrite their code base? This was not mentioned in the announcment and they plan to release a "user ready" alpha in less then a month, so I don't think they plan a rewrite.
And while it is nice that they are asking for help, they were paid to write the implementation them self.
Hu? They did collect money to make a working implementation. That was in fact their excuse for releasing software of this quality. (Our customers paid, and wanted something they could see/use).
I don't think unproven oss assertion is that "many eyes make bugs shallow". I can accept that. The unproven oss assertion is that many(More then for a similar closed source program) eyes will ever look at the code just because it is open source. I am for example coding c,c++ and Java and running a Fedora Core 13 as my desktop os, but I have newer looked at any any source for any operation system or applications I have been running.
but the conceptual idea of Diaspora is sound
That may be and nobody is arguing about the concept itself. But a concept with not of much use without any usefull implementation.
And hell, the majority of the security issues found appear to be rather simple to fix.
This is exactly why this is so bad. The mistakes are so big and so obvious for any developer with experience in web applications that the developers which worked on Diaspora can not be trusted to write secure code. They have clearly demonstrated that they have absolutely no knowledge of security. They did not just make a security hole due to some obscure implementation detail, they designed and implemented a framework with no security at all.
And security is not something you can add after you write the code. Just ask Microsoft about that.
The only solution I see is to get a new team which know how to write code, and then ask them to take over(Or rewrite) the application.
How do you know it checked with a server. It could just have checked your computers clock.
It's called Serial instead of auto_commit but the semantic is the same and used with
MyPrimaryKey serial not null primary key, ...
But is the problem with this specific application or with flash? The tower defence game I used to play a little(Gem crafter) newer took much cpu time when nothing happend. But it can take a lot of cpu time when there are lots of monsters on the map.
Remember You can make a busy loop in any language. Doom does that so even standing still in the game will tax your cpu to 100% rendering that nice 640x480 screen again and again.
It was newer database size which were the problem but the number of queries per second(Aka performance) which could be executed.
You can run a Google size database from MySQL, but you can't use to MySQL* to implement a search solution with performance like Google, without requiring much much much hardware.
*Or an other sql database.
Hmm, you are right. Oracle are also claiming that Google copied some of their code and included it with Android. But I could not find any description of exactly what code that would be.
The state of the law is currently that you can't copyright an api so anyone is free to reimplement the methods in any class library as long as the reimplementation don't include any code from the original implementation. This is also the reason that wine(The implementation of most of the windows api for linux) is legal.
The only way to stop anyone from implementing a specific api is if you have a patent which is needed to do any implementation. This is most likely the reason that Sun is suing for patents, and not copyright. Google have not made any copy of code owed by sun.