Hello HN community. JSweet.org creator/maintainer here. Being an individual and having other projects right now, I don't have much time to maintain JSweet anymore. I am looking for an organisation that would be interested in taking over the maintenance and / or ownership. Would anyone have an idea or connection to introduce? I would be grateful for any suggestion.
Ask HN: Anyone Interested in Taking over Jsweet.org?
1–10 of 17 posts
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#2clickable link: https://www.jsweet.org/ - A transpiler from Java to TypeScript/JavaScript
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#3A bunch of people will come out of the woodwork drawn to the idea of being able to immediately walk into managing a popular project, but it'll end poorly. If your project has outgrown you, or you've outgrown your project, then you can either shut it down gracefully or transition into community ownership (by finding people who have a demonstrable pre-existing interest in the project itself and allowing them to take over).
Shutting the project down gracefully doesn't mean it has to end, and it doesn't mean failure: shutting down the project gives invested community members the chance to fork it and demonstrate that they want to put the work in to run a natural successor to your project, and people will naturally gravitate towards the best fork over time. Afterall, without people with a vision leading it, it's just code.
Handing over ownership feels cleanest but it's rarely the best outcome (unless you're handing it over to a natural successor).
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#4A bunch of people will come out of the woodwork drawn to the idea of being able to immediately walk into managing a popular project, but it'll end poorly. If your project has outgrown you, or you've outgrown your project, then you can either shut it down gracefully or transition into community ownership (by finding people who have a demonstrable pre-existing interest in the project itself and allowing them to take ov…
They're explicitly looking for an organisation, not individuals, which should filter out most of this.
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#5clickable link: https://www.jsweet.org/ - A transpiler from Java to TypeScript/JavaScript
I can see the value if working with js, less so with ts. I'd done some work with GWT in the past and the Java -> js part worked great. A problem I can see when working with ts is not having the ts libraries imported into Java's types.
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#6A bunch of people will come out of the woodwork drawn to the idea of being able to immediately walk into managing a popular project, but it'll end poorly. If your project has outgrown you, or you've outgrown your project, then you can either shut it down gracefully or transition into community ownership (by finding people who have a demonstrable pre-existing interest in the project itself and allowing them to take ov…
They're explicitly looking for an organisation, not individuals, which should filter out most of this.
Yes indeed
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#7clickable link: https://www.jsweet.org/ - A transpiler from Java to TypeScript/JavaScript
I can see the value if working with js, less so with ts. I'd done some work with GWT in the past and the Java -> js part worked great. A problem I can see when working with ts is not having the ts libraries imported into Java's types.
JSweet comes with a TS definition files to Java translator (.d.ts to .java). So when you have the TS definition file, you can generate the correspond Java API on-the-fly or use a pre-translated/pre-compiled definition in so-called "candies". The candies are just here for typing in Java and ensure that you have the exact same API as in TS. Then JSweet generates intermediate TS code, which is compiled against the original TS definition. This 2-step transpilation process ensures that the generated code is correct and well-typed. In the end, you can work either directly with the JS code or the TS code depending on what you need.
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#8A bunch of people will come out of the woodwork drawn to the idea of being able to immediately walk into managing a popular project, but it'll end poorly. If your project has outgrown you, or you've outgrown your project, then you can either shut it down gracefully or transition into community ownership (by finding people who have a demonstrable pre-existing interest in the project itself and allowing them to take ov…
Shutting down the projet and/or change the OS license to make it easier to fork is a potential option. However, I think it's worth asking if some organisation could be interested first. I believe JSweet could be more helpful if it was backed by some org that would have a use case of JSweet and maintain it for it's own purpose.
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#9Earlier quoted context omitted.
I can see the value if working with js, less so with ts. I'd done some work with GWT in the past and the Java -> js part worked great. A problem I can see when working with ts is not having the ts libraries imported into Java's types.
JSweet comes with a TS definition files to Java translator (.d.ts to .java). So when you have the TS definition file, you can generate the correspond Java API on-the-fly or use a pre-translated/pre-compiled definition in so-called "candies". The candies are just here for typing in Java and ensure that you have the exact same API as in TS. Then JSweet generates intermediate TS code, which is compiled against the origi…
Ok now that's cool!
Re: Ask HN: Anyone Interested in Taking over Jsweet.org?
#10Didn't know about that project. Looks awesome. What are some cool java libraries to use in node.js?