I have to disagree with that experience - probably each to their own -
python certainly has its limitations. I only started using python for
GAE - being a J2EE guy for way too long (still). I am enjoyng the
freedom of things like closures, instant gratification (change the
server code, refresh the
I tolerate javascript. I am also tolerating python.
GTK is a huge gift from google because I have become too used to to
decipher problems from cryptic java compilation logs. Familiarity
breeds contempt - contempt for the ways others do their programming.
It's hard for me to work with scripting la
I would like to echo Aral's post. Language wars generate noise, not
analysis. It's no surprise that the top four issues *by a mile* are
just adding language ABC. It is depressing that people are working on
that at the expense of other things.
Admittedly, I am assuming that providing a complet
Ciao Marzia -
I forgot to ask you this question yesterday during the "Chat with the
GAE team" session (which, by the way, I think is a great idea).
Will the "service for storing and serving large files" be something
like S3, totally separate from the datastore, or would it be in the
form of a ne
To illustrate my point further with an analogy:
Google App Engine is here right now:
http://icanhaz.com/rightscaleweb
It needs to be here:
http://icanhaz.com/rightscalepremium
Aral
On Nov 5, 3:54 pm, Aral Balkan <[EMAIL PROTECTED]> wrote:
> The roadmap is a great step forward, thank you.
>
> I
The roadmap is a great step forward, thank you.
I am, however, disappointed at seeing "Support for a new runtime
language" on the roadmap for the immediate feature.
Quite bluntly, I would have expected better triage.
There are showstopping issues in Google App Engine at the moment.
Application
Thank you for the response. It makes me feel better about investing
time into creating a significant app on the platform. Like I
mentioned, the core concept of keeping each pageview quick, is one
that I wholeheartedly support. I think that a fast site is probably
the most important usability fa
Hi,
Billing will allow you to scale your application to your heart's content.
So, in general, most quotas will no longer exist when billing is enabled.
However, the per-request High CPU limits in App Engine are in place to
protect the stability and responsiveness of the cluster as a whole. We know
On Nov 4, 5:08 am, "Rodrigo Moraes" <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 3, 2008 at 8:14 PM, johnP wrote:
> roadmap: "Billing: developers can pay for more resource usage"). I
>
> -- rodrigo
It's not clear what "paying for more resource usage" means. Yes, you
can buy more traffic, storag
On Mon, Nov 3, 2008 at 8:14 PM, johnP wrote:
> There is still a significant amount of development ahead. If it
> appears that my task is a non-starter for Appengine, I'd prefer to
> switch to pure django earlier rather than later.
>
> Can anyone provide some enlightenment for my dilemma? Thanks.
Yeah, John has a point... when the billing system is implemented, will
you guys relax the limits on CPU optimization per request? Avoiding
infinite loops or deadlocks is fine, but there are resource hungry
calculations we have to do... I'm gonna need to calculate the centers
and distributions of t
I still don't understand one aspect of Google's approach - regarding
CPU limits. For example, consider my application, a personal
organizer. Each page view needs to tie together disparate entities;
there are lots of writes; etc. The final result of the application is
the creation of reports (us
Dear Marzia
Can you say a bit more about the Service for storing and serving large
files?
Actually, I want to write a html form with file upload. After the
form is submitted,
an email will be sent out containing the form data and a link to
download the
uploaded files.
Will the Service for stori
the short answer is, at least in the short to medium term, each app
will be limited to a single language. multi-language apps, sharing
datastores across apps, and inter-app RPCs are definitely interesting
ideas, and we've had fun discussing them internally. they're not on
the roadmap, though, and
Ah, I understand the question now. For the Python runtime, the App Engine
frontend actually sends requests for your app to one or more Python
Interpreters for your app.
The I/O talk 'Building a Production Quality Application on Google App
Engine' actually deals with this topic when talking about
> Lastly, concerning Bill's comment, I'm not entirely sure what you have in
> mind when you ask if they will be running on the same 'VM', immediate plans
> for new language support would most likely follow the same general theme as
> python support. Meaning, you would upload your application to A
Hi,
First to further what Jon was saying, the roadmap has to do with our feature
development plans, and not with issue fixes. In addition to building new
features, the team will also continue fixing issues with the system. These
include those issues listed in the tracker, as well as an overall d
This is great! Thanks Marzia et al! It's a great step towards giving
us visibility to what we should expect and what we should be planning
for.
On Oct 24, 5:45 am, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Many of you have expressed interest in learning about what's coming next for
>
Hi Jeffrey, I appreciate your feedback. You definitely have good
insight into the issues and the reasons why they are still issues :-).
We recently did such a fixit of low hanging user bugs and these fixes
will be pushed soon. I don't remember if we got everything that you
mentioned in your email,
Nice with some roadmap information, and also neccesary as i see it.
But to my big disappointment I do not se long-running processes .-(.
I'm very well aware that it raises a lot of quistions, but come-on.
Using webcron (and keeping every request på 8 sec) seems like a lot of
unneccesary enginerin
Great to finally get official about the Roadmap
On Oct 24, 8:01 am, Jeffrey Rosen <[EMAIL PROTECTED]> wrote:
> Thanks for clarifying this! I am especially relieved to see the
> datastore import/export and the billing option announced. I am also
> relieved to see recent advances like the HTT
Thanks for clarifying this! I am especially relieved to see the
datastore import/export and the billing option announced. I am also
relieved to see recent advances like the HTTPS release which now lets
us add things like Google Checkout integration. As someone who runs
their entire business (ht
"Support for a new runtime language"
What an evil way to tease all those python-a-phobes out there! Should
we start a pool on what the mystery language is? I've got $10 that
says java.
oh yeah, and Bill's question is a great one.
-peter
On Oct 23, 10:11 pm, Bill <[EMAIL PROTECTED]> wrote:
> >
> * Support for a new runtime language
Would you be able to say how different languages will be partitioned?
Could you access a single datastore with more than one language or
have different languages running on the same VM?
--~--~-~--~~~---~--~~
You received this
Thanks for the feedback - good to know you are listening to our
concerns.
The big one for me is billing, which presumably will remove all the
quota issues. I have an application just about ready to go live, and I
don't anticipate huge resource use, but I'm hesitant about launching
until I can be
This is fantastic, thanks Marzia!
There also seems to be a fair amount of clamor for beefing up the
Image API, any chance that might be in the pipeline?
Also, I would like to suggest that the documentation be fattened up,
especially concerning the inner workings of datastore/BigTable and
related
26 matches
Mail list logo