librelist archives

« back to archive

Future of flask

Future of flask

From:
Scott Czepiel
Date:
2015-07-12 @ 00:44
I have been studying and using flask for several months, and have 
developed several sites that I am very happy with.  I love the simplicity 
of flask, the ease of working with it, and the flexibility of choosing the
tools to integrate with rather than being coerced to use the approved 
building blocks -- an alternative approach that Django or Rails insists 
upon.

However I am concerned that flask development is not rapidly advancing.  
We have not had a release in 2 years.  I see that there is activity in the
github repo, but I fear that without new features being added and a sense 
of the project being actively moved forward, that eventually people will 
migrate to other frameworks for fear of being locked into a framework that
may become orphaned one day.

What is the current plan for maintenance of core flask?  And the  future 
development roadmap?

Again I must emphasize that I am very happy with what flask already 
provides, and do not see myself in need of immediate new features, but 
there will come a time when active development will be necessary, if for 
no other reason than to be able to keep up with other projects, eg. 
Sqlalchemy which recently had a major release.  It is still compatible 
with flask 0.10.1, but eventually something will break and without active 
development of core flask, developers will feel reluctant to commit to 
using flask.

I'm not asking for flask to become Django or rails, nor does the flask 
community need to be of equal size as those communities for us to prosper.
I would however like some assurance that there is interest and commitment 
among the leaders of flask to keep moving the project forward.

Any thoughts about my concerns?

Re: [flask] Future of flask

From:
Robert Shady
Date:
2015-07-12 @ 02:39
I've actually been concerned about this myself...

On 7/11/2015 8:44 PM, Scott Czepiel wrote:
> I have been studying and using flask for several months, and have 
developed several sites that I am very happy with.  I love the simplicity 
of flask, the ease of working with it, and the flexibility of choosing the
tools to integrate with rather than being coerced to use the approved 
building blocks -- an alternative approach that Django or Rails insists 
upon.
>
> However I am concerned that flask development is not rapidly advancing.
We have not had a release in 2 years.  I see that there is activity in the
github repo, but I fear that without new features being added and a sense 
of the project being actively moved forward, that eventually people will 
migrate to other frameworks for fear of being locked into a framework that
may become orphaned one day.
>
> What is the current plan for maintenance of core flask?  And the  future
development roadmap?
>
> Again I must emphasize that I am very happy with what flask already 
provides, and do not see myself in need of immediate new features, but 
there will come a time when active development will be necessary, if for 
no other reason than to be able to keep up with other projects, eg. 
Sqlalchemy which recently had a major release.  It is still compatible 
with flask 0.10.1, but eventually something will break and without active 
development of core flask, developers will feel reluctant to commit to 
using flask.
>
> I'm not asking for flask to become Django or rails, nor does the flask 
community need to be of equal size as those communities for us to prosper.
I would however like some assurance that there is interest and commitment 
among the leaders of flask to keep moving the project forward.
>
> Any thoughts about my concerns?
>

Re: [flask] Future of flask

From:
Samuel Taylor
Date:
2015-07-12 @ 02:20
For anyone who's interested, mistuhiko talked a little bit about the future
of flask on Talk Python to Me Ep. 13 a little bit ago:

http://www.talkpythontome.com/episodes/show/13/flask-web-framework-and-much-much-more

If I'm remembering correctly, it didn't sound like he had major plans for
new features.

Thanks,
Samuel

On Sat, Jul 11, 2015 at 8:44 PM, Scott Czepiel <sczepiel@gmail.com> wrote:

> I have been studying and using flask for several months, and have
> developed several sites that I am very happy with.  I love the simplicity
> of flask, the ease of working with it, and the flexibility of choosing the
> tools to integrate with rather than being coerced to use the approved
> building blocks -- an alternative approach that Django or Rails insists
> upon.
>
> However I am concerned that flask development is not rapidly advancing.
> We have not had a release in 2 years.  I see that there is activity in the
> github repo, but I fear that without new features being added and a sense
> of the project being actively moved forward, that eventually people will
> migrate to other frameworks for fear of being locked into a framework that
> may become orphaned one day.
>
> What is the current plan for maintenance of core flask?  And the  future
> development roadmap?
>
> Again I must emphasize that I am very happy with what flask already
> provides, and do not see myself in need of immediate new features, but
> there will come a time when active development will be necessary, if for no
> other reason than to be able to keep up with other projects, eg. Sqlalchemy
> which recently had a major release.  It is still compatible with flask
> 0.10.1, but eventually something will break and without active development
> of core flask, developers will feel reluctant to commit to using flask.
>
> I'm not asking for flask to become Django or rails, nor does the flask
> community need to be of equal size as those communities for us to prosper.
> I would however like some assurance that there is interest and commitment
> among the leaders of flask to keep moving the project forward.
>
> Any thoughts about my concerns?
>
>

Re: [flask] Future of flask

From:
Frank Valcarcel
Date:
2015-07-12 @ 02:55
Since Flask is so stable and flexible in terms of extensibility, the real
threats to the frameworks future won't necessarily come from updates to
ancillary libraries. Had SQLAlchmey's update caused a breaking change, the
Flask-SQLalchemy extension would have been easily updated.

The podcast mentioned by Sam actually had some interesting points made
by Armin. What I took from it was that the real issues that
threaten the framework come more from changes in the governing protocols
(http2) and the status quo of web application development in general. Armin
has expressed his desire to keep Flask minimal and maintained only enough
to remain stable.

Considering the lack of libraries that are compatible with Python 3, one of
the great things about Flask is that it's kept up with the development of
Python itself. I certainly feel that Flask will continue to keep pace with
the current state of web development as much as Python can.

On Saturday, July 11, 2015, Samuel Taylor <sam@samueltaylor.org> wrote:

> For anyone who's interested, mistuhiko talked a little bit about the
> future of flask on Talk Python to Me Ep. 13 a little bit ago:
> 
http://www.talkpythontome.com/episodes/show/13/flask-web-framework-and-much-much-more
>
> If I'm remembering correctly, it didn't sound like he had major plans for
> new features.
>
> Thanks,
> Samuel
>
> On Sat, Jul 11, 2015 at 8:44 PM, Scott Czepiel <sczepiel@gmail.com
> <javascript:_e(%7B%7D,'cvml','sczepiel@gmail.com');>> wrote:
>
>> I have been studying and using flask for several months, and have
>> developed several sites that I am very happy with.  I love the simplicity
>> of flask, the ease of working with it, and the flexibility of choosing the
>> tools to integrate with rather than being coerced to use the approved
>> building blocks -- an alternative approach that Django or Rails insists
>> upon.
>>
>> However I am concerned that flask development is not rapidly advancing.
>> We have not had a release in 2 years.  I see that there is activity in the
>> github repo, but I fear that without new features being added and a sense
>> of the project being actively moved forward, that eventually people will
>> migrate to other frameworks for fear of being locked into a framework that
>> may become orphaned one day.
>>
>> What is the current plan for maintenance of core flask?  And the  future
>> development roadmap?
>>
>> Again I must emphasize that I am very happy with what flask already
>> provides, and do not see myself in need of immediate new features, but
>> there will come a time when active development will be necessary, if for no
>> other reason than to be able to keep up with other projects, eg. Sqlalchemy
>> which recently had a major release.  It is still compatible with flask
>> 0.10.1, but eventually something will break and without active development
>> of core flask, developers will feel reluctant to commit to using flask.
>>
>> I'm not asking for flask to become Django or rails, nor does the flask
>> community need to be of equal size as those communities for us to prosper.
>> I would however like some assurance that there is interest and commitment
>> among the leaders of flask to keep moving the project forward.
>>
>> Any thoughts about my concerns?
>>
>>
>

-- 
Frank Valcarcel
Cuttlesoft <http://www.cuttlesoft.com>
850.692.9832
<http://www.cuttlesoft.com>