kdanb.blogg.se - Run kotlin online

But even in those situations, I don’t want to give up all the convenience that I’ve gotten used to when using Heroku.Įnter Dokku, which unites the best of both worlds. I really like Heroku as a place to host my Kotlin apps because the time from setting up my application to having it available to the public is very short – I can confidently get my prototype applications running in the cloud in less than 10 minutes, and even if I need a database or integration with some other service, it can be spun up in mere minutes.īut there are also situations where I want to own the deployment environment for my Kotlin (mainly Ktor) web applications – for example, when I’m deploying an app that’s running in my home network, or when I want to keep the application running without continuously having to pay for always-on Heroku instances. Outdated, unsupported and does not decompile correctly Java 5 and later.In my last article, I talked about “ Publishing server-side Kotlin applications built with Ktor on Heroku”.

Probably, this is the most popular Java decompiler, but primarily of this age only. Free, no source-code available, jad download mirror Author: Pavel Kouznetsov

Supports Java up to version 6 (Annotations, generics, enums) Very promising analytical Java decompiler, now becomes an integral part of IntelliJ 14.

Java 8 Lambdas and method references (i.e., the :: operator).

Local classes (both anonymous and named).

Handles language enhancements from Java 5 and beyond, up to Java 8, including: Has its own visual interface and plugins to Eclipse and IntelliJ. It'll even make a decent go of turning class files from other JVM langauges back into java!įree for non-commercial use only, Author: Emmanuel Dupuy

Java 14: 'instance of' pattern match and 'Record types'.

Java 12: Kotlin style "switch expressions".

Regularly updated, CFR is able to decompile all the modern Java features: This free and open-source decompiler is available here: Author: Lee Benfield Here's a list of decompilers presented on this site: class file and pre-process it, so it becomes JDK 1.3 compatible, and then run Jad over it (one of those older, but better decompilers).īut recently, a new wave of decompilers has forayed onto the market: Procyon, CFR, JD, Fernflower, Krakatau, Candle. The only so-so working solution was to take the. The obsoleteness was typically proved by the fact that they can only decompile JDK 1.3 bytecode.

Until recently, you needed to use a Java decompiler and all of them were either unstable, obsolete, unfinished, or in the best case all of the above.