Whats your thoughts on base camp?

As a CTO I would guess something from 4% - 6% some will get more depending on a number of factors. The thing is a CTO could get 10%, but if it is a bad idea or mismanaged then that 10% might be worth $0 after 4 years. A well managed, great idea might still get you $0 but it might also get you $1,000,000. You never know. You have to way up if you think this idea is something which will be viable.

Flask or Django would be good options.

Django is very modular so you can pull out or change the bits you do not like (templating you can use jinja, orm you can exchange for sqlalchmey).

Flask, you build what you want (enough said).

If you are removing Django templating and ORM, it makes completely sense to use something else.

Flask is an awesome option, I'm building things with it for some years now.

I have to agree with iurisilvio here.

If you are pulling out the Django templates and the ORM you should just use Flask. You shouldn't choose a framework and then immediately start taking it apart if there is an alternative that comes the way you want basically out of the box.

The django project is a good example of a large opensource project which has aged well. http://github.com/django/django

I don't know what would be of my life right now without Django and I can't praise it enough... but "good example of readable python-code", it is not.

However, I think it's one of the best examples of phenomenal documentation.

I learned a lot from reading the Django codebase. I didn't read it like a book, I read parts of it as I tried to figure out how to do things in Django, but I never felt like the code was bad. This was around 5 years ago so it's possible things have gotten more convoluted since then.

If the OP wants to grok a small, discrete codebase then I agree that Django is not what he's looking for.

I know it is a good project, but would you recommend it for someone to read through the codebase?

(Honestly, looking at the repo, I don't even know where to start if I wanted to do a read through. Has anyone created a map? :)

No, definitely no. Django aged well in terms of being alive, usable and comfortable to use in most usecases. But the codebase... Let me explain. Currently it works as "pay-to-get-a-feature" by crowdfounding. It not a bad thing, it gives good features we all need, but it is a bit sad fact when you look at Rails. So, it doesn't mean Django developers doesn't care about code, they care. But codebase is so big and complicated(because some code needs to be refactored)... it is common to see that some bug cannot be simply fixed by two lines, because some core member insists "this all should be reworked".

Have you considered building something with Django and figuring out the magic as you go along??

I would start with django.core.handlers.base.BaseHandler (https://github.com/django/django/blob/master/django/core/han...), which is Django's Front Controller.

This usually happens when they are doing infrastructure or software updates to the site.

It will be back online soon.

You can also check there operations page

https://twitter.com/sfnet_ops

I managed to solve the travelling sales man problem in `P` time but lost the commit.

Before I get trolled that was a joke

Nice idea, you should certainly keep working on it.

Thanks for comment :-)

Thats a really constructive comment.

For a lot of people paypal is just fine and does the job they need it to do.

Its like the mac fan boys who comment on windows being crap. But for 90% of joe public it works and works well allowing them to edit word documents and browse the interweb. Its just the loud mouthed 10% who like to cry their balls off and tell people what they are using is wrong.