[okaleniuk]

It is a terrible name. You can do web dev in pure Assembly and it actually makes sense in contrast with yet another framework over a framework over an interpreter over POSIX-libraries.

E. g. monitoring for mission critical servers. You really don't want the whole stack of unverified goodies on these machines, but since you already have TCP/IP for SSH, writing a simple web-server that reports machine health over HTTP is like a half-day job.

And it's verifiable since it's small. It doesn't drag the whole Python infrastructure with it.

[smitty1e]

I thought the flowers bracketing the name unappealing as well.

While the intro complained about application scalability, I wondered about Assembly's relationship to Flask blueprints.

[phlakaton]

You're going to dump on them for flowers on the home page? Really??

I think more projects should feature flowers. They're nice. I feel confident O'Reilly would back me up on this one.

[ben_jones]

In the context of discussing the library's marketing/presentation I think the the branding is also fair game. It's also a little odd how at the bottom of the page it gives credits to the image as a non-commercial license. Personally I would recommend avoiding any licensed assets in such a project all together (when possible).

But at the end of the day if you build and release an OSS project you should get to do whatever you want with it, like the use of emojis that was discussed in the postwoman.io project that came up last week.

My opinion is who cares, we should be discussing its technical merits first and foremost on a forum like this.