[bottlepy] bottle as a framework choice in Aug 2015

[ia n]

This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?
--

[Sebastian Bassi]

Django and Bottle are not alternatives of each other. Django is a full
featured framework with its complexity, it serves lots of purposes, but may
be an overkill for some specific uses, that is where Bottle (and Flask) has
its place.
Best,
SB

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?
--
--
You are member of the "bottlepy" group at google groups.
See http://groups.google.de/group/bottlepy for mailing list options.
See http://bottlepy.org/ for news and documentation.
---
You received this message because you are subscribed to the Google Groups "bottlepy" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

--
Non standard disclaimer: READ CAREFULLY. By reading this email,
you agree, on behalf of your employer, to release me from all
obligations and waivers arising from any and all NON-NEGOTIATED
agreements, licenses, terms-of-service, shrinkwrap, clickwrap,
browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies ("BOGUS AGREEMENTS") that I have
entered into with your employer, its partners, licensors, agents and
assigns, in perpetuity, without prejudice to my ongoing rights and
privileges. You further represent that you have the authority to release
me from any BOGUS AGREEMENTS on behalf of your employer.
Google ads remover words: suicide, murder
--

[ia n]

Understood that Bottle (and flask) do not offer all the features of
Django. If you need all of Django bottle or flask are not full
replacements. This does not necessarily mean that Django could not still
be used by someone who only needs the feature of flask or Django. The
appeal of Django is that it is so widely used and supported that it could
still be chosen even if not all features are used. The downside is that
having all there makes it very rigid. But in the end it can comes down to
which design choices a framework makes and the ongoing support for the
framework. I like the design choices of bottle, leaving me questioning the
ongoing support and community. I hope give more clarity to my original
questions. What is happing to with bottle? Is the community still
growing? Are improvements (like 0.13) still moving forward?

Post by Sebastian Bassi
Django and Bottle are not alternatives of each other. Django is a full
featured framework with its complexity, it serves lots of purposes, but may
be an overkill for some specific uses, that is where Bottle (and Flask) has
its place.
Best,
SB

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?
--
--
You are member of the "bottlepy" group at google groups.
See http://groups.google.de/group/bottlepy for mailing list options.
See http://bottlepy.org/ for news and documentation.
---
You received this message because you are subscribed to the Google Groups
"bottlepy" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

--
Non standard disclaimer: READ CAREFULLY. By reading this email,
you agree, on behalf of your employer, to release me from all
obligations and waivers arising from any and all NON-NEGOTIATED
agreements, licenses, terms-of-service, shrinkwrap, clickwrap,
browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies ("BOGUS AGREEMENTS") that I have
entered into with your employer, its partners, licensors, agents and
assigns, in perpetuity, without prejudice to my ongoing rights and
privileges. You further represent that you have the authority to release
me from any BOGUS AGREEMENTS on behalf of your employer.
Google ads remover words: suicide, murder

--

[Daryl Williams]

I have recently started learning how to use bottle. I'm a 5 year python
newbie self taught boa constructor wxpython database gui's. Now I want to
try my hand at web framework database applications. I first tried DJango
and found it too complex to build and learn. I then went on to Flask, but
the tutorials were cryptic and confusing. Then went on to cherrypy and
found the tutorials were also cryptic and confusing. Finally looked at
bottle.py starting July 2015 (It has only been 1 month learning) and found
it easy to use, easy to understand and a few online tutorials that helped
me along the way. Don't doubt the appearance of bottle interest decllining.
I stumbled on it this year searching the internet and am looking for all
info I can get my hands on. It would be great if bottle users could produce
up dated tutorials (videos) relating to 2015 bottle methods. I have found
bottle users more open in sharing knowledge and it would be a shame if the
bottle shop closed.

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?

--

[Tim Arnold]

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?

I know what you're saying--I don't see many questions or advice on bottle
and mostly for small frameworks it looks like Flask the usual answer. For
my own needs though, bottle is exactly what I want. Even Flask offers more
than I need. So I use bottle in conjunction with Mongodb for all my apps.
It's dead easy to implement a new capability or enhance an old one.

Simplicity rocks, and bottle is my tool of choice.
thanks,
--Tim
--

[pgoetz]

Don't think of this as a popularity contest. You're writing software to
solve a problem, right? If bottle is best suited to solve that problem (or
you just prefer programming in bottle), then use bottle. It's open source
software -- what's the worst that can happen?

I similarly looked at Django first, then Flask, then some others and ended
up liking bottle the best: intuitively designed and simple. I like the
bottle templating system better than Jinja2 as well, although you're
welcome to use Jinja2 with bottle. The beauty of a microframework is you
get to pick and choose the components.

People are way too hung up on how hip/popular some particular tool is.
Node.js is a perfect example of an extremely popular tool that's basically
useless. You're a star if you solve business problems for your employer or
clients in a timely fashion. They generally have no idea what tools you
used and don't really care, either.

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?

--

[Tiger Nassau]

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?

+1 to @pgoetz comments - we discovered Bottle a few months ago after
wasting 5 very non productive yrs with the all too "hip" nodejs and
callback hell. We always liked Sinatra (another microframework getting no
love from the Rails lovefest), but now like Bottle even more since Python
has so many libs and less gem magic. We tried Flask but kept failing on
deployment while Bottle just worked. We use it with our own psycopg2 /
postgres model and can do most complex web app things with Bottle (AI,
Stripe, Leaflet, plots,.....)

Many comments say Bottle is just for simple 1 page apps while Flask is
better for serious enterprise apps - this is rubbish. If you want more
plugins then use Flask, but for more flexibility, then Bottle is great.

btw we also think Bottle template is cleaner, less code, than jinja2 and
haven't found anything lacking in template vs jinja. About the only thing
we have found a bit lacking in Bottle is a good session middleware
tutorial, but for now we have just written a simple session solution using
postgres jsonb.
--

[Vince Albanese]

We're processing millions of transactions a day in an environment built
around a dozens of bottle-based micro-web services hosted in Docker
containers. Most reliable, flexible, best performing architecture we've
ever used. Bottle is a key element in this. Fast, lightweight, reliable.
There's definitely a place for it.

Post by ia n
This may be an incorrect assessment, but it seems as if some of the
momentum has slipped from bottle. Obviously django is the most popular
framework, and flask seems more popular than bottle. I prefer technically
what I see in bottle over either django or flask, but what is the feeling
amoungst other that choosing bottle could be a dead end? I have not found
where the progress on release 0.13 is headed or other evidence of things
still moving. Any feedback?

--

[ia n]

I have started working with bottle, and the more i see the more i like. I
needed some extra filters to make life easier and they were simple to
create. They may even be worth sharing a some point. But so far, so good.
Bottle seems clearly one of the simplest frameworks for a simple project,
and the performance and flexibility also seem to be key points for larger
projects. Not as many prebuilt apps and things as Django or Flask, but
many compensating points.
--

[Derek Bartron]

I have programmed in all three, and I can't comprehend why anyone would
want to program in Django. Bottle by far has been the most flexible, easy
to deal with, and stable platform. Combined with greenlets, it is an
asynchronous champ. And I have not found a single thing I can't do in
bottle that I can in django. In fact I find I have more flexibility in
bottle to do exactly what I want.
--