4 ms·
> Kotlin comes from industry, not academia. It solves problems faced by working programmers today. As an example, the type system helps you avoid null pointer e
by Ericson2314 10y ago
> Kotlin comes from industry, not academia. It solves problems faced by working programmers today. As an example, the type system helps you avoid null pointer exceptions.
I'm sorry but you just undercut your own anti-intellectualism better than I could right there.
(There exist languages which have guarded against this without loss of expressive power since before Java and, oh, are from academia.)
- ansgri 10y agoA better example of 'engineering not academy' would be explicit vectorization, memory layout support and a good FFI. (all the stuff that in theory is better managed by compilers, in practice it either doesn't matter at all or else should be left to humans). Please correct me if I'm wrong, but Kotlin doesn't improve on Java in these areas.
- misja111 10y agoIt would be awesome if there would be some JVM language that supported explicit vectorization, memory layout support and a good FFI. But it also seems impossible. How would any JVM language have memory layout support while at the same time running in the memory managed sandbox of the JVM?
- aardvark179 10y agoWell, project Panama is aiming to add those things to the JVM, so you may get your wish in a few years.
- premium-concern 10y agoHave a look at Scala Native. Despite its young age it creates really fast, tight code (they have issues benchmarking things because Dotty Linker + LLVM gets rid of too much stuff).
- ansgri 10y agoThanks. It is too early to say if it would be of any use, however, since they don't talk about freeing these native data structures.
- premium-concern 10y agoYou can have both managed (T) and unmanaged pointers (Ptr[T]).
- jmfayard 10y agoIndeed this is more an aspect inspired by academia the point would have been better made by pointing out the excellent and extensive tooling built by jetbrains for kotlin. that's something the maker of the intellij platform has more experience with than academics Also there is a tradeoff between advanced language features and good tooling, which is why you will sometimes miss the former inside kotlin
- billyjobob 10y agoThe reason they disavow academia is not because there is anything wrong with academia but to make a contrast with their closest competitor, Scala. It's a subtle way of saying "we may look like Scala, because like Scala we are a better Java, but the difference is we are actually useful in the real world. "
- ungzd 10y agoThat means "Comes from company that made popular IDE so it has lots of marketing advantages".
- coldtea 10y ago>(There exist languages which have guarded against this without loss of expressive power since before Java and, oh, are from academia.) So? Their academic status might solve this, but create other problems still. E.g. lack of an actual commercial ecosystem, too much emphasis on research-y features, immature tooling, etc.
- mike_hearn 10y agoSometimes I think I should change that paragraph because it too often gets interpreted as generically anti-academia, which then triggers people who think I'm anti-intellectual. Note the very important part of that statement: It solves problems faced by working programmers today. Academic PL research can have that property. Pizza went on to be the foundation of Java generics, there's a ton of excellent compiler and GC theory that comes from academic research and so on. And of course a few of the ideas in Haskell and others are leaking into the mainstream. But when it comes to handling null pointer errors, sorry, it's insufficient to say "some languages popular in academia don't have null". So what? Working programmers today hardly use such languages. They very much rely on languages which do have nulls, and APIs which use them, and yet the only language that came out of academia in recent times which has serious production usage is Scala, which has ... nothing to say on the topic. Except, oh, an option type. Which can also be null, and which even C programmers can easily have. It's simply not comparable to language integrated support with backwards compatibility. It would have been nice if academic research had identified up front the best set of usability tradeoffs for adding optionality into a backwards compatible language, but nobody did, so JetBrains had to do it themselves.
- codygman 10y ago> And of course a few of the ideas in Haskell A few? Don't you feel like you're underselling the impact Haskell had had on other languages? > he only language that came out of academia in recent times which has serious production usage is Scala, What are your qualifications for serious production usage? Would ocaml count by your standards? Haskell also has increasing production usage, though I'm sure you don't count it. Swift (if you don't count it now, you will)? Rust? > It would have been nice if academic research had identified up front the best set of usability tradeoffs for adding optionality into a backwards compatible language, That's not enough. It would have to be more convenient to use optionals than null or programmers in that language would have to be convinced optionals are better. In an existing language that uses null pervasively, it would be hard to get a critical mass of legacy code which uses optional.
- mike_hearn 10y ago