From: Lucretia <laguest9000@googlemail.com>
Subject: Re: What can Ada do to survive Big Tech's war-on-portability?
Date: Wed, 14 Aug 2019 15:17:37 -0700 (PDT)
Date: 2019-08-14T15:17:37-07:00 [thread overview]
Message-ID: <e2fac948-5a8a-47b1-b160-cc3239aae599@googlegroups.com> (raw)
In-Reply-To: <6bbf496c-6067-4047-ac48-d26f69bbfe4a@googlegroups.com>
On Wednesday, 14 August 2019 21:12:04 UTC+1, Optikos wrote:
> https://blogs.dropbox.com/tech/2019/08/the-not-so-hidden-cost-of-sharing-code-between-ios-and-android
>
> Dropbox has learned the hard way that the titans of Big Tech (e.g., Google, Apple, Microsoft) have erected semi-impermeable walls around their core technology that intentionally make portability difficult. Although that prior sentence is semi-obvious for decades, what could Ada do differently henceforth to not suffer the above-linked article's same fate as C++ at Dropbox?
1) Have Ada->JVM and Java bindings without GPLv3 generated code or RTS.
2) Have Swift bindings without GPLv3 generated code or RTS.
Good luck with that.
prev parent reply other threads:[~2019-08-14 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 20:12 What can Ada do to survive Big Tech's war-on-portability? Optikos
2019-08-14 21:10 ` Dmitry A. Kazakov
2019-08-14 22:17 ` Lucretia [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox