Rewrite index to use scala + angular #38
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I concluded dynamic typing isn't worth the effort when it comes to prolonged maintenance of a web application. Initially I chose scheme just in case someone else would want to contribute to the project, but that hadn't happened. My chosen previous stack of kawa + my own library wrappers feels unreliable. Kawa maintainer isn't interested in communicating with potential volunteers regarding improving the language. My own wrappers are one person effort. Although scala and angular might be foreign to typical scheme programmer, they are very reliable and future-proof choices.
And ultimately, I feel the programming part of this project isn't that important, ultimately I decided it didn't matter much what the index site is written in. Most of the value lies in definition data files in types/*.scm. Writing a service / ui layer against it is relatively easy.
Additionally: