As a Roblox developer, it is too hard to migrate to the new TextChatService system because there are a number of critical features that my game requires that are not provided within the framework of the new system. My game generates system messages on the server, but there is currently no way within the new framework to send those messages to all clients. Currently, there is no out-of-the-box method to do this as there is with the legacy system.
My use case involves generating system messages on the server to notify players about what is happening in game, such as when a player joins the server. Currently, with the legacy LUA chat system, I can create a speaker that will broadcast to several channels and send a message to those without too much glue code. With the new chat system, a significant amount of development work will be required to work around the limitations of the new framework. The best method that I can come up with is to create a new RemoteEvent and perform a RemoteEvent:FireAllClients() to get the message to the players so I can use TextChannel:DisplaySystemMessage() on the client, which will require creating a new remote command structure on both the server and the client to handle this, along with the required development time and resources, and the debugging that will also be required.
If this issue is addressed, it will improve my development experience because I will not need to develop my own workarounds for the deficiencies and limitations of the new TextChatService system and the associated time investment to develop those workarounds.