nice work simple smile

@sreich: Glad you like it simple smile

@sdavids has left the channel

There's currently a drama unfolding around the PHP web framework PHPixie, defrauded download numbers and its PHP-FIG (which wants to become PHP'S de facto standard group) membership. Unrelated of this, I stumbled upon a blog post [1] about manipulated download numbers of the Apache Groovy project. Maybe someone finds this useful, as Kotlin has some Groovy features (although it doesn't follow the initial vision of Groovy; as I puzzle this vision together from the few posts I've read from this blog). [1] http://gavingroovygrover.tumblr.com/post/131337969066/groovys-apache-hoax

Did you verify this article? It’s from October, and I didn’t see it before. That’s suspicious simple smile

the counter on bintray is easily verifyable

I didn't check the IPs and such, though

Yeah, also comments are deactivated for this Tumblr blog. Would've been interesting to hear people approve/disprove this.

I asked @jbaruch about that in our chat, but he doesn't like answer how it possible shipit

And 7 millions from Germany 😬

4 times more than US

That doesn’t look right, but I don’t think it is a big deal. Even if they are tweaking downloads in any way, why is it important?

No, it doesn’t have to be mentioned elsewhere and to promote bad buzz. It’s just good to know.

The future of kotlin is more important to me than the past of languages I don’t use anymore.

Guys, I have a strong concern about using data classes everywhere. If an object is mutable, you get unstable hashCode which can break HashMap. Only immutable classes are ok to become data classes. What are your thoughts?

I've config in yaml like

<https://github.com/Feng-Zihao/protox/blob/master/src/main/resources/protox.yaml>

why not use HOCON then?

Because configuration is not execution

I've just 2 weeks experience with Kotlin... Make protox work is my first priority.

But it's time to think more.

Just like ruby, Data as Code, it's great.

The most ideal language is dynamically in syntax, static type in compilation and execution.

Kotlin sits nicely in this position.

As I pointed out to @jkbbwr, I try to stick very strictly to three principles in the Kobalt DSL in order to make it intuitive: http://beust.com/kobalt/documentation/index.html#general-concepts You should never be unsure what to write: 1) Simple value: equal sign. 2) Multiple values: function call 3) Complex value: closure. That’s it

A principle I stick to in writing DSLs is to make the DSL compose objects, never mutate objects.

Still not sure how I should expose a series of shell commands

that one is bugging me

@jkbbwr:

shell(“ls -l”, “rm foo”)

?

why do you not use ansible, chef or puppet?