91–100 of 156 posts
Google should have acquired Sun instead of buying dropcam/boston-dynamics/motorola and such.
Let's give Oracle 10 years from now to fade from relevance as yet another fucked by cloud vendor and Google can then orchestrate a hostile takeover.
I was thoroughly impressed with the judge who presided over the last ruling -- IIRC he went so far as to learn at least the basics of Java to the point where I remember being impressed by the insight of the questions he posed. There are subsets of law one can specialize in ranging from medical malpractice to obscure patent litigation, but as far as I know there are no factors linking a presiding judge to a specific s…
On software like JDK, my feeling (without thinking too much) is that the API is actually the most valuable part and the one that requires true expertise to craft.
Imagine if Microsoft granted Google a perpetual license to use C#.
Google should have acquired Sun instead of buying dropcam/boston-dynamics/motorola and such.
How amazing would that have been? Zfs might have helped the world move forward a lot faster... Sigh... Let's give Oracle 10 years from now to fade from relevance as yet another fucked by cloud vendor and Google can then orchestrate a hostile takeover.
FYI, Oracle is pushing this agenda to squeeze Java shops in other places as well. The tack they are taking is to define any computer that does "one specific thing" as an embedded device and ask you for $300+ per "device", plus some other lofty fees. ( http://www.oracle.com/us/corporate/pricing/price-lists/java-... ) So, if you're using Java in a kiosk, ATM, media player, etc, they may be coming for you. My guess is t…
Oracle should pay Google for using Java in Android and keeping the language somewhere around edge of hip and cool. I wonder how long it will be before Google flips to Go or JavaScript for Android.
I don't think anyone has used "hip and cool" and "Java" in the same sentence for at least 15 years (2001) and no amount of Android can fix that.
Earlier quoted context omitted.
Not more difficult per se, but more obfuscated. So much brands, paradigms, domain specific metalanguage. Medicine, physics have some kind of shared, time-tested foundations.
>Medicine, physics have some kind of shared, time-tested foundations. So do programming languages.
Earlier quoted context omitted.
Not more difficult per se, but more obfuscated. So much brands, paradigms, domain specific metalanguage. Medicine, physics have some kind of shared, time-tested foundations.
>Medicine, physics have some kind of shared, time-tested foundations. So do programming languages.
Earlier quoted context omitted.
I don't think anyone has used "hip and cool" and "Java" in the same sentence for at least 15 years (2001) and no amount of Android can fix that.
Kotlin? :) --> https://kotlinlang.org/
Earlier quoted context omitted.
On software like JDK, my feeling (without thinking too much) is that the API is actually the most valuable part and the one that requires true expertise to craft.
Why do you think so? The java.* API is not even that good (it is very verbose to achieve basic things). The only reason to re-implement it is compatibility with existing, third-party software using that API. If you would come with API, that would be technically better, but doing the same thing, do you think that everyone would rewrite all their libraries, frameworks and apps? No way.
Oracle apparently bamboozled the Federal Circuit into deciding that something called the "structure, sequence and organization" of the API should be copyrightable. But of course nobody cares about that part -- the order doesn't matter. You can sort the API into alphabetical order and strip out all the comments and it would make no real difference to anybody. But here is Oracle claiming that the copyrightable part is worth billions of dollars.