Kotlin 1.2.60 comes with native compiler binaries
51–60 of 69 posts
Re: Kotlin 1.2.60 comes with native compiler binaries
#52Jetbrains is like a new Borland. I hope they don’t end the same...
Re: Kotlin 1.2.60 comes with native compiler binaries
#53Earlier quoted context omitted.
I think it's a symptom of times changing. People don't want to code in vi/nano anymore. A general purpose language launching today is expected to have a good support in an IDE. At least autocompletion, support for building and debugging, refactoring if possible. Also people prefer to have a one well working IDE plugin than several half-baked ones that don't offer much more than syntax highlighting. That's why IDE plu…
> I think it's a symptom of times changing. People don't want to code in vi/nano anymore. Not sure if that is true. Many people are still using vim for many newer languages. I think it depends on the language. Some languages are simply more IDE-reliant than others. Statically typed languages with a large vocabulary (Java, C#, Scala) tend to benefit more from IDEs than simple, dynamic languages like Python and Ruby. A…
Re: Kotlin 1.2.60 comes with native compiler binaries
#54Earlier quoted context omitted.
Yes, but none of those IDEs were developed concurrently with the language by tightly integrated teams (well, except smalltalk).
Yes they were. Delphi and Visual Basic are the most obvious examples of IDE-centric languages. You couldn't even buy the compiler separately from the IDE.
Re: Kotlin 1.2.60 comes with native compiler binaries
#55Earlier quoted context omitted.
Well, it's a language created by an IDE company…
The dividing line between what's a language and what's the IDE is fairly arbitrary. E.g. a language could conceivably come with a tool chain that includes CLI-driven refactoring, and an "IDE" would only need to be a graphical interface calling it.
Re: Kotlin 1.2.60 comes with native compiler binaries
#56Earlier quoted context omitted.
There were zillions of language-specific IDEs in 2000 when C# was announced.
Yes, but none of those IDEs were developed concurrently with the language by tightly integrated teams (well, except smalltalk).
But beside smalltalk, there were lots of others. All the commercial Lisps, Dylan etc. Somewhat more mainstream-ish - the NeXT Objective C environment is a good and much earlier example.
There were lots of interesting things about .NET when it came out, the IDE-ness of it doesn't strike me as one of them at all.
Re: Kotlin 1.2.60 comes with native compiler binaries
#57Jetbrains is like a new Borland. I hope they don’t end the same...
What does that mean?
I'm sure someone will be happy to correct anything I got wrong :)
edit: I don't think this will happen to JetBrains. edit2: Forgot the "Delphi" name, but it was basically TP w/ libraries.
Re: Kotlin 1.2.60 comes with native compiler binaries
#58Jetbrains is like a new Borland. I hope they don’t end the same...
What does that mean?
I've yet to write any Kotlin in anything other than Vim and Atom though... and Gradle built those apps just fine. So I'm not sure I see a real comparison here.
Re: Kotlin 1.2.60 comes with native compiler binaries
#59Earlier quoted context omitted.
I think it's a symptom of times changing. People don't want to code in vi/nano anymore. A general purpose language launching today is expected to have a good support in an IDE. At least autocompletion, support for building and debugging, refactoring if possible. Also people prefer to have a one well working IDE plugin than several half-baked ones that don't offer much more than syntax highlighting. That's why IDE plu…
This. I really only bother touching languages with good to great IDE experiences which is why I basically concentrated on JVM tech for most of my career. The good news is that the tools story is improving across all languages these days.
Re: Kotlin 1.2.60 comes with native compiler binaries
#60Earlier quoted context omitted.
How do you use Jupyter for Deep Learning? I can only think about prototyping stuff, but not for training a large dataset (that doesn't fit in memory) for days.
Of course, prototyping only + test runs; then moving the code to proper source files (or writing them separately and including them in the notebook). Usually I write everything in the notebook, make sure I catch all the bugs, do some initial test runs to see if I am getting anywhere, then separating code out to individual Python files. The good thing is I can immediately showcase principles and progress to clients by…