3 ms·

What other people actually use matters a lot though. Hell, a greater proportion of Java devs ca. 2002 probably knew how to AOT-compile their programs than do to

What other people actually use matters a lot though. Hell, a greater proportion of Java devs ca. 2002 probably knew how to AOT-compile their programs than do today. Using minority tooling in a popular language is often just as painful as using a minority language.

pjmlp 4y ago
That is orthogonal to what language implementations can do, failure to education doesn't change what tools are available.
- morelisp 4y ago
  Only in a vapid purely existential sense of "available".
  - pjmlp 4y ago
    It is available, if people don't want to pay for them, and prefer free beer stuff, it is another matter.
- coldtea 4y ago
  It's actually the opposite: The availability of a half-arsed, hardly supported, restricted compared to regular JVM based runs feature, dumped at some point by SUN so that they could say they also have it, doesn't mean people should use it, or that a platform is as good in that aspect as another who has that feature as a fully supported, first class, default mode. Don't be excited by mere presence of a feature. Implementation, maturity (which is different than "age of introduction"), completeness, support, and usage, matter...
  - pjmlp 4y ago
    Ah the proof of not have the slightest idea of what you are talking about, given that those commercial AOT features were never sold by Sun in first place, with exception of Embedded Java deployments. If we go down the implementation, maturity route, than even there are several half-arsed, hardly supported capabilities in Go compared with the JVM ecosystem, even after 10 years of existence.
    - coldtea 4y ago
      >Ah the proof of not have the slightest idea of what you are talking about, given that those commercial AOT features were never sold by Sun in first place, with exception of Embedded Java deployments. Didn't wrote sold, said "dumped at some point by SUN so that they could say they also have it". But thanks for the ad hominem. >If we go down the implementation, maturity route, than even there are several half-arsed, hardly supported capabilities in Go compared with the JVM ecosystem, even after 10 years of existence. Sure. Just not related to the ability of building a static binary.

pjmlp 4y ago

That is orthogonal to what language implementations can do, failure to education doesn't change what tools are available.

morelisp 4y ago
Only in a vapid purely existential sense of "available".
- pjmlp 4y ago
  It is available, if people don't want to pay for them, and prefer free beer stuff, it is another matter.
coldtea 4y ago
It's actually the opposite: The availability of a half-arsed, hardly supported, restricted compared to regular JVM based runs feature, dumped at some point by SUN so that they could say they also have it, doesn't mean people should use it, or that a platform is as good in that aspect as another who has that feature as a fully supported, first class, default mode. Don't be excited by mere presence of a feature. Implementation, maturity (which is different than "age of introduction"), completeness, support, and usage, matter...
- pjmlp 4y ago
  Ah the proof of not have the slightest idea of what you are talking about, given that those commercial AOT features were never sold by Sun in first place, with exception of Embedded Java deployments. If we go down the implementation, maturity route, than even there are several half-arsed, hardly supported capabilities in Go compared with the JVM ecosystem, even after 10 years of existence.
  - coldtea 4y ago
    >Ah the proof of not have the slightest idea of what you are talking about, given that those commercial AOT features were never sold by Sun in first place, with exception of Embedded Java deployments. Didn't wrote sold, said "dumped at some point by SUN so that they could say they also have it". But thanks for the ad hominem. >If we go down the implementation, maturity route, than even there are several half-arsed, hardly supported capabilities in Go compared with the JVM ecosystem, even after 10 years of existence. Sure. Just not related to the ability of building a static binary.