I suggest a similar website (actually the latter is a total copy of the former), the work will be a motivation for many people to start learning WEB2PY. Also short intros to WEB2PY - probably what / how / when can be done (more or less a cookbook). And last but not least - how can anyone find a work with WEB2PY - there are no projects, no search and demand announced, at least not officially?
On Jul 17, 6:24 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > I am not familiar with those web sites. What do you suggest? > > On Jul 16, 10:18 pm, Vidul Petrov <vidul.r...@gmail.com> wrote: > > > > > Hi Massimo, > > > I fully agree, everything is very well said IMHO. > > > Only one small addition - most of the MVC users have never even heard > > about most of the features (not to mention the rich set that WEB2PY > > offers). > > > Do you think that a website for WEB2PY like jobs.perl.org and > > jobs.rubynow.com would help (probably some sample works should be > > shown there also)? > > > Regards, > > Vidul > > > On Jul 17, 5:49 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > Pareto (http://en.wikipedia.org/wiki/Pareto_principle) once said that > > > 80% of effects come from 20% of causes. For software we can re-phrase > > > as 80% of users use only 20% of features. > > > > These are not at all a scientific statements but you understand what > > > they mean. > > > > We can add more and more features to web2py with the effect that: > > > - web2py grows in complexity to the point that it becomes harder to > > > maintain > > > - web2py gets slower > > > - I spend all my time reviewing patches instead of improving > > > documentation > > > - You spend all your time thinking how to improve web2py instead of > > > building applications with it > > > - Many of these improvement will not buy us a significant number of > > > users. > > > > I am not trying to discourage people from submitting patches and I > > > very very much appreciate people who have done so. Most if not all the > > > patches that I have received were good and needed. I am sure I will > > > continue to receive excellent patches. > > > > Yet, when discussing the roadmap it has to be clear that the point > > > should not be adding new features. The goal should be locking existing > > > features: make sure they are well documented, make sure there are no > > > problems, make sure everything has tests. > > > > We also need a plugin system but that is not a new web2py feature. > > > That is a set of specifications and naming conventions for writing > > > models/views/controllers. It is possible that we may have to modify > > > admin as result of these specs (in order to apply/remove plugins). > > > > Finally, this community has to do a better job at outreach. You should > > > talk to your friends and blog about web2py. You must talk about the > > > applications you build with it. We do not lack developers. We lack > > > salesmen. This is not because we want to have more user but because > > > more users means web2py is tested more, there will be more web2py > > > jobs, and you (as early adopters) will have a better chance to sell > > > your web2py based solutions. > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
