7 ms·
It's a Java applet?
by mcguire 10y ago
It's a Java applet?
- sideshowb 10y agoAlas yes! In hindsight not the best choice of tech so a Javascript rewrite might be on the cards.
- Filligree 10y agoKotlin 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 agoScala has both those things and is a better and more mature language.
- mushishi 10y agoIt 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 agoMore 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 agoWe 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 agoIt'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 agoI agree with lmm. The only thing where Kotlin wins is in marketing and hype.
- jeffwass 10y agoHey 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 agoPlease be sure to repost if you do get round to porting it.
- sideshowb 10y agoI open sourced it, so porting might happen now.
- mindcrime 10y agoOr how about just configure it to run using JNLP, instead of running in-browser as an applet?
- Vendan 10y agoAnd doesn't have any way to download it or anything. Java in browsers is officially a bad choice, people, as Chrome refuses to work with it.
- edejong 10y agoTechnically, Chrome refuses to work with NPAPI, which Java depends on. Unfortunately, Oracle did not deliver any alternative to run Java in some of the more secured browser-plugin architectures.
- Vendan 10y agoWell, Oracle has also deprecated java in the browser, so...
- mindcrime 10y agoYou could just as easily argue that "Chrome as a browser is a bad choice" for that reason.
- Vendan 10y agoor that NPAPI is really old, and that oracle is discontinuing their browser java plugin. Do you really think you can argue that Chrome is a bad choice cause it doesn't support something that is deprecated?
- mindcrime 10y agoThe thing about NPAPI is that it was at least a somewhat universally supported standard... and after dropping NPAPI, all Chrome offers is NaCL and PNaCL, which - AFAIK - nobody else supports. So you could argue that Chrome took a step backwards by dropping NPAPI before waiting to see if NaCL/PNaCL (or something else) would become the industry standard replacment for NPAPI. I am, of course, just "playing devil's advocate" here a bit. NPAPI clearly had issues and I'm not enough of an expert to say if it would have been possible to simply improve it, or whether it was truly necessary to go to a whole new model. And you can certainly argue that the other browser vendors could adopt NaCL / PNaCL. I guess they have their reasons for not doing so. It's sad really, because "Java on the Web" has a ton of value, but Sun screwed the pooch years ago with some of their decision making, leaving us where we are now. Oh well, at least there is JWS / JNLP. Hmm... come to think of it, I wonder if the OP could just rework their app to run as a JWS app, instead of as an applet? That might make everybody happy...
- deleted 10y ago[deleted]
- Myrmornis 10y agoYou have something interesting to say?