My understanding is all kids moved to Instagram / Snapchat as soon as parents started using Facebook too, and now parents are on Instagram too so I expect kids are already using something else.
Kinda? There's other patent issue with HLS that keeps it mostly Apple only since Apple foots the costs on apple products, which can be similarly argued creates/continues an unfair barrier of entry: http://www.overdigital.com/2012/04/17/the-hidden-licensing-c...
But being required to license anything in order to implement what is a supposed to be an open standard is already a problem for a standard that's supposed to be open, even if it's not an antitrust issue.
> Can people use or license Apple's version of DRM instead?
There's no public mechanism for doing so. If Apple would do so to people it liked is not known.
You could license PlayReady from Microsoft though, and lots of people do for various implementations. There are also a few other companies that do similar modules, mostly aimed at the global pay TV market.
The terms would be fairly painful for a free browser vendor I expect, but "I priced my product at a level where I can't afford to buy in the things my users want from any of the independent vendors" isn't really an anti-trust concern.
> Why was anti-trust pursued against Microsoft then?
One example among the many things the court found they did was to tell OEMs that they wouldn't license Windows to them if they _also_ included Netscape preinstalled in their computers.
The stated purpose, from internal emails, was to prevent Java from becoming the de-facto API for writing applications, which at the time was win32. This was a gigantic barrier of entry that protected Windows' monopoly and they did all those shady things to keep it raised.
Hermetic Builds. ... Our builds are hermetic, meaning that they are insensitive to the libraries and other software installed on the build machine. Instead, builds depend on known versions of build tools, such as compilers, and dependencies, such as libraries.
Kind of like a container for building? I had to look it up myself.
That, and also insensitive to builds you might have done of other versions of the source code, etc. I.e. it's not affected by "files left behind" that would require you to do a clean build and lose incrementality.
I don't know if this is what the parent was intending (I'm curious to see other examples), but depending on your definition Nix (nixos.org) seems to fit that need.
What tooling? Being forced to use InteliJ, without any proper support on Eclipse and Netbeans?
Still not able to use several of Android Studio features available to Java, like incremental compilation and slim APKs?
Kotlin advocates seem to forget JVM will never be rewritten in Kotlin, the language is just yet another guest, with the usual syndrome to wrap existing libraries, having to take care about FFI for Java access, not having all features taking advatange of the latest bytecodes, e.g. lambdas implementation.
As for Kotlin/Native, there is nothing to worry about versus what Go, Rust, C++, Dart, D, Nim offer in terms of performance, libraries and in some cases tooling.
Having to buy CLion for a graphical debugger isn't a selling point versus the established alternatives.
Fuchsia is being written in Go, Rust, C++ and Dart, with the team now hiring for node.js support.
>What tooling? Being forced to use InteliJ, without any proper support on Eclipse and Netbeans?
Seeing that both Eclipse and Netbeans are now more or less dead (and speaking as a long time Eclipse user, from the very first version to around 4), yes, first class vendor-direct InteliJ support is more than enough. And more than most languages (including Groovy) ever had.
>As for Kotlin/Native, there is nothing to worry about versus what Go, Rust, C++, Dart, D, Nim offer in terms of performance, libraries and in some cases tooling.
IMHO, Rust will always be kind of niche as hard to tackle, Dart we'll see, D never went anywhere, and Nim will remain niche, it's a little too idiosyncratic to catch on.
Kotlin is already more popular than all of the above except perhaps Go.
>Fuchsia is being written in Go, Rust, C++ and Dart, with the team now hiring for node.js support.
Fuchsia is still vaporware or at least irrelevant. It's not even in the market yet. And the fact that it's written in 4 (and looking for 5th) languages doesn't really bring much confidence.
Groovy had Netbeans and Eclipse support, which was dropped when it started fading away.
We move in different worlds, no InteliJ installations around here.
I remember when Groovy was popular, with every JUG in Germany having weekly talks and Sun talking how the next JEE revision would support Groovy for writing beans.
>Groovy had Netbeans and Eclipse support, which was dropped when it started fading away.
I know, I've used it. What I said is that it did not have the first class IDE attention of a major vendor, those were mostly third party sub-par plugins compared to the Java focus of those IDEs. For Kotlin, however, it was first class IDE support as a primary concern from the start.
>We move in different worlds, no InteliJ installations around here.
Then we indeed move in different worlds.
>Popularity doesn't write software.
No, its just the only thing that matters when it comes to get paid for it.
I don't understand how Groovy is fading away when it is getting more and more popular. Groovy is also very similar to Java. There is no learning curve, you are immediately creating value.
Google Trends says Groovy is just as popular as it was 10 years ago. The number of downloads has increased significantly but it is not because of Gradle, as Gradle bundles Groovy.
It is also currently placed #16. on TIOBE Index
And last, Groovy with compile static is in most cases, just as fast and memory efficient as Java.
Some people always talk down Groovy, yet the numbers speak for them self. Before Kotlin, Groovy was attacked by Scala developers.
The major thing Groovy has over both Scala and Kotlin is strong similarity to Java syntax which makes the learning curve non-existing. And that is a bigger deal than a random cryptic/confusing programming expression. Code readability is very important.
> Some people always talk down Groovy, yet the numbers speak for them self
Many of those numbers are fake. Groovy was #70 on the Tiobe index only 12 months ago, see [1], but is #16 now. How do you explain that? Groovy was last in Tiobe's top 20 about 2 years ago when the search numbers for "Groovy" from Baidu were hugely incorrect. Groovy later quickly dropped back out of the top 50.
Fuchsia is language agnostic. This is a boon. Writing for Fuchsia isn’t like writing for Unix where C is king. Fuchsia is able to natively host many more ecosystems than Linux cares to bother with. It gives me great confidence.
Tons of great stuff for Unix is written in C++ and other languages all the way to Python and Java. You can write Unix apps in whatever language you want. Ditto for Windows and MacOS.
Not sure what the special deal is with Fuchsia here.
Perhaps you think you'll be able to write Fucshia device drivers with any language you like? That wont be the case at all.
Also Linux has this going in its favor over Fucshia: it actually exists.
That won't get kotlin more traction. No proper/official tools for LSP support means no vscode, vim, emacs etc. users. As a happy eclipse user, I wouldn't call it dead either.
>Not every Java shop is going to drop Eclipse and Netbeans just to make JetBrains happy.
True. They will drop them because Eclipse has been faltering for ages and has been dropped by IBM, and Netbeans has always been a subpar unloved stepchild used by the kind of devs that don't know better and think SlickEdit or Notepad++ are great editors.
>The overwhelming majority of Java developers don't even know who Steve Yegge is.
>I guess Fortune 500's have missed that memo, including IBM own subsidiaries.
They probably did. They're late for all memos. The Fortune 500 is not were you'll go to gauge adoption. Heck, half of them still have IE6 only apps.
There are hundreds of thousands of companies, and just 500, well, Fortune 500.
Apparently you use the most established and boring development-wise of companies (Fortune 500) to prove Kotlin is not used widely, but you're OK with vaporware like Fucscia that's not even beta yet as an argument that Dart and co are.
>I am betting Kotlin would become yet another language that happens to compile to the JVM
And I bet you're wrong. Let's see in 5 years. We were on HN 10 years ago, we'll probably be here then. I'll set a reminder.
Specifically every link they every clicked on, on every web site.
Yes some fraction of this was on google. That's not cheating. No content from google was transmitted back to Bing. Just the next site the users went to. Is Bing supposed to go through the logs looking for visits to google and then delete the rest of the session because it might indirectly reveal something about what existed on the google page?
I should own my records about what pages I go to, not Google. If I share them with Bing it's nobody else's business.
> every link they every clicked on, on every web site. [...] No content from google was transmitted back to Bing. Just the next site the users went to.
Your theory cannot explain how Bing associated that "next site" with the specific search term the user had entered in Google.
If you had clicked a link on HackerNews, it wouldn't have shown up in Bing under some random search phrase. It's obvious that Microsoft parsed the search query out of the google.com URL, and the only reason why you'd do that is to mine what results were being presented for each search query.
