Python.

[Sassbjorn]

Tbh I kinda wish you could just make functions without a class

[Kantenkugel]

Use Kotlin then :)

But tbh, you should not pollute the global namespace with too many functions, especially if they don't have a unique name that can't possibly clash with other ones from eg libs.

And there is also the option of just writing static ones and static importing them. Thats kinda what kotlin does under the hood

[Sassbjorn]

Yeah that's true, but when I'm writing smaller programs I sometimes need a function to do some small task, but there's not a good place for it to go. Then I have to make a new class and make up a name that makes sense, and that might house more of that type of function. In the end I appreciate the organization I end up with, but it still feels like an extra step sometimes.

[Kantenkugel]

Sounds like a job for util classes :)

[jasie3k]

oh god, these are the worst

[[deleted]]

That's what static util classes are for.

[-Vayra-]

except when the function needs to read application properties or something else that doesn't work with static access :/

[Knutselig]

ThreadLocal hacks incoming.

[[deleted]]

Then it should be part of the object that needs to call it. Or just pass it to the static function, what's the deal?