Oracle is set to repeat the trajectory of SCO. Their primary product (the Oracle DB engine) is being displaced by the NoSQL and things like Postgres. The "next generation" of developers equals SQL engines with "old and bad", and when forced, it ends up with Postgres anyway. Oracle used to survive in significant part by the support of the "database administrators" class. This layer of support is also becoming thinner…
Oracle refuses to accept pro-Google “fair use” verdict in API battle
251–260 of 344 posts
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#252Earlier quoted context omitted.
If the "structure, sequence, and organization" of APIs is a copyrightable work in its own right, then couldn't Google make a GPL-licensed derivative SSO (Android's API) but put their implementation under a separate license? Has anyone done a legal analysis of how the GPL's copyleft provisions would apply to this new kind of copyrighted work?
No. Everything that gets linked to GPL has to be GPL.
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#253Earlier quoted context omitted.
Actually, plagiarism and copyright infringement are different things. For example, it is possible to plagiarize something that is not copyrighted, and many forms of copyright infringement wouldn't fit the definition of plagiarism.
True, but the parent seems to think they wouldn't have been plagiarizing if they had "paraphrased" the declaring code so to speak, which makes the relationship here explicit. If they had paraphrased the declaring code, it would have been much harder to say they were infringing on copyright, but instead, they copied it verbatim. Of course, in academia paraphrasing is still plagiarism, but it is likely no longer copyri…
That seems an odd thing to say. A significant portion of academic writing is paraphrasing, with attribution. What is a review article, other than attributed paraphrasing?
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#254Oracle is set to repeat the trajectory of SCO. Their primary product (the Oracle DB engine) is being displaced by the NoSQL and things like Postgres. The "next generation" of developers equals SQL engines with "old and bad", and when forced, it ends up with Postgres anyway. Oracle used to survive in significant part by the support of the "database administrators" class. This layer of support is also becoming thinner…
> The "next generation" of developers equals SQL engines with "old and bad" I think that what you mean is: - they don't understand the relational model - they don't understand the tradeoffs of ACID vs BASE - they never bothered to actually learn SQL - they *think* that they have "big data" Don't get me wrong - there are compelling use cases for, and decent products for, every class of non-relational database. But the…
I think the OPs tossing NOSQL in there was poor form, and I think "SQL engines" could be replaced with DBAs. The world still needs RDBMS and we desperately need people who understand them from an engineering perspective.
But as an average app developer, I can scale my product to serve hundreds of thousands of people with really shitty DB architecture by simply throwing RAM at Postgres. That means Oracle corporate promises and hoards of query-optimizing DBAs are not the default for most fast (and even some moderately fast) moving startups anymore.
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#255Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#256Oracle is set to repeat the trajectory of SCO. Their primary product (the Oracle DB engine) is being displaced by the NoSQL and things like Postgres. The "next generation" of developers equals SQL engines with "old and bad", and when forced, it ends up with Postgres anyway. Oracle used to survive in significant part by the support of the "database administrators" class. This layer of support is also becoming thinner…
> The "next generation" of developers equals SQL engines with "old and bad" I think that what you mean is: - they don't understand the relational model - they don't understand the tradeoffs of ACID vs BASE - they never bothered to actually learn SQL - they *think* that they have "big data" Don't get me wrong - there are compelling use cases for, and decent products for, every class of non-relational database. But the…
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#257Earlier quoted context omitted.
Not understanding is fine: assuming that something one doesn't understand must be a slur is not fine.
He didn't assume but presume. And I think that's quite understandable for a non native speaker, given the connotation of the word 'dark'.
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#258Earlier quoted context omitted.
> Their primary product (the Oracle DB engine) is being displaced by the NoSQL and things like Postgres. Worth noting they own MySQL (via Sun acquisition)
The developers moved to MariaDB, which is what everyone uses nowadays anyway rather than MySQL.
The 10M+ pulls (and 3.8k stars) on Docker Hub suggests that MySQL is still getting a ton of use.
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#259Earlier quoted context omitted.
The people that intended to do evil merely waited until those who didn't intend to do so finished implementing the things they were implementing. Then they used that sound infrastructure to do evil with, as they had intended to do all along. Those people that took the slogan seriously were used.
Those are very damning accusations. Care to give some examples?
Google buzz was also one of the early moves that showed this, opting everyone who uses gmail into a social network was pretty evil if you ask me.
Re: Oracle refuses to accept pro-Google “fair use” verdict in API battle
#260Oracle is set to repeat the trajectory of SCO. Their primary product (the Oracle DB engine) is being displaced by the NoSQL and things like Postgres. The "next generation" of developers equals SQL engines with "old and bad", and when forced, it ends up with Postgres anyway. Oracle used to survive in significant part by the support of the "database administrators" class. This layer of support is also becoming thinner…
Every public company needs to run Oracle/Peoplesoft or SAP.