I don’t care if arrays start at 1.

Going a little overboard with tickets and process improvements can be really beneficial. As I’ve utilized the features in Jira more and more, I’ve found I’m more organized, less likely to loose tasks in our backlog, and more driven to get things done. I think that’s partially because it helps sort out my ADHD brain a bit.

Kotlin is a more complex programming language than Scala.

Scala still seems to have this bad rep from the times when functional programming features weren’t commonplace yet in most programming languages, because it stood for this oh-so-complex functional programming stuff.
Now, Kotlin is climbing up the TIOBE index, lauded by Java programmers as finally giving them the features they wanted, and as someone who’s now coded extensively in both, I don’t get it.

Kotlin is obviously heavily inspired by Scala and they seem to have roughly the same features. But Kotlin imposes tons of rules that limit these features in how you can use them.

However, I’m not talking about the good kind of rules, those which might help to streamline the code style. I’m saying it feels like they implemented half of each feature respectively, and then, so they didn’t have to finish implementing, they disallowed using it in other ways.
Arbitrary rules, which as a programmer you just have to memorize to please the language gods.

From a technical perspective, the only aspects I can see Kotlin being better are somewhat better Java interop and if you want to build a DSL, it has some nice features for that. But those DSL features make it worse / less streamlimed when you don’t want to build a DSL, and it just seems to be worse in every other aspect.

Obviously, popularity rarely correlates with technical merit, I can accept that. But when people tell me I shouldn’t use Scala, because it’s so complex, I should use Kotlin instead, that shit fucking triggers me.

1. Any programmer who can’t recite the fallacies of distributed programming from memory should not be permitted near any kind of networking code.

2. Any programmer who is permitted to program networking applications (c.f. #1) should be required to only use a network environment (for work and personal use) that is high load and low reliability while doing so.

3. If you don’t have used-in-anger knowledge of everything from an HDL to a formal theorem-proving language, plus the entire spectrum in between, you should not call yourself a “full stack” developer. The stack is much deeper than you can imagine.

4. If you don’t know everything from network PHY to high-level networking abstractions you should not call yourself a “full network stack” developer. Network stacks are also much deeper than you think.

deleted by creator