Here's a radical and possibly stupid idea for Massimo to think about on a Saturday morning.
Forget web3py. Think about web2go. There's lots of promise today for a good full-stack Golang framework. The Golang folks eschew the notion of full-stack frameworks, but I don't think many of them get it. If you have an intuitive, easy-to-use, and relatively performant CRUD, full-stack framework in Golang, I guarantee you it's going to be a hit. My lightweight web/networking apps these days are written in Golang. The beauty of it is that it's so easy to get deployed. Golang's builtin http handling is rock solid. There's no need for gunicorn, uwgsi, etc. About Python, I know many people are still on Python 2, but to me it's legacy. Many people completely moved on to Python 3. That makes web2py very outdated. The notion of Web3py is still a good idea *right now*. But by the time you can deliver Web3py, it is likely that it will be technologically outdated. So, there it is. Web2Go. You've learned many lessons from having built web2py. These experience will make your CRUD full-stack framework very meaningful. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
