121–130 of 344 posts
Earlier quoted context omitted.
fsharp |> welcomes all alienated Java veterans and newbies with open arms!
If you don't like maven, you're going to need a padded cell when you move to nuget.
https://fsprojects.github.io/Paket/
But I agree, even Yarn/npm is better than the current state of dependencies for F#
Curious to hear your reasons for calling Red Hat a dark horse. (Which I presume is some kind of slur/holds a derogatory meaning)
I wish intent and end result counted more strongly. Andoid's compatibility isn't transitive: once code goes through the Android build pipeline to produce an Android Application it cannot be meaningfully used in the context of Oracle Java; it's a one-way transformation to remain "talent-compatible" with a large pool of Java developers and reuse the base of Java libraries. Projects like OpenJDK and WINE are efforts to…
Java SE, Java EE and JavaME are incompatible. Java was already fragmented by their creators
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…
It's not about age(ism) it's that Oracle stabbed them in the back by pushing cloud over on-prem where these guys (and gals) were employed. Now Oracle's biggest supporters are re-skilling to Postgres et al and stopped recommending Oracle to their organisations...
Earlier quoted context omitted.
Maybe he is an asshole, but at least Larry Ellison didn't build a company to spy on half the planet like Page & Brin.
He failed to make half the world use his company's products, among other things. BTW I'd appreciate if you gave an example of a highly successful and ethically impeccable company.
First of all this is moving the goalposts significantly and is also an impossible standard. I would say that Apple and Microsoft are more ethical than Google but the question is of course along what axis?
The sequence, structure and organization of those method signatures, in those 37 Java packages, were all GPL'd in the OpenJDK in 2007 by Sun. Regardless of whether API's can be copyrighted or not, Google had every right to use the code Sun GPL'd.
Google didn't use OpenJDK, they used Apache Harmony implementation
Earlier quoted context omitted.
I don't think that Florian Mueller is an unbiased source, he was paid by Oracle while the trial was happening
Well if you could point me to an unbiased source trying to argue the other side of this question, then sure. I really want to know both sides of this issue and it's nearly impossible to find someone separating the quintessential geek love for Google and geek hatred for Oracle from the facts of the case other than Mueller. Honestly I'm all for liberalizing copyrights and fair use but it makes me mad to see Google goin…
But you can't separate the facts from the quintessential paid love for Oracle and the paid hatred for Google of Mueller.
And exactly what tech has been ripping Google?
Earlier quoted context omitted.
Let's assume Oracle wins on appeal... What's next? Is everyone suddenly writing .Net code? Or are we left to find languages with lapsed copyrights? Fortran IV and Snobol are the new hotness! Everyone in to the pool!
Languages without a corporate owner.
This is one of the most important tech cases in history. Oracle is on a fast-track to destroying the software industry with it.
Oracle is such a shit company. There are still some great hackers there but Larry Ellison is an asshole, and I don't envy anyone who has to work for him even indirectly. "Left Oracle's Java business in tatters" eh? Where was their mobile OS? Their Dalvik? The wounds to Java have all been self-inflicted. If they succeed in copyrighting the API then where does this leave OpenJDK? Operating at the mercy of Larry fucking…
fsharp |> welcomes all alienated Java veterans and newbies with open arms!
Earlier quoted context omitted.
But, and I think this is really the main point, Google didn't just use the API signatures they used the API documentation to preserve the semantic meaning of those signatures which are necessary to make the API actually useful. I think Google could argue very successfully that literally just the API signatures should fall under fair use but that's not really what this is about.
The semantic meaning of the signatures IS the API. The whole forms the interface. This includes bugs, weird behaviour, shortcomings.