The problem with making a new language is that it seems like people do it because they want to make a new language. Don't make a new language just to make a new

The problem with making a new language is that it seems like people do it because they want to make a new language. Don't make a new language just to make a new language. Do it because you are solving a problem by doing it, and if you are solving a problem, you already win regardless of how many people will use the language. Have the problem before you make the solution. > It turns out that people don't always agree on what the pain points with C is. People have different problems so they should probably use different languages. Don't even try to make a language that will solve everyone's problems. > Also, while the company has experience recruiting for C developers, it doesn't know how to recruit for this new language. If the language is so hard that people have to have special knowledge to use it and can't learn it quickly then it's probably not a good language. > For a business it's whether despite the downsides the language can help the bottom line: "Is this valuable enough to outweigh the downsides?" Exactly, it's solving real problems that matters. > The "build it and they will come" idea is tempting to believe in A better idea is "build it and we will come because we need it. Then maybe other people will come if they need it too."