6 ms·

That's not the takeaway that you should have - simplicity doesn't matter if minor language versions make breaks.

knewter 8y ago
it was a rewrite of the compiler in a pre-1.0 language trying to find its preferred API. you shouldn't be surprised it broke stuff, especially when literally every thing about native explained it was a private unsupported API. calling this a minor release is idiotic and you're just mad because they took away a thing they promised to take away and said you shouldn't use.
- alluro2 8y ago
  While I agree about it being ok to break things at this stage, some of the words in your reply were a bit confusing - what do you mean a "private unsupported API" in an open source project? Kind of supports the notion that this is a private group project and others can use it, but are not welcome to participate. Also, if calling this a minor release is idiotic, why was the version number then a minor increase (at least according to commonly accepted understanding, i.e. semver) and not a 0.20 or whatever else, especially if there are breaking API changes.
  - Zyst 8y ago
    In semver versions before 1.0 are prerelease versions.
  - uryga 8y ago
    GP probably meant something like "an internal API that's exposed in case you need it but gives no guarantees about stability because it's still evolving"
  - knewter 8y ago
    > Kind of supports the notion that this is a private group project and others can use it, but are not welcome to participate. Native's existence was an implementation detail. no one using it didn't know it was likely to go away if they read anything about it from core. it was undocumented, but where you could find any documentation it said very clearly not to use it. people used it anyway. I was one. but I knew going in that it would likely disappear. > why was the version number then a minor increase (at least according to commonly accepted understanding, i.e. semver) and not a 0.20 or whatever else, especially if there are breaking API changes. https://semver.org/#spec-item-4 https://semver.org/#spec-item-4 you not understanding semver doesn't make elm bad
    - fulafel 8y ago
      Elm doesn't seem to use semver (which requires that "A normal version number MUST take the form X.Y.Z")
    - mst 8y ago
      I asked upthread about native versus ports and somebody was kind enough to mention ports were async only. But I'm still curious about exactly what people were using native for and why at least some users don't feel they can rewrite easily - care to share what you used and why, and what your thoughts are about replacing it? (the discussion around this has, so far as I've been able to see, devoid of concrete examples, and now the question's nerd sniped me :)
    - vmchale 8y ago
      Clearly the internal API existed because Evan et al. decided they needed to use it. So why did they decide it a feature that was so obviously necessary was too complicated for the hoi polloi?

it was a rewrite of the compiler in a pre-1.0 language trying to find its preferred API. you shouldn't be surprised it broke stuff, especially when literally every thing about native explained it was a private unsupported API. calling this a minor release is idiotic and you're just mad because they took away a thing they promised to take away and said you shouldn't use.

alluro2 8y ago
While I agree about it being ok to break things at this stage, some of the words in your reply were a bit confusing - what do you mean a "private unsupported API" in an open source project? Kind of supports the notion that this is a private group project and others can use it, but are not welcome to participate. Also, if calling this a minor release is idiotic, why was the version number then a minor increase (at least according to commonly accepted understanding, i.e. semver) and not a 0.20 or whatever else, especially if there are breaking API changes.
- Zyst 8y ago
  In semver versions before 1.0 are prerelease versions.
- uryga 8y ago
  GP probably meant something like "an internal API that's exposed in case you need it but gives no guarantees about stability because it's still evolving"
- knewter 8y ago
  > Kind of supports the notion that this is a private group project and others can use it, but are not welcome to participate. Native's existence was an implementation detail. no one using it didn't know it was likely to go away if they read anything about it from core. it was undocumented, but where you could find any documentation it said very clearly not to use it. people used it anyway. I was one. but I knew going in that it would likely disappear. > why was the version number then a minor increase (at least according to commonly accepted understanding, i.e. semver) and not a 0.20 or whatever else, especially if there are breaking API changes. https://semver.org/#spec-item-4 https://semver.org/#spec-item-4 you not understanding semver doesn't make elm bad
  - fulafel 8y ago
    Elm doesn't seem to use semver (which requires that "A normal version number MUST take the form X.Y.Z")
  - mst 8y ago
    I asked upthread about native versus ports and somebody was kind enough to mention ports were async only. But I'm still curious about exactly what people were using native for and why at least some users don't feel they can rewrite easily - care to share what you used and why, and what your thoughts are about replacing it? (the discussion around this has, so far as I've been able to see, devoid of concrete examples, and now the question's nerd sniped me :)
  - vmchale 8y ago
    Clearly the internal API existed because Evan et al. decided they needed to use it. So why did they decide it a feature that was so obviously necessary was too complicated for the hoi polloi?