This does look nice but we can solve the configuration difficulty of Webpack without switching tools. Webpack should be the standard we all get behind until there is a tool that offers significant improvements, not just being easier to use.

We are using an internal NPM package for common Webpack settings similar to the JetBrains library [1]. With that setup, our Webpack configs are much easier to use. There are other libraries like webpack-config [2] that give you a fluent api and allow common configs to be extended.

[1] https://github.com/JetBrains/ring-ui [2] https://www.npmjs.com/package/webpack-config

Django

PostgreSQL + Mongo + Memcache

Apache + wsgi

ipdb lets you use pdb in a ipython shell which makes it much more powerful. http://pypi.python.org/pypi/ipdb

I hate 'me too' comments but IPDB IS A GODSEND. Once you use it you will:

* Wonder how you ever did without it

* Wonder why on earth it's not a standard part of Python

* Free your code of crappy conditional debug prints forever

* Take ipdb to bed and cuddle it at night

Just:

    import ipdb

Then where you'd like to start debugging:

    ipdb.set_trace()

Type 'help' for help.

Here's a similar project supporting the same syntax written in python that woks in vim.

http://github.com/rstacruz/sparkup

Im in a similar situation, testing a move from magento to satchmo. Still in early testing but it does seem like a really solid cart which is much faster.

The thing that really helps satchmo is the django base and the huge number of reusable apps available.

In magento if you need forum or cms you need to add bridges to other packages all with their own auth and coding style. With satchmo you can plug in one of the django forum apps apps let it share user registration with the rest of the site.

The way that django has embraced reusable apps is the killer feature of the framework for me.

I really love the Django style architecture and want to use it but I thought I would see if some of the smart hackers here knew of a showstopper in the satchmo cart other than the name.

Its good to see some more options but it still does not compare to jQuery UI with its unified styling and theme roller.

I like having jQuery UI components standalone and using them as needed, relying on compression and merging tools like yui compressor to do their job.

Being a smaller core set of components is not really a big benifit.

They have a good point about the api improvements over jQuery UI but i can't see it being enough to switch.

Its cool that css frameworks are starting to use fluid widths instead of fixed px found in most original grid layouts.