and their response, on their forum, was that they are intentionally make hard to avoid the jetbrains ide while using kotlin
now technically you still can, kotlin is open source, and you can download it standalone, if you search hard enough
i am not really sure, how jetbrains think kotlin will help it long term to increase its sales .. but this seems to be one of their objectives .. they did not create kotlin just for the sake of it (and nothing wrong with that)
Remember that the community edition is open source
They are an open company and do offer a lot completly for free
Borland was .. a very traditional closed company
One of the great things about Borland was they published the source code to their VCL (their main platform library Delphi and C++ builder applications used). So you could read, learn from, troubleshoot and debug with the source code. At a time when Microsoft and most companies didn't.
And the VCL design patterns were/are incredibly elegant, and studying them an excellent and accessible way for an interested programmer to learn some real software architecture skills.
Very weird; what happened ? In java/kotlin it is as great as ever in Android Studio
FWIW I've never found IntelliJ code completion in Javascript, Ruby, or Python to be very accurate. It's fantastic in Java and Typescript.
do you have a link for this?
As alternatives they suggest their online REPL (to play and learn without installing anything), IntelliJ (unsurprisingly their favourite), gradle, or maven. The latter are about as fully-fledged build systems as you can imagine and are easily used with any editor.
I'm sure there will be gradle plug-ins available for VS.Code or Atom, or a gradle mode for emacs.
The Vue.JS community would beg to differ.
But yeah, if JetBrains could implement something like the Rust Language Server for Kotlin I would be so happy.
Vue's reactive nature actually is superior, because something like Redux requires destroying, regenerating, and messaging around entire objects. This can create serious problems when, for example, trying to use Chrome APIs or manage component renders.
Also, although JSX is nice for developers, it's not friendly to designers. Vue, however, supports single file components that are very designer-friendly.
FWIW, Alibaba began creating their own native framework with Vue called Weex, which is now part of the Apache project. https://weex.apache.org/
http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular...
Even more so when you consider that Vue itself is a React clone underneath. Templates compile directly into createElement calls internally and if you'd strip off Vue's outward complexity, the api surface, the syntax parsers, the observable system, etc., what would remain is React.