Cameron Purdy will be talking about the future of computing using the Ecstasy programming language.
Ecstasy at the NY Java SIG (meetup link) (EventBrite link)
2022/11/10
4 comments:
All comments are subject to the Ecstasy code of conduct. To reduce spam, comments on old posts are queued for review before being published.
Subscribe to:
Post Comments (Atom)
Thanks for the presentation! It was the first time I really got what you were trying to do.
ReplyDeleteThanks! Unfortunately, you came through as "anonymous" on your comment. What was your take-away (good, bad, etc.)?
DeleteOne of the things that became clear that wasn't really before was that the container you were building was the important thing and that the language was meant to implement the semantics of container.
DeleteThe Ectasy byline was 'a language built for the cloud'. Originally I thought that it was another ballerina (https://ballerina.io/) but it's closer to Elixir/Erlang in that those language are built around a special purpose VM (Beam) whose libraries (OTP in particular) and languages (many at this count) implement that semantics. What you're trying to do is different from Erlang but it's closer to that than most other things.
I'm not a language designer so I didn't follow everything towards the end...but I at least understand where to place it now.
Exactly. Ecstasy the language only exists because the new XVM runtime model (designed for the serverless cloud, for edge compute, and for modern devices and browsers) didn't have a language that could support it.
DeleteOr, as the saying goes: "Form follows function."