I mean that the marketing around "happiness" doesn't directly address any concerns that developers should have when evaluating a library. At best it's indirect if you assume that happiness means performance, but that's a big assumption.
So I'd rather marketing just say exactly what it's direct goals are rather than indirect ones like happiness.
> Since the F# transpiles into JS at runtime it's really no different than, say, TS in terms of performance concerns.
But as a particular point, this is hard to believe. TS tries to have no (or a minimal) runtime component whereas F# definitely must have a major runtime component.
So I'd rather marketing just say exactly what it's direct goals are rather than indirect ones like happiness.
> Since the F# transpiles into JS at runtime it's really no different than, say, TS in terms of performance concerns.
But as a particular point, this is hard to believe. TS tries to have no (or a minimal) runtime component whereas F# definitely must have a major runtime component.