Isn’t that the case just now? For the core team at least, that’s all we work on. The only thing that could be at all seen as working against that point is we avoid things like:
Annotations that control the JS output
But that’s only partially because that would make it impossible to fully support other backends. Even aside from that I wouldn’t really be in favour of this kind of thing anyway - it’d be going backwards; the FFI was inline at one point, but it was a pain. Being able to use JS linting tools and stuff is a major benefit of having the code separate.
Tool for typescript defs -> Purescript generation
This has been talked about since 2015. There are so many problems to solve here (type system mismatch, effects) that I’m very dubious it’s ever going to happen!
Focus on performance and improved code output
I really don’t think this has much to do with why PS doesn’t have more adoption. There’s definitely a ton of room for improvement, but it’s not slow enough that it typically stops people from being able to build what they want to build.
But don’t get me wrong - I’m not saying that fixing all the points you raise here would have no impact. It’s just unfortunately I think @razcore-art’s points are closer to the truth of what stops people from picking up PS.
I think the “killer app” thing is probably the closest point listed that might have an effect on driving adoption, since that’s probably why Elm is more popular than PS… it’s as much an app/framework as it is a language. That and Elm has a significantly lower abstraction ceiling, making things appear simpler.
Sorry this is all rather negative, it seems I only have problems for this stuff, no answers.