Kotlin to take off?

mxnerd

Diamond Member
Jul 6, 2007
6,799
1,103
126
Last edited:

Cogman

Lifer
Sep 19, 2000
10,284
138
106
Depends. I worry that kotlin will end the same way the CoffeeScript did. It is nicer, but I worry it isn't nice enough to justify switching.
 

Gryz

Golden Member
Aug 28, 2010
1,551
204
106
When you read about new technology, new programming-languages, new network-protocols, new "paradigms", new anything, it seems all that new stuff is very exciting. And very good, with more benefits, new improvements, it's awesome. Everybody is talking about it. You see it everywhere.

Reality is that most companies use old proven technology. And once something is deployed, it'll stay deployed for years, 10 years, maybe 20 years. I write code in C. So do a few hundred of my collegues. That language is 46 years old. Yes, computer science is changing all the time. But it takes time. And new stuff will not replace old stuff overnight. Sorry.
 
  • Like
Reactions: urvile

urvile

Golden Member
Aug 3, 2017
1,575
474
96
I remember when node was replacing everything. I am yet to see it. As noted above companies particularly large ones rely on proven technology. For a number of reasons one being skill sets, pool of available talent, what's being taught at universities, what advantages the language brings to RAD, design, how easy it is to maintain etc. I have been using C# since 2008. The major switch I have seen in the last few years on the back end is to .NET core.

On the front end it's been the move towards javascript frameworks. Like angular and react. Back to the OP :) maybe kotlin will replace java in the android space? I am not a phone developer so I don't really know.

I like JetBrains resharper so much that I have my own license and take it with me from job to job.
 

DaveSimmons

Elite Member
Aug 12, 2001
40,730
670
126
The other barrier is libraries.

For Windows, if you write code in either native C/C++ or the full (non-Core, non-UWP) .NET then you can find existing pre-written libraries to do almost anything, and in many cases the library is free open source. That can save months of initial development time, and you get near free maintenance on those libraries for as long as the library is actively developed.

With each new flavor of the month you're back to square one and lose those millions (billions?) of lines of available code unless you can find wrappers to connect them to the new hotness.