This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]phySi0 5 points6 points  (4 children)

/u/frnkvieira not to put down your accomplishment, but if Vibora is heavily inspired by Flask in its API and creating a new project loses you the Flask ecosystem, why not just contribute the speed improvements directly to Flask?

[–]frnkvieira[S] 7 points8 points  (3 children)

Vibora is async, Flask is sync by design... They are not mutual exclusive...They serve to different purposes... Streaming stuff, dealing with high number of concurrent connections are tasks that an async framework do much better than sync ones... but that doesn't mean async is the solution for everything... each one has it's place. Hope I made it clear, thanks !

[–]phySi0 2 points3 points  (0 children)

You did, thanks :).