You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.
Ok folks, we haven't had much development over the past few years, even if we managed to assemble a release in Fall 2021 😉
While we've all moved to other priorities in our personal and professional lives I think the main problem with the Golo code base is migrating past Java 8 (see #504). Lots of assumptions in how the Golo runtime and code generation work have been made in a pre-JPMS model where we could freely peak into classes, unlock reflective access, and more. As time flies by it's clear none of us has managed to go past the fundamental problems JPMS introduced in Java 9.
That's why I propose to close the chapter of Golo at the Eclipse Foundation, and unless people have a different opinion and/or want to step in I'll open a termination review early September 2022. In such a case I'd like the foundation to mark the repository as archived so we don't loose all history. Or at least it'd be ok to transfer back the repo + issues to the golo-lang organisation so we could archive it ourselves.
On a more personal note I have to say that creating and nurturing this project has been a very fun chapter of my life. I'm proud of all of you who've contributed to Golo, and by contributing I don't just mean code. Seeing some of you give talks, write blogs or just have a little fun with what many saw as a toy language has made me incredibly humble and proud 🙏
I learned a lot thanks to Golo (better coding, discovering Java, participating in an OSS project, experimenting, ...). I was able to do my first conferences thanks to Golo (even internationally). Thanks for all that. Thank you, @jponge, for taking me on this adventure.
Ok folks, we haven't had much development over the past few years, even if we managed to assemble a release in Fall 2021 😉
While we've all moved to other priorities in our personal and professional lives I think the main problem with the Golo code base is migrating past Java 8 (see #504). Lots of assumptions in how the Golo runtime and code generation work have been made in a pre-JPMS model where we could freely peak into classes, unlock reflective access, and more. As time flies by it's clear none of us has managed to go past the fundamental problems JPMS introduced in Java 9.
That's why I propose to close the chapter of Golo at the Eclipse Foundation, and unless people have a different opinion and/or want to step in I'll open a termination review early September 2022. In such a case I'd like the foundation to mark the repository as archived so we don't loose all history. Or at least it'd be ok to transfer back the repo + issues to the
golo-lang
organisation so we could archive it ourselves.On a more personal note I have to say that creating and nurturing this project has been a very fun chapter of my life. I'm proud of all of you who've contributed to Golo, and by contributing I don't just mean code. Seeing some of you give talks, write blogs or just have a little fun with what many saw as a toy language has made me incredibly humble and proud 🙏
/cc Top contributors @yloiseau @artpej @k33g
The text was updated successfully, but these errors were encountered: