The #1 Appengine Programmer Excuse for Legitimately Slacking Off

[Kaan Soral]

"My request is running on the SDK"

http://xkcd.com/303/

In 30 seconds I can probably go downstairs, get a tea and return back to see the results =)

[PK]

You might want to check out the workarounds suggested here and star some of the issues mentioned.

PK

www.gae123.com

[Brandon Wirtz]

I’ll Bite.

 

Why do people run on the SDK?  Everyone complains it is slow. The time it takes to set it up, and the slowness which it runs test passes can’t possibly be cheaper than running on a test App on GAE.

 

I thought the SDK was just something that was invented so you could tell your boss… “If Google ever kills GAE they’ll give 180 days notice and we could run on the SDK for another 180 days, plenty of time to port the code to Azure”

 

-Brandon

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/sNIfQ0eHw3AJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Joshua Smith]

When you are working on small apps, it's plenty fast enough to do iterative testing. In particular, you can tweak html and css (or even main.py) without restarting anything.

I've never complained that its slow. It's much faster than doing a deploy to do tests.

On my apps with big data stores where I need to test on the real server, I often just start it up and hit the hello world page to make sure I don't have a syntax error in my main.py

[Barry Hunter]

Refreshing a page to see how a change worked, is still quicker than
waiting for a deployment.

Sadly not all of us can just create a large block and have it work.

Need interactive development. The SDK is used for development, not
just running test harnesses.

[Brandon Wirtz]

Hmm. I find that AppCFG.py handles the number of lines of code I can
generally change in a pass in a few seconds. It doesn't upload the whole
app.

Granted if I was tweaking the HTML or CSS I could see that 8 seconds to do
an update might slow me down, or that Caching might be annoying.

Typically I do that kind of work from the static output of the app. Save the
CSS and output HTML locally tweak, tweak, tweak, Upload.

Not saying your work flow isn't right. Just interesting, because I've been
so paranoid about small differences in the SDK vs GAE that I have forced my
Guys to work in the cloud. (plus then I can suck down their code every so
often to see if they are doing dumb things)

[Barry Hunter]

> (plus then I can suck down their code every so
> often to see if they are doing dumb things)

Surely the job for a proper version control system :)

[Brandon Wirtz]

This is for between versions.

Programmer is fighting through Code but where they have to get the fox the
hen and a bag of corn across the river.

They tell me they can't figure it out. I download their code and I see that
they are putting a scorpion on the fox and having him swim across on his
own.

-Brandon

-----Original Message-----
From: google-a...@googlegroups.com
[mailto:google-a...@googlegroups.com] On Behalf Of Barry Hunter
Sent: Sunday, December 04, 2011 1:42 PM
To: google-a...@googlegroups.com
Subject: Re: [google-appengine] The #1 Appengine Programmer Excuse for
Legitimately Slacking Off

--

[PK]

+1 for barryhunter's first comment.  Four years of development on GAE suggests, that in general, parity between the dev server and production has not been a problem. Uploading an app has been expedited recently and is adequate for its purposes but it will need to become sub-second to be considered as a development cycle option. 

Here is some real hard data, from a real app, with real functionality used by real users. Who can  wait for one minute, for each set of edits, in the 21st century?

$ appcfg.py --secure update ...

Application: ...; version: 1-7-31

Host: appengine.google.com

Starting update of app: ..., version: 1-7-31

Scanning files on local disk.

..

Scanned 1500 files.

Cloning 191 static files.

Cloned 100 files.

Cloning 1538 application files.

...

Compilation starting.

Compilation completed.

Starting deployment.

Checking if deployment succeeded.

Will check again in 1 seconds.

...

Deployment successful.

Checking if updated app version is serving.

...

Uploading index definitions.

Uploading cron entries.

Uploading task queue entries.

real 1m0.530s

user 0m4.110s

sys 0m0.320s

It also allows to develop while disconnected from the internet. And if you apply the suggested work arounds the dev server's performance becomes great for dev. purposes.

Regarding the comment: "I thought the SDK was just something that was invented so you could tell your boss… “If Google ever kills GAE they’ll give 180 days notice and we could run on the SDK for another 180 days, plenty of time to port the code to Azure”"

This was exactly what it was not invented to be :-) Even when the notice is three years...

PK

http://www.gae123.com