That probably means Haskell is becoming more popular. Most software projects and businesses, after all, fail. I wouldn't advice against Haskell. But I would ad

That probably means Haskell is becoming more popular. Most software projects and businesses, after all, fail. I wouldn't advice against Haskell. But I would advice against having a business with more than one non-boring component. And usually that non-boring component should be the solution to the client problem, not the tech stack used to implement it. If you start a business in a language stack none of the devs have done large scale production projects, you are basically begging for a world of trouble. If the devs are familiar with Haskell, I don't see any problem with choosing it, if it matches the problem domain. I wouldn't choose it for example for frontend development (although I suppose you can get it compiling there) or things where C, C++ or Fortran still have a strong legitimate foothold.