• 3 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle





  • I don’t think we know that yet, and I think the discovery will be interesting.

    How many reports were there? Were they credible? What other sources of truth did Google consult in deciding to ignore those reports?

    Google gets lots of reports and needs to filter out spam, and especially malicious reports like trying to mark a competitor’s business as closed, or trying to get less traffic in your neighborhood for selfish reasons. It wouldn’t be reasonable for Google to accept every user suggestion either.

    So if Google reached out to the town and the town said the bridge is fine, then it’s not Google’s fault. If they ignored multiple credible complaints because the area was too rural to care about, that might be negligent.




  • Wasn’t she an unknown, while they were all famous stars, though?

    The same happens today.

    “The cast of Moana earned a total of $56 million. Auli’i Cravalho, who voiced the title character, made $200,000. Dwayne Johnson, who voiced Maui, earned $21 million. Temuera Morrison, who voiced Moana’s father, earned $2 million.”

    I’m not excusing any of the ways they abused Garland. But it made her a star and she earned far more in future roles, just like Cravalho now commands a much higher salary.







  • First of all, since the very early days Android has always allowed apps to make use of native code using the “NDK”, and in fact most games and most apps that do any sort of AI, image processing, or anything else complex like that make heavy use of native code already, for performance reasons.

    Keep in mind that the decision to base Android apps around Java was made back in 2003 when Android was founded. Some of the reasons they picked Java were:

    • It’s one of the most widely known languages by developers
    • It’s hard to write code in languages like C and C++ without introducing memory bugs and security bugs. Using a higher-level language makes those bugs far less common.
    • It’s portable - you note that Android only supports arm64 now, but at the time it was arm32, and Android has actually always had some level of support for x86 - you can run the emulator for x86, and some x86 Android devices exist. Using a bytecode language means Android is future-proof
    • It’s not limited to just Java - the JVM has a rich ecosystem of languages that developers can use

    Now 20 years later I think it’s worked out pretty well. It’s hard to imagine picking a different language would have worked out better. Java is still just as popular as ever, and Android developers can take advantage of all of the Java tools from any other platform or application.

    Apple’s original option for iOS apps was just Objective-C, which is higher-performance, but overall it’s a more obscure, difficult to use language. Developers adopted it despite Obj-C, not because of it. Apple had to invent Swift to provide a more modern alternative, because Obj-C is basically not used anywhere else and it felt very ancient. While Swift is a pretty great language, it’s still somewhat obscure, only used for iOS and Mac apps - while Java and JVM languages are used everywhere.

    Anyway, let’s say that Android really did want to switch, for some reason. I’m not sure why you think switching to compiled code would be less complex. How would all of the millions of existing Android apps migrate? What native languages would be supported? It’d be a huge transition for dubious benefits.

    As it is, Android is extremely flexible. While the official APIs require a JVM language, because of the NDK you can basically write Android apps in whatever language you want. People have built frameworks enabling you to build Android apps in nearly every language under the sun.