Convert to kootlin

[SollyW]

convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin convert to kootlin

[MsRandom]

based

[SollyW]

Hmm, even when they're only used once?

[MsRandom]

Yeah, I think declaring what's going to be used just looks better

[SollyW]

I can't use delegates (to my knowledge - there might be a feature I'm unaware of) since the property names contain underscores, which don't follow naming conventions for kotlin values. I could do val propertyName = properties["property_name"].toString(), though

[MsRandom]

You could rename the properties to be camel case, that's what I usually do.

Also, declaring it as a variable but accessing it from properties is worse imo since you need to type the name twice

[SollyW]

Perhaps. I'll wait for someone else's opinion on it before I go with it

[gudenau]

Kotlin is evil.

[MsRandom]

Kotlin is evil.

@gudenau is evil.

[Jack-Papel]

@gudenau Eviller than groovy? 🥴

[MsRandom]

Also the alternative in this case is Groovy which I'm sure we can all agree is worse

[gudenau]

We are currently using groovy, why change it when it works and they are both bad?

[MsRandom]

Kotlin build scripts are far better imo and they are way less prone to breaking with changes, due to their statically typed and compiled nature

[SollyW]

It might be nice to extract plugin versions to the properties file. In particular, crowdin includes the minecraft version in its version

[MsRandom]

I think the delegates look a lot better, although shouldn't they be localized to their scope, rather than being global?

[SollyW]

Perhaps. On the other hand, having them all in one place is nice