No no, this post is for all: "Having doubts about AppEngine"

1) """My concerns center around Google’s commitment to the App Engine
project"""

My concerns center around Google’s commitment to Django template.

2) """Here on the GAE forum elementary questions about how GAE ticks
go unanswered for months"""

Also about the template system.

3) """Communication with the developer community here is abysmal
compared to the investment in developer relations made by companies
such as Microsoft Redhat or Amazon"""

Django is free, no investment.


On Aug 30, 9:05 pm, Michael Schreifels <[EMAIL PROTECTED]> wrote:
> Davide,
>
> I really don't see the Django template language being a valid concern
> at all. It is just a library that Google provides, no one is forcing
> you to use it.
>
> And further, personally I think that if you find Django templates too
> limiting, you probably don't fully understand it. I switched to Django
> after coding with Ruby on Rails and PHP, both of which allow you to
> embed code right in your templates. It was a difficult transition at
> first, but the restrictions placed by the Django template language
> make sense, and they encourage good programming practices of the
> separation between programming logic and presentation code.
>
> And if you're concerned about reusing blocks of code, the concerns
> about {% with %} are only relevant to Django < 1.0, and the devs have
> been telling users to use SVN (which is very stable) and not 0.96 for
> MONTHS now. (Yeah, AE only supports 0.96 out-of-the-box, but that
> makes sense. Why would Google want to track SVN? I just have my own
> checkout of Django I use. And besides, Django 1.0 is due for release
> next week. I guarantee Google will support it.) And besides, I have
> never had to use {% with %}. Most code repetition I come across is
> more logically solved with block inheritance.
>
> I strongly recommend you upgrade to the latest Django beta and read
> the template docs. And if it really doesn't work for you, there are
> plenty of other options.
>
> This post is really about the problems that Google has with
> communications about where App Engine is going (and WHEN).
>
> On Aug 30, 4:56 am, Davide Rognoni <[EMAIL PROTECTED]> wrote:
>
> > Doubts about Django 
> > Templatehttp://groups.google.com/group/google-appengine/browse_thread/thread/...
>
> > On Aug 28, 12:09 am, javaDinosaur <[EMAIL PROTECTED]> wrote:
>
> > > I am starting to have doubts about continuing to develop my
> > > applications for GAE. My concerns are not technical although I have a
> > > some anxieties about transaction data propagation performance.
>
> > > My concerns center around Google’s commitment to the App Engine
> > > project. Compared to Amazon’s Web Service forums this place feels like
> > > a technical backwater. Developers hosting on Amazon AWS post
> > > interesting questions and get deep-dive replies promptly from Amazon
> > > staff. Amazon is releasing new Cloud development services monthly yet
> > > all we get is minor patches.
>
> > > Here on the GAE forum elementary questions about how GAE ticks go
> > > unanswered for months. Basic roadmap type info such as will we get SSL
> > > or scheduled tasks is missing.
>
> > > I just feel that the GAE Team is not building up any development
> > > stream in what should be the last 4 month run up to the year-end
> > > release. Communication with the developer community here is abysmal
> > > compared to the investment in developer relations made by companies
> > > such as Microsoft, Redhat or Amazon.
>
> > > What’s happened to the early buzz Google? Has the top bass pinched
> > > half the team to firefight problems on another project?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to