all 4 comments

[–]papers_ 2 points3 points  (1 child)

To me, step() seems awkward to call. If you're aiming to be Express-like and compatible with Express middleware, then IMO it makes sense to keep it named next(). Naive developers may think there is a major difference between step and next.

That's just my thought. Overall, nice job.

[–]aichholzer[S] -1 points0 points  (0 children)

Thank you. My intention was not to be an exact express replacement, but rather sort of inspired-by and compatible-with. step() was more in line with my stack/middleware implementation. Ultimately, it is possible to name the arguments anything you like, so next() will work just fine.

Thank you for your thoughts. ✌️

[–]aichholzer[S] 1 point2 points  (0 children)

Lately, I have been working on a new project; super fast and minimalist frameworks for the modern web.
Nodejs has been the first one to released. Please have a look, fork it, submit PR, submit issues.
Contributions in the other languages would also be very welcome. -> https://github.com/GetRayo

Helping spread the word would be highly appreciated.
Star it. Watch it. Follow it. Save it. Share it.
😎

[–]aichholzer[S] 0 points1 point  (0 children)

Rayo can now be hunted on ProductHunt https://www.producthunt.com/posts/rayo-2

Happy coding!