Why Programming Language Designers Don't Always Use Their Own Languages: The Case of Kotlin and PHP

While Andrey Breslav, the creator of Kotlin, might design and champion this robust language for Android apps and other projects, he often uses PHP for his own website, Alter. This raises a question: why don't programmers and language designers use their own creations for their personal projects or websites? This article delves into the reasons behind this phenomenon, offering insights that can help developers make informed language choices for their projects.

Why Not Use Your Own Language?

The key idea here is that the ldquo;best tool for the jobrdquo; principle applies not just to individual languages, but also to specific use cases. In other words, just because Andrey Breslav created Kotlin doesn't mean he would use it for a simple web application. PHP, on the other hand, is a perfect fit for the kind of website is.

Cost Efficiency: Hosting a PHP website is less expensive than hosting a JVM (Java Virtual Machine) application. For a personal website like Andrey Breslav's, the added cost of using a more complex language might outweigh the benefits. It's like using a flamethrower to kill a fly—solving a small problem with excessive resources is often not the most efficient approach.

Documented Best Practices: Languages like PHP are well-documented and have a proven track record in web development. This means the frameworks, libraries, and tools available for PHP are highly optimized and reliable. Kotlin, although powerful, lacks some of these equivalents due to its design and use cases.

Availability of Resources: When it comes to hiring web backend engineers, PHP developers are more readily available and broadly experienced. Many experienced Kotlin developers have backgrounds in areas unrelated to web development. This makes PHP a better choice for projects where quick and efficient hiring is crucial.

Language Designers' Biases and Expertise

It's not unusual for language designers to be biased towards the languages they know and like. However, highly experienced software engineers and language designers often have deep exposure to various languages and platforms. They understand that different languages are better suited for different tasks. Andrey Breslav, as a seasoned developer and language designer, would almost certainly recognize the limitations of Kotlin in certain scenarios, even if he designed it.

Soft Overrides Hard: Sometimes, professional judgment and industry standards take precedence over personal biases. Just because a language designer has a favorite language doesn't mean they should dictate its use in every context. This is especially true in the professional realm, where the interests of the project often override personal preferences.

Conclusion

Language designers, like Andrey Breslav, often use languages other than their own for various reasons. These reasons include ease of use, cost efficiency, availability of resources, and adherence to best industry practices. Understanding why they might choose one language over another can help developers make better-informed decisions about which language to use for their projects.

Ultimately, the choice of language depends on the specific requirements and constraints of the project. Just as the simplest tools are often the most effective for small jobs, the right tool—whether it's Kotlin or PHP—will be the most effective for the job at hand.