tag:blogger.com,1999:blog-23493348871730756112024-03-12T19:55:56.527-04:00EcstasyLangxtclang (Ecstasy)http://www.blogger.com/profile/10099977807321312612noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2349334887173075611.post-35413703777979887602019-06-10T15:00:00.000-04:002019-07-09T22:50:13.864-04:00Public Project<div dir="ltr" style="text-align: left;" trbidi="on">
It has been a few years in the making, but (<i>update: 9 July</i>) the wait is over, and the work begins: The Ecstasy project is public on Github at <a href="https://github.com/xtclang">https://github.com/xtclang</a>. As part of this process, the licenses (Apache 2.0 for source code, and Creative Commons CC-BY-4.0 for documentation) and the contributor agreements (Apache model for both individuals and organizations) have been published.<br />
<br />
The biggest challenge is not in the <i>publishing</i> of the existing work; that is a fairly simple, if tedious, process. The real challenge is in clearly communicating the status of the project, the target of the project, and -- quite importantly! -- who should <b>not</b> use the project.<br />
<br />
Based on our internal tracking process, what we are releasing is a version 0.1, and <i>not</i> a version 1.0. Most developers should not invest their time in a project until it nears an actual 1.0 release, because such a project is not ready for production use, and most developers are paid to work on things that are intended for production use.<br />
<br />
What actually defines a 1.0 release? For the Ecstasy project, the requirements are clear:<br />
<ul>
<li>A language specification, a runtime specification, and user documentation for the language, the runtime library, and the toolchain.</li>
<li>A native runtime implementation, with (minimally) either a JIT or an AOT native compiler.</li>
<li>A natural (Ecstasy) runtime library.</li>
<li>A natural (Ecstasy) implementation of the toolchain, including the Ecstasy compiler, the Ecstasy assembler, and the Ecstasy linker.</li>
</ul>
There are many additional "<i>nice to haves</i>" that we hope to complete before we finish the 1.0 release, but there is a reason why the other items are called "<i>nice to haves</i>" instead of "<i>requirements</i>".<br />
<br />
We will only "<i>get one chance to make a good first impression</i>", and we are determined not to waste it. We will not ask developers to waste their time attempting to use an incomplete project. We must find a way to communicate that clearly, while simultaneously opening our doors as widely as possible to those who desire to learn, contribute to the project, and propel us towards completion.</div>
xtclang (Ecstasy)http://www.blogger.com/profile/10099977807321312612noreply@blogger.com0tag:blogger.com,1999:blog-2349334887173075611.post-66082061734013142222016-11-05T21:56:00.001-04:002019-03-31T17:35:50.921-04:00Welcome to the Ecstasy Language, the first programming language built for the cloud!<br />
<br />
This is an official blog of the Ecstasy Language open source project at <a href="http://xtclang.org/">xtclang.org.</a><br />
<br />
Blogs:<br />
<ul>
<li><a href="https://xtclang.blogspot.com/">https://xtclang.blogspot.com/</a> - technical topics</li>
<li><a href="https://ecstasylang.blogspot.com/">https://ecstasylang.blogspot.com/</a> - (this blog) announcements and project-related topics</li>
</ul>
Twitter:<br />
<ul>
<li> <a href="https://twitter.com/xtclang">@xtclang</a> - Official Twitter account for the xtclang project.</li>
</ul>
Email Inquiries: <span style="font-family: "courier new" , "courier" , monospace;">info at xtclang dot org </span>xtclang (Ecstasy)http://www.blogger.com/profile/10099977807321312612noreply@blogger.com0