When comparing SideBar Enhancements vs Kotlin, the Slant community recommends SideBar Enhancements for most people. In the question“What are the best plugins for Sublime Text?” SideBar Enhancements is ranked 2nd while Kotlin is ranked 32nd. The most important reason people chose SideBar Enhancements is:
- Move to trash - Clipboard - Open in browser - Copy the content of a file as data:uri base64 - Close, move, open and restore buffers affected by a rename/move command - Copy as tags img/a/script/style - Duplicate - Preference to control if a buffer should be closed when affected by a deletion operation - Allows to display "file modified date" and "file size" on statusbar
Ranked in these QuestionsQuestion Ranking
Pro Adds a ton of functionality to the sidebar
- Move to trash
- Open in browser
- Copy the content of a file as data:uri base64
- Close, move, open and restore buffers affected by a rename/move command
- Copy as tags img/a/script/style
- Preference to control if a buffer should be closed when affected by a deletion operation
- Allows to display "file modified date" and "file size" on statusbar
Pro Great tooling support
Since Kotlin is made by Jetbrains (the developers of IntelliJ IDEA) so it stands to reason that the IntelliJ support for Kotlin is also great. Besides that, Kotlin also works well with existing Java tools such as Eclipse, Maven, Gradle, Android Studio, etc...
Pro Easy adoption for existing Java programmers
Kotlin runs on the JVM and Java interoperability has been one of the main objectives since the language was born. It runs everywhere Java does; web servers, mobile devices (Android), and desktop applications. It also works with all the major tools in the Java ecosystem like Eclipse, IntelliJ, Maven, Ant, Gradle, Spring Boot, etc.
All of this makes adoption extremely easy even for existing Java projects. On top of this there's also ensured Type safety and less boilerplate code needed.
Pro Easy to learn if you have prior programming experience
Kotlin's syntax is extremely easy to understand. The language can be picked up in a few hours just by reading the language reference.
Pro No runtime overhead
The standard library is relatively small and tight. It mostly consists of focused extensions of the Java standard library and as such adds no additional runtime overhead to existing Java projects.
Pro Officially supported for Android development
Starting with version 3.0 of Android Studio, Kotlin support will be built-in. This means that it's now easier than ever to use Kotlin for existing Android projects or even start writing Android apps only with Kotlin from scratch.
This also means that Kotlin and Kotlin plugins for Android Studio will be fully supported in the future and their likelihood of being abandoned is quite small since Google is fully embracing the language for their Android ecosystem (alongside Java and C++).
Pro Low-risk adoption for existing Java codebases
Since it has such a good interoperability with Java, Java libraries, and Java tools. It can be adopted for an existing Java codebase at little to no cost. The codebase can be converted from Java to Kotlin little by little without ever disrupting the functionality of the application itself.
Pro Does not impose a particular philosophy of programming
It's not overly OOP like Java and it does not enforce strict functional paradigms either.
Pro Is built to solve industrial problems
Kotlin has been designed and built by developers who have an industrial background and not an academic one. As such, it tries to solve issues mostly found in industrial settings. For example, the Kotlin type system helps developers avoid null pointer exceptions. Reasearch languages usually do not have
null at all, but APIs and large codebases usually need
Con Data Collection
SE ships your data off to Kite.
Con ST2 version is not maintained anymore
The last ST2 version is available here. All future functionality will be added only to the ST3 version.
Con May be hard for programmers already used to imperative style to learn functional programming from Kotlin
Since Kotlin does not enforce any particular paradigms and is not purely functional, it can be pretty easy to fall back to imperative programming habits if a programmer comes from an imperative background.
Con The need for Java interoperability has forced some limitations
The need to make Kotlin interoperable with Java has caused some unintuitive limitations to the language design.