yann510

Working on new projects has been fun for me ever since I started using https://github.com/chocolat-chaud-io/stator

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 :)

You are right that having a fresh eye on the project might be hard to grasp what it actually is. You easily become biased from working on a project, you make readers assumptions without even realizing it.

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

Awesome, will definitely check that out!

Very interesting, we should get in touch to see if there is a possibility of collaboration here. If interested, email me y.thibodeau1@gmail.com

Totally biased opinion as I'm familiar with React, but if you want to learn more about the thought process behind the decision, I recommend reading this: https://yann510.hashnode.dev/creating-a-todo-application-usi...

We've currently selected very hot and trendy libraries which are currently maintained. Although the goal of this project is to be used for projects in production. Right now we haven't tested anything large scale, but the goal would be to replace any technology that isn't suitable for production.

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.

I will definitely check this out, thanks for sharing!

Thanks, I will check this out!

Oh wow that is not reassuring at all, I'll look around for an alternative.

I haven't used typeorm for any real world projet yet. Although when I tried using the mongo driver, literally nothing worked. I also ran into problems from the generated migrations where I would get errors when trying to run them.

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.

We thought about it, but decided not to implement that for V1. Might be something we do in the future. If you'd like to see that, you could create an issue for it! :)

You can read this article to get all the details on the decision: https://yann510.hashnode.dev/the-best-node-web-framework-par...

Yeah this handles a lot of the complexity of setting up a complete project with TypeScript and has some nice examples. Try it out and let me know how it went ;)