On Sun, 2009-08-23 at 15:29 -0700, Jamie wrote: > You all might as well be arguing which is the superior OS. It doesn't > matter. > > Apple's OS's arguably have been superior to anything MS has ever put > out. Back in the day, for a very brief period, Apple was the dominate > player because first they shipped with BASIC preinstalled in ROM. > They maintained momentum because everyone was writing educational > software for the platform. MS zoomed past Apple once the PC became > more integral to daily life and "productivity" software became more > important. Now, Apple is starting to turn things around because their > Internet-centric and music stuff "just works". > > The point is that everything is about the applications. People don't > care about which is coded to a higher standard, is more secure, has > better documentation, or slicker produced marketing campaign. They > buy a particular PC (or use a particular framework) because it allows > them to do something that the others don't. > > If you want Pylons adoption to take off, a subset of the people > treading this thread ought to pool their efforts and develop a killer > Pylons-based application. Maybe target phpBB, or produce an awesome > wiki package or bug tracker. Or even better: an open-source e- > commerce platform (every single one out there sucks). Give them a > reason to abandon PHP, not just platitudes. When you've got a 100,000 > people using a Pylons-based app, interest in Pylons itself will > naturally follow.
Sorry, I totally disagree. The above may be true for Django, or for the average person purchasing a Mac, but it is expressly *not true* for Pylons. The Pylons target user is *not* someone looking for plug-and-play. You may be, that's fine, but if so, you are probably looking in the wrong place ( Django or Rails would be much better for that ). There is a market niche for people who looking precisely for "coded to a higher standard, is more secure, has better documentation". That niche does care about the very carefully made design decisions behind Pylons, and those are the people for whom Pylons is a good fit. Also, that niche cares a heck of a lot less about some killer app because they are looking for a foundation to write their own killer apps, not something to just use. Trying to market Pylons to people impressed by plug-and-play drop in apps is IMHO a waste of time and will backfire, because you are then selling people the wrong product. Never a good idea for any marketing campaign. You must know your competitive differentiation, your value proposition, and your ideal customer to market effectively, and you must targeting the right people with the right benefits. The main problem for Pylons marketing as I see it, is that the core developers don't seem to be concerned about it, so no one will put in time and effort to do something that is not wanted and appreciated and stand a good chance of being used. I have already railed against that in previous threads. I would love to see that change though, so I'm sure the discussion is still productive. Iain > > > On Jul 19, 5:11 pm, Iain Duncan <[email protected]> wrote: > > Taking Ben's suggestion, I just went ahead created a new thread. > > > > Mike Orr said: > > """ > > I have started a Talking Points wiki page to gather the essential > > points. Please add anything that's missing. > > > > http://wiki.pylonshq.com/display/pylonscommunity/Talking+Points > > """ > > > > Thanks Mike, what do you and the other core team propose we do from here > > with this starting point? It is probably the area where I can most > > helpfully contribute to Pylons, as I've done a fair bit of > > sales/marketing stuff and as I mentioned, I feel I have a real vested > > interest in making sure that clients feel good about the future > > viability of Pylons ( and Repoze, Pypes, etc ). > > > > As cheesy as it sounds ( and we don't have to call it that ), I think we > > need a clear "Pylons Vision Statement". The purpose and future goals of > > Pylons distilled into a few very clear sentences that help separate it > > from competition, but in a realistic and accurate manner. IMHO, I > > believe this has been one the main problems for TG, no real clear vision > > on what the framework was trying to provide and for whom. Some wanted it > > to be a django-competitor, others something different, and that has been > > an elephant in the room for too long now. > > > > iain > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
