mountaineer VS anansi-tags

I imagine a lot of this comes down to personal preference. In the early days of Mountaineer (gee, almost two months ago at this point), I played around with the idea of embedding html into python instead of needing a JS layer. Eventually my consensus was:

- The most extensive typehinted approaches typically end up wrapping JS/React components anyway (like Reflex/Pinecone)

- We really need better IDE support for html strings that are within python strings. The editing problem is a big setback.

The ergonomics of Python + JS in separate code files won out and the user experience has been better than forcing them both into a common language would be.

This has the benefit of leveraging whatever the two languages are best at, in native code, so you have access to all the native APIs without having to learn a shim on top of it. Way more longevity to that approach too. Context switching between two languages isn't that bad if you minimize the glue layer that you have to write between them.

[^1]: https://github.com/piercefreeman/mountaineer

mountaineer – batteries-included web framework for Python and React

https://github.com/piercefreeman/mountaineer/tree/1d44cdf1c6...

(In an old commit and stripped out from the current codebase until it has better test coverage and the main codebase is stable)

anansi-tags – Apply markdown to Python strings to get ANSI