| Pour répondre aux questions sur Kotlin, on avait formalisé ça sur notre documentation interne (en anglais). Je copie-colle ça ici :
Elixir relevant for the core thanks to high availability foundations, but has limited productivity for development at large: Lack of maturity of IDEs, frameworks, libraries; Dynamic typing reduces code safety.
Kotlin vs Elixir Access to the whole Java ecosystem: libraries, frameworks; Static typing and null value handling reduces runtime errors; Superior IDE support (IntelliJ): refactoring, static checking, debugging; Quick ramp up for Java developers Perennity: backed by Google and by JetBrains; can be reverted to Java in case of a catastrophe. Based on standard Java deployment vs. own VM Performances should not be an issue in the short/medium term for our B2B business.
Kotlin vs Java Fixes many Java flaws: less verbose and more secure through type inference, data classes, null pointer security, additional syntactic constructs, etc Better functional programming support
Kotlin vs other modern statically typed languages with a rich ecosystem Few contenders: Scala, maybe C#, which is for the MS world Scala integration with the Java ecosystem is less seamless than Kotlin; also, it is perceived as complex and less pragmatic by team members who have some exposure to both languages.
Pour AWS, vu que le sujet est (très) clivant, je préfère ne pas lancer de troll. En revanche, vu qu'on a également documenté notre choix en interne, pas de souci pour partager ça avec des personnes potentiellement intéressées par le poste.
Bonne journée,
Michel
|