On Wed, Jul 15, 2015 at 2:03 AM, Keean Schupke <ke...@fry-it.com> wrote:
> To clarify, I was not criticising Java, C#, Swift or other similar
> languages. I was trying to discuss how dynamic loading might be done in a
> general purpose systems language like BitC.

Don't worry, I did't think you were criticizing languages with
built-in non-fragileness. Thing is though, I thought it was already
settled that BitC would be non-fragile. If so, it presumably wouldn't
handle dynamic loading your way. Or at least not publicly; it's a
possible implementation.

> If I were to criticise Swift, it would be for its proprietary nature.
> Although it is now open source, its design is still under proprietary
> control. It really needs independent control of its specification, whether
> the implementation is open source is far less important.

Sneaky. But if the implementation is really open source, then I figure
it should be legal to fork both the implementation and the
specification of the language it's implementing. In other words, the
community can fork off a community-controlled dialect if they want.
The tough part is convincing developers to use the community dialect.

> An openly specified modern safe dynamic language taking the best ideas from
> Java, C# and Swift would be great. Apple and Microsoft can compete with
> their proprietary implementations and make sure the dynamic loading
> abstraction is well implemented on their respective architectures.

Of course Apple and Microsoft would much prefer to not have to compete
with each other on technical grounds. They'd rather have monopolies on
their own, mutually incompatible ecosystems, supported by the mass of
legacy code that depends on them. Sucks for everyone else.

So yes, a modern language, well-supported by all major platforms would
be great. Apple and Microsoft are probably not so dumb that they'd let
it happen. (JavaScript doesn't count. Yuck.)
_______________________________________________
bitc-dev mailing list
bitc-dev@coyotos.org
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to