yann510
Joined 6 years ago
Joined 6 years ago
Although to your point that the jargon is too specific is a bit concerning to me. When I go on and discover a new project, if I don't understand specific terminology, I will go on and read about it to increase my knowledge of this topic. If you're not from the "web world" and you are not familiar with what full-stack means, you should go on and read on the subject simply out of curiosity!
Once again, I totally get your point that the project first few lines should be more informative as to what it is exactly and how it can be used.
I have in fact created an issue for it: https://github.com/chocolat-chaud-io/stator/issues/105
We will be testing stator out with a large scale production project (that's why we plan on implementing kubernetes support) and we will update the libraries accordingly.
Even with these encountered problems, I'm still willing to give it a try for my upcoming project. I'll probably write an article on this if things go bad.
For sure, this is less mature then the others out there, but I think it has a bright future as it has a nice syntax and cool features.
This allows me to quickly start coding while not focusing on the tedious configuration tasks that usually accompany a new project. I've been using it for over a year for personal and professional projects. It's not perfect, but it helps. I wrote this open-source template, so I am, of course biased :)