While I do find Pony interesting from a technical perspective, I’ll admit that publishing every point release changelog to lobsters is an extremely generous understanding of what some of us would like the “release” tag to showcase.
Major features? Sure. Security fixes, yes. But:
Pony 0.23.0 is primarily a bug fix release but does also include some additional changes. Upgrading is recommended. There is a single breaking change caused by the implementation of RFC 56.
Yeah, I’d be fine with a post when notable, interesting things have been added/removed/changed. Pony is an interesting language! But yeah, posting this one seems like it is wasting a bit of goodwill.
as I write this, this story is hidden by 8, +10, -5 spam, which indicates to me that might be better to refrain unless there is a major milestone, or an interesting new feature that might spur some discussion.
Adding some additional commentary about why the breaking type change is interesting or useful might help; there are enough language implementation nerds who read lobsters regularly that it could generate some discussion, especially since the capability types are one of pony’s most compelling and novel features.
As an outsider who doesn’t use Pony, I find the constant stream of releases a bit tedious. Why do a new release just to fix one or two bugs? The current release pace feels excessive even if they’re not being announced on lobste.rs
While I do find Pony interesting from a technical perspective, I’ll admit that publishing every point release changelog to lobsters is an extremely generous understanding of what some of us would like the “release” tag to showcase.
Major features? Sure. Security fixes, yes. But:
is arguably less interesting.
Yeah, I’d be fine with a post when notable, interesting things have been added/removed/changed. Pony is an interesting language! But yeah, posting this one seems like it is wasting a bit of goodwill.
as I write this, this story is hidden by 8, +10, -5 spam, which indicates to me that might be better to refrain unless there is a major milestone, or an interesting new feature that might spur some discussion.
Adding some additional commentary about why the breaking type change is interesting or useful might help; there are enough language implementation nerds who read lobsters regularly that it could generate some discussion, especially since the capability types are one of pony’s most compelling and novel features.
I wont be posting releases to lobsters anymore.
I don’t think anyone wants you to stop posting releases. They are just expecting more from each post.
Perhaps. Either way. Not submitting them anymore.
As an outsider who doesn’t use Pony, I find the constant stream of releases a bit tedious. Why do a new release just to fix one or two bugs? The current release pace feels excessive even if they’re not being announced on lobste.rs