3 ms·

Alas yes! In hindsight not the best choice of tech so a Javascript rewrite might be on the cards.

Filligree 10y ago
Kotlin has a JS compilation mode, and IDEA has a java-to-kotlin converter. Maybe that's a good place to start? Kotlin is a good language anyway.
- lmm 10y ago
  Scala has both those things and is a better and more mature language.
  - mushishi 10y ago
    It is a different language to be sure but why would you say it is better? Isn't there such a many ways to look at the strengths/weaknesses of a language that simply valuing one language over another does not make much sense? (In this context, I assume that both are good enough to be possible for this project).
    - lmm 10y ago
      More consistent design - a lot of things that are special cases in Kotlin are just the logical combination of two orthogonal features in Scala (or Ceylon). That and the huge power of higher-kinded types - there are some language features where it's arguable whether they're worth their weight, but higher-kinded types are one where it's really clear-cut (IMO) - once you're used to them, using a language without them is like using a language without generics. For the sake of argument I'll accept that it's maybe difficult to compare two languages in general, but in terms of Kotlin/Scala they are extremely similar languages targeting extremely similar use cases.
      - softawre 10y ago
        We reviewed both and went with Kotlin. Scala is not the obvious choice here in my opinion. Kotlin is a simpler language which is a huge benefit. https://kotlinlang.org/docs/reference/comparison-to-scala.html https://kotlinlang.org/docs/reference/comparison-to-scala.ht...
        lmm 10y ago
        It's not a simpler language. It's a less powerful one but as a result it has a lot of ad-hoc special case features to cover subsets of functionality that Scala provides with a few powerful features applied consistently. (If you want an actually simpler language, look at Ceylon)
        airless_bar 10y ago
        I agree with lmm. The only thing where Kotlin wins is in marketing and hype.
jeffwass 10y ago
Hey SideShow B, I responded in a different comment with my old page of QM simulations I made 12 yrs ago as Java applets : http://www.pha.jhu.edu/~javalab/ http://www.pha.jhu.edu/~javalab/ I'd be very interested in how you eventually decide to update your applet to be more web friendly for current browsers, as I'd like to do the same, but know very little of modern web design. Right now only one of mine is on GitHub : Squankum, for showing operations of single-qubit operations on input qubits, both graphically and in eigenvector form : https://github.com/jeffwass/Squankum/blob/master/README.md https://github.com/jeffwass/Squankum/blob/master/README.md
scrumper 10y ago
Please be sure to repost if you do get round to porting it.
- sideshowb 10y ago
  I open sourced it, so porting might happen now.
mindcrime 10y ago
Or how about just configure it to run using JNLP, instead of running in-browser as an applet?

Kotlin has a JS compilation mode, and IDEA has a java-to-kotlin converter. Maybe that's a good place to start? Kotlin is a good language anyway.

lmm 10y ago
Scala has both those things and is a better and more mature language.
- mushishi 10y ago
  It is a different language to be sure but why would you say it is better? Isn't there such a many ways to look at the strengths/weaknesses of a language that simply valuing one language over another does not make much sense? (In this context, I assume that both are good enough to be possible for this project).
  - lmm 10y ago
    More consistent design - a lot of things that are special cases in Kotlin are just the logical combination of two orthogonal features in Scala (or Ceylon). That and the huge power of higher-kinded types - there are some language features where it's arguable whether they're worth their weight, but higher-kinded types are one where it's really clear-cut (IMO) - once you're used to them, using a language without them is like using a language without generics. For the sake of argument I'll accept that it's maybe difficult to compare two languages in general, but in terms of Kotlin/Scala they are extremely similar languages targeting extremely similar use cases.
    - softawre 10y ago
      We reviewed both and went with Kotlin. Scala is not the obvious choice here in my opinion. Kotlin is a simpler language which is a huge benefit. https://kotlinlang.org/docs/reference/comparison-to-scala.html https://kotlinlang.org/docs/reference/comparison-to-scala.ht...
      - lmm 10y ago
        It's not a simpler language. It's a less powerful one but as a result it has a lot of ad-hoc special case features to cover subsets of functionality that Scala provides with a few powerful features applied consistently. (If you want an actually simpler language, look at Ceylon)
      - airless_bar 10y ago
        I agree with lmm. The only thing where Kotlin wins is in marketing and hype.

jeffwass 10y ago

Hey SideShow B, I responded in a different comment with my old page of QM simulations I made 12 yrs ago as Java applets : http://www.pha.jhu.edu/~javalab/ http://www.pha.jhu.edu/~javalab/ I'd be very interested in how you eventually decide to update your applet to be more web friendly for current browsers, as I'd like to do the same, but know very little of modern web design. Right now only one of mine is on GitHub : Squankum, for showing operations of single-qubit operations on input qubits, both graphically and in eigenvector form : https://github.com/jeffwass/Squankum/blob/master/README.md https://github.com/jeffwass/Squankum/blob/master/README.md

scrumper 10y ago

Please be sure to repost if you do get round to porting it.

sideshowb 10y ago
I open sourced it, so porting might happen now.

mindcrime 10y ago

Or how about just configure it to run using JNLP, instead of running in-browser as an applet?