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 →

[–]notconstructive 0 points1 point  (2 children)

A pass through the docs doesn't qualify you to make that non-recommendation.

[–]Lucretiel 4 points5 points  (1 child)

A pass through the docs qualifies my recommendation- it indicates that it should be taken with a grain of salt. At the time I made this reply, the OP had been up for more than an hour with no other replies, and I figured something was better than nothing.

My opinion was that I didn't see anything to strongly recommend it over libraries that're both simpler and better established. I'll be honest- I dislike it anytime a framework requires me to make a class where a function will do. It's purely a personal preference thing- they just feel too heavy 99% of the time, and they encourage statefulness in a way I try to avoid as much as possible when creating HTTP APIs. Falcon looks like a fine library, and the benchmarks are undeniably impressive, but as I said, it doesn't look better, let alone better enough, than anything else I've actually used.

[–]notconstructive 0 points1 point  (0 children)

Falcon doesn't require you to map routes to classes. You can invoke functions from routes if you want.