3 ms·

I needed something real because you cannot build a useful web server in a vacuum. I’d even go as far as saying that you can’t build anything in a vacuum. T

by iampims 16y ago

I needed something real because you cannot build a useful web server in a vacuum. I’d even go as far as saying that you can’t build anything in a vacuum. This is my main gripe about many sample projects for web frameworks. You get the traditional and useless hello world and the blog engine in 20s. Yet none of them highlights how to decouple your app, how to deal with non mundane stuff (security, error handling and reporting). Most of us, when learning about a new framework, have many years of experience with other frameworks, so why not try to sell us on how your framework is different and better suited to the real world situations we’re facing.

nakkiel 16y ago
I found flask's documentation quite well-written in this regard. For example, they provide insights at how to grow your application's structure in several ways: http://flask.pocoo.org/docs/becomingbig/ http://flask.pocoo.org/docs/becomingbig/, http://flask.pocoo.org/docs/patterns/packages/ http://flask.pocoo.org/docs/patterns/packages/ and http://flask.pocoo.org/docs/patterns/appfactories/ http://flask.pocoo.org/docs/patterns/appfactories/. Generally speaking, http://flask.pocoo.org/docs/patterns/ http://flask.pocoo.org/docs/patterns/ gives a good overview of things to explore in Flask. Edit: I elaborated a bit more. Please note that I'm not advocating anything, just giving my opinion on their documentation.
- iampims 16y ago
  Indeed, I’m going through the docs as we speak and I’m impressed by the quality of the docs and the examples provided are interesting. Thanks for reminding me about Flask.
  - FraaJad 16y ago
    you should definitely check out Pyramid then: http://docs.pylonshq.com/pyramid/dev/narr/introduction.html http://docs.pylonshq.com/pyramid/dev/narr/introduction.html
chipsy 16y ago
This is true of many(most?) open-source library/framework/engine/API projects. They suck and don't do more than demos because they were written with insufficient perspective for anything beyond that. So do anything more, and they suddenly collapse.

by iampims 16y ago

nakkiel 16y ago

I found flask's documentation quite well-written in this regard. For example, they provide insights at how to grow your application's structure in several ways: http://flask.pocoo.org/docs/becomingbig/ http://flask.pocoo.org/docs/becomingbig/, http://flask.pocoo.org/docs/patterns/packages/ http://flask.pocoo.org/docs/patterns/packages/ and http://flask.pocoo.org/docs/patterns/appfactories/ http://flask.pocoo.org/docs/patterns/appfactories/. Generally speaking, http://flask.pocoo.org/docs/patterns/ http://flask.pocoo.org/docs/patterns/ gives a good overview of things to explore in Flask. Edit: I elaborated a bit more. Please note that I'm not advocating anything, just giving my opinion on their documentation.

iampims 16y ago
Indeed, I’m going through the docs as we speak and I’m impressed by the quality of the docs and the examples provided are interesting. Thanks for reminding me about Flask.
- FraaJad 16y ago
  you should definitely check out Pyramid then: http://docs.pylonshq.com/pyramid/dev/narr/introduction.html http://docs.pylonshq.com/pyramid/dev/narr/introduction.html

chipsy 16y ago

This is true of many(most?) open-source library/framework/engine/API projects. They suck and don't do more than demos because they were written with insufficient perspective for anything beyond that. So do anything more, and they suddenly collapse.