"What next?"

Aug. 18th, 2017 02:11 pm
graydon2: (Default)
[personal profile] graydon2
Warning: this has turned out to be a .. long post.

Recently, on the twitters, Stephanie Hurlburt suggested that it'd be healthy for people who have been around the computering industry for a while (*cough cough*) to take some "audience questions" from strangers. I obliged, and someone asked me an interesting one:

"After memory safety, what do you think is the next big step for compiled languages to take?"

Setting aside the fact that "compiled" languages have had various more-or-less credible forms of "memory safety" for quite a long time, I agree (obviously!) that cementing memory safety as table stakes in all niches of language design -- especially systems languages -- continues to be an important goal; but also that there's also lots more to do! So I figured I'd take a moment to elaborate on some areas that we're still well short of ideal in; maybe some future language engineers can find inspiration in some of these notes.

Before proceeding, I should emphasize: these are personal and subjective beliefs, about which I'm not especially interested in arguing (so will not entertain debate in comments unless you have something actually-constructive to add); people in the internet are Very Passionate about these topics and I am frankly a bit tired of the level of Passion that often accompanies the matter. Furthermore these opinions do not in any way represent the opinions of my employer. This is a personal blog I write in my off-hours. Apple has a nice, solid language that I'm very happy to be working on, and this musing doesn't relate to that. I believe Swift represents significant progress in the mainstream state of the art, as I said back when it was released.

That all said, what might the future hold in other languages?

so many things )

February 2017


Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Aug. 21st, 2017 02:46 am
Powered by Dreamwidth Studios