[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-04-18 Thread MdeA
I've been developing on Google Application Engine since its beginnings, when Python (v2.5) was the only language supported. I came from the world of ASP/IIS and LAMP stacks, so suddenly not having to worry about scaling-up a web server and having a DB pretty much built-in was very appealing to

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-20 Thread Patrice B
Hi guys, A few months back, I had a similar reflexion on current trends regarding AppEngine, which I called "the end of paas", which could be called "end of serverless" in a way https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!search/paas|sort:date/google-appengine/DHMMv5r

Re: [google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-20 Thread Giuliano Ribeiro
Unfortunately I need to say the same. Nowadays, it seems Google is forcing us to use GKE or Cloud Run, as all the App Engine "magic" gone. I've been using App Engine my last 8years, and is clear, the Google strategy is not App Engine anymore. Giuliano Ribeiro Cloud and Software On Fri, Mar 20

Re: [google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-19 Thread john
+1 I also lament the loss of the turnkey environment that app engine used to provide. I can only presume that the business model for it isn’t very profitable, otherwise someone else would reproduce it. On Monday, March 16, 2020 at 2:47:25 AM UTC-4, Nickolas Daskalou wrote: > > Same experien

Re: [google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-15 Thread Nickolas Daskalou
Same experience for us. 10 years ago App Engine was a revolution. Now it's almost revolting. Agree with the hard to set up development environment for the newer App Engine installments. Other pain points too, like no shared Memcache replacement (we're told NDB for Python 3 is fully ready, when i

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-15 Thread Vitaly Bogomolov
+1. GCP.AppEngine.StandardEnvironment.SecondGeneration looks like a terminal point for me. You must stop using GAE. 10+ years of GAE use. WBR, Vitaly. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and st

Re: [google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-15 Thread Rajesh Gupta
I have been a user of google appengine for 7-8 years. Yes, its disappointing The local dev console did not improve. There is no easy way to import/export from local dev to the cloud. I am really unhappy that they did not provide tools for migrating data into new schemas. First they promoted map

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-15 Thread Matthew Parkes
I have to totally agree with this. My experience has been the same coming from AppEngine Standard python 2.7 I decided to try and migrate one of my apps to Python3.7 but was extremely frustrated and put off with the whole experience. I lost a lot of nice framework that made decisions easy and

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-15 Thread Brian Ruuska
Glad to hear I'm not the only one disappointed with it all. I started using App Engine when it was in beta, and launched a one-person business when it went GA. It's so overwhelming attempting to port my product to the new environments that it's much more than a one-person effort. And with all th

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

2020-03-14 Thread Kaan Soral
A small update, after my conclusion, I went ahead with my live trial and finally started a new journey ~/Desktop/APPENGINE/cloudsdk184/bin/gcloud app deploy -> after every small change ~/Desktop/APPENGINE/cloudsdk184/bin/gcloud app logs tail -> replaces the local development server - instead of