Straight up - you should not use it without much more compelling reasons than those you have outlined.
It's not OK as CTO to push your company to use for favorite pet slightly obscure technology.
The company needs ordinary technologies to get its job done - Java, C#, TypeScript, Golang, Python, something like that. Maybe even Ruby but frankly that causes hiring headaches too.
Unless the company is doing something so extraordinary that it NEEDS Elixir over the technologies above, and it probably doesn't need it.
I know companies that went all in on Elixir - they spend all their time trying to recruit Elixir developers from a tiny recruiting pool, or trying to find people willing to learn it and bring them up to speed. This is poor business practice - there was nothing they were doing that could not be done just as effectively with any of the other major languages.
Just use normal technologies, have all the people and documentation and training and other resources available and get on with the job of building the software that the business needs.
I guarantee you that the company that went with Elixir due to the enthusiasm of some current or past CTO will have to go through the painful process of getting rid of it.
Elixir is for personal projects. Corporate software development is mature enough now that ordinary technologies are extraordinarily powerful and there's almost no reason sufficiently compelling to not use them. Toys are for home, tools are for work.
Comments
Straight up - you should not use it without much more compelling reasons than those you have outlined.
It's not OK as CTO to push your company to use for favorite pet slightly obscure technology.
The company needs ordinary technologies to get its job done - Java, C#, TypeScript, Golang, Python, something like that. Maybe even Ruby but frankly that causes hiring headaches too.
Unless the company is doing something so extraordinary that it NEEDS Elixir over the technologies above, and it probably doesn't need it.
I know companies that went all in on Elixir - they spend all their time trying to recruit Elixir developers from a tiny recruiting pool, or trying to find people willing to learn it and bring them up to speed. This is poor business practice - there was nothing they were doing that could not be done just as effectively with any of the other major languages.
Just use normal technologies, have all the people and documentation and training and other resources available and get on with the job of building the software that the business needs.
I guarantee you that the company that went with Elixir due to the enthusiasm of some current or past CTO will have to go through the painful process of getting rid of it.
Elixir is for personal projects. Corporate software development is mature enough now that ordinary technologies are extraordinarily powerful and there's almost no reason sufficiently compelling to not use them. Toys are for home, tools are for work.