Why's Kotlin so based?

Why's Kotlin so based?

Attached: 48518894-e0ec1a80-e81f-11e8-8b75-e3ed0777fe60.png (1306x997, 61K)

Other urls found in this thread:

youtube.com/watch?v=b2F-DItXtZs
youtube.com/watch?v=bzkRVzciAZg
twitter.com/abreslav
en.wikipedia.org/wiki/Breslov_(Hasidic_group)
chabad.org/library/article_cdo/aid/316874/jewish/Breslav.htm
twitter.com/NSFWRedditVideo

Because you're fat.

Attached: Dzem-truskawkowy-29251-big.png (216x400, 140K)

>slower than python
>slower than ruby

kotline btfo'd for ever

Attached: kotlinbtfo.png (1488x682, 148K)

>hurr durr slow
when you're one of the best programming languages it doesn't matter.

>Update: I was doing it wrong and got a run time of 2 seconds when I fixed it.

Because it's the comfiest language. No wonder people like it.

Something is fishy in this pic. Where is JS

>Comfiest language

That would be C#

>writing 5 lines of code to read a text file
>MUH CLASSES
>comfiest

still a headache of a language.

xamarin is ok though I'll give you that one.

just thinking about not having to use Java for Android makes me hard
this is a graph for 'fastest growing', by contributions I think

Can you one-line a class with a variable and getters/setters and all the other boilerplate shit for it in c#?

Attached: 234.png (310x35, 2K)

>popularity contest

it isn't, java is just really bad

google is the actual reason it's so popular.

it's another same-y language that anyone who's typed a { can figure out in 10 mins, and it runs on the jvm

>Can you one-line
muh getters and setters

coroutines are shit, it's a hack for async IO for languages without proper/easy concurrency

The problem here is that operating systems do not support any other asynchronous primitives other than threads. Threads are expensive as fuck, they take up to 1MB of stack and thread switching is a really slow operation. Threads are generally okay for heavy CPU-bound operations but really bad for IO operations (try to run 10000 threads and that's already 10GB of RAM allocated). That's why languages implement their own lightweight (green) threads or co(go)riutines. Coroutines also provide new methods for synchronizations - channels/actors instead of locks. "Do not communicate by sharing memory; instead share memory by communicating".

and async is hack for people who don't know how to use threads, more you know.

>groovy
isnt it dead for almost a decade?

would you rather do this
view.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
// Do whatever you want to
}});

or this
view.setOnClickListener { // Do whatever you want to }

>Android build system
Mavel >>>> grader

desu I prefer
view.onClick += (object sender, OnClickEvent e) => { /* do whatever */ };

make your property public. no getters/setters needed

>gradle
ah yes thats why
also wtf with all these typos

disgusting

>Groovy
That doesn't seem right.

What the fuck is "proper, easy" concurrency? Seems like an Oxymoron.

make everything microkernels

whats HCL?

hydrochloric acid

Try using a thread per socket, moron, tell me how that goes.

class BullshitActivity : AppCompatActivity(), View.OnClickListener {

val someButton : Button
val someOtherButton : Button

override fun onCreate(savedInstanceState: Bundle) {
super.onCreate(savedInstanceState)
setContentView(R.id.activity_bullshit)
someButton.setOnClickListener(this)
someOtherButton.setOnClickListener(this)
}

override fun onClick(v: View?) = when (v) {
someButton -> {
// whatever happens when I click the button
}
someOtherButton -> {
// whatever happens when I click the other button
}
else ->
}
}

Shut up, poojet

What happened to Coffeescript? it used to be popular among startups

That's HCl

Based Polska.

and again, you apparently don't know HOW to use threads if you think per socket is only thing to do.

that's not webscale, go and node are webscale

>PowerShell
>HCL
>CMake
>SQLPL
Yes this is obviously a good proxy for quality.

Attached: 1516059818143.png (1309x507, 79K)

Used to read the first option. It's too verbose to what it intent to achieve logically, but once you understand OO on Java it's just natural to read.

Second option is beautiful indeed and very easy to use indeed.

webscale... reminded me of this
youtube.com/watch?v=b2F-DItXtZs

and for node
youtube.com/watch?v=bzkRVzciAZg

It was made by a Russian Jew:

twitter.com/abreslav

en.wikipedia.org/wiki/Breslov_(Hasidic_group)

chabad.org/library/article_cdo/aid/316874/jewish/Breslav.htm

>2 people join 1 person
>growth DOUBLED

Kottlinfags on suicide watch

kek

What's the point of makin Kotlin the primary Android's programming language when they're going to drop it in Android's successor anyway?

why are javafags seething so much?

Because this Google moves from java to another language just to drop that language soon anyway
Make up your fuckin' mind

So what? With Kotlin now you can not only write Android apps, but use it for frontend and backend as well as ios (with kotlin/native) and even for fucking raspberry pi.

>Android's successor
wat dis?

> webscale
hello zoomer

there is none

>relative growth in contributors
Absolutely fucking pointless metric, if I start a project and my mom comments on it it's already a 2x growth.

>writing 5 lines of code to read a text file
In C# it's literally one line to not just read, but to break it into lines, perform some operations on it and then write it all back.

Getters and setters are one-line in C#, in fact that's where Kotkin borrowed them from.

Kotlin doesn't strictly depend on JVM.

>when you're one of the best programming languages it doesn't matter.

It's not and Java 11 already has most of the good features that Kotlin was riding off of. Like many other Java "killers" they will all go down in history as a irrelevant hipster language that failed to gain hold since they fail to innovate and compared to Java.

If I wanted to learn Android app development, should I focus on Java or Kotlin?

kotlin if you want to be able to read and understand what you're writing

Typescript replaced it. Coffeescript was just because javascript was kind of ugly, but with modern javascript you can avoid a lot of the ugly. Promises, async, new operators..

Dragonfly BSD does not have this problem.

>python 10 seconds
>kotlin 30 minutes
I don't even have to look at the code to know he probably used kotlins query functions incorrectly. Easy to write bad code if you don't understand how it translates to Java.