3 ms·

As a note (I think you're aware, but others might not be): that was the release candidate, this is the final release. Most importantly: some people back then r

by Vinnl 7y ago

As a note (I think you're aware, but others might not be): that was the release candidate, this is the final release. Most importantly: some people back then reported performance issues on OS X. Inkscape stated that that was a blocker for release, so presumably that's fixed now: https://mastodon.art/@inkscape/103993588384088165 https://mastodon.art/@inkscape/103993588384088165

Jare 7y ago
I came here exactly for this reason - to find out details that may have changed from RCs, and specifically for impression on the mac version, which I would install in a heartbeat if the concerns that were blocking RC have been eased. We could also talk about how the servers seem flooded and what that means about the popularity and future of Inkscape. To see totally relevant discussions killed like this is disheartening.
- dang 7y ago
  I hear you, and I'm sorry. I'd like it if my post upthread could at least convince you that it is a structural consequence of how HN was designed—the very constraints that make it good at some things make it bad at others—but maybe that's too much to hope for. There are past explanations of this phenomenon—not the project release issue, but the disheartening part—at https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20scarce&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... if you or anyone cares to look.
  - Jare 7y ago
    I can't agree with the very concept that discussion about a final release has plenty of meat and is relevant separately from a release candidate. Plenty of people will not install a release candidate (me among them). As such we have nothing to add there, but will try a 1.0 and then become not just a spectator but a part of the discussion. I think it's a fair assessment to say many people may be in a similar position, just going by the difference in download server availability. Ah well.
    - dang 7y ago
      It's clear that the final release is by far the most significant in the real world. If there were a way to defer the big discussion till then, that would be best. In principle, there's no harm in waiting (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20%22no%20harm%20in%20waiting%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). But as I covered above, I don't see how we could get away with that. It would lead to even more complaints about threads being killed prematurely.
  - Vinnl 7y ago
    Just since you took the time to update your previous comment: I think the current situation is not that bad. People who particularly care about this release might end up on this page anyway (e.g. because they submitted it themselves), and can still discuss it, see the relevant links posted here, and discuss the diff against the RC. Thanks for the moderation work. Edit: Also, I hadn't seen the comment update you posted the last time: > That makes this post a duplicate by HN's rule (see [2]). I won't bury this one, but when this comes up again in a few weeks, let's not have a third thread. I wasn't aware of this, or I wouldn't have reposted. Sorry!
    - dang 7y ago
      Actually I think the points you're making in this comment here are good ones, so I'm glad you did post it. "Let's not have a third thread" really just means a major thread on the front page. HN has quite a lot of non-frontpage slots :)

by Vinnl 7y ago

Jare 7y ago

I came here exactly for this reason - to find out details that may have changed from RCs, and specifically for impression on the mac version, which I would install in a heartbeat if the concerns that were blocking RC have been eased. We could also talk about how the servers seem flooded and what that means about the popularity and future of Inkscape. To see totally relevant discussions killed like this is disheartening.

dang 7y ago
I hear you, and I'm sorry. I'd like it if my post upthread could at least convince you that it is a structural consequence of how HN was designed—the very constraints that make it good at some things make it bad at others—but maybe that's too much to hope for. There are past explanations of this phenomenon—not the project release issue, but the disheartening part—at https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20scarce&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... if you or anyone cares to look.
- Jare 7y ago
  I can't agree with the very concept that discussion about a final release has plenty of meat and is relevant separately from a release candidate. Plenty of people will not install a release candidate (me among them). As such we have nothing to add there, but will try a 1.0 and then become not just a spectator but a part of the discussion. I think it's a fair assessment to say many people may be in a similar position, just going by the difference in download server availability. Ah well.
  - dang 7y ago
    It's clear that the final release is by far the most significant in the real world. If there were a way to defer the big discussion till then, that would be best. In principle, there's no harm in waiting (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20%22no%20harm%20in%20waiting%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). But as I covered above, I don't see how we could get away with that. It would lead to even more complaints about threads being killed prematurely.
- Vinnl 7y ago
  Just since you took the time to update your previous comment: I think the current situation is not that bad. People who particularly care about this release might end up on this page anyway (e.g. because they submitted it themselves), and can still discuss it, see the relevant links posted here, and discuss the diff against the RC. Thanks for the moderation work. Edit: Also, I hadn't seen the comment update you posted the last time: > That makes this post a duplicate by HN's rule (see [2]). I won't bury this one, but when this comes up again in a few weeks, let's not have a third thread. I wasn't aware of this, or I wouldn't have reposted. Sorry!
  - dang 7y ago
    Actually I think the points you're making in this comment here are good ones, so I'm glad you did post it. "Let's not have a third thread" really just means a major thread on the front page. HN has quite a lot of non-frontpage slots :)