3 ms·

Hi, I'm a Product Manager on the App Engine team. We're actually (finally!) gearing up to offer Python 3. Would you like to be an alpha tester? Here's the sign

Hi, I'm a Product Manager on the App Engine team. We're actually (finally!) gearing up to offer Python 3. Would you like to be an alpha tester? Here's the sign-up form: https://docs.google.com/forms/d/e/1FAIpQLSfLXViTUmtY6Ed_Gm9HohVVe7HMKcT37_MvzgPpKIDQTkZNjg/viewform?usp=sf_link https://docs.google.com/forms/d/e/1FAIpQLSfLXViTUmtY6Ed_Gm9H...

lostmsu 8y ago
How about .NET Core?
- rattray 8y ago
  Ooc, why run .net core on gcp instead of azure?
  - tracker1 8y ago
    I'd presume the most common are probably other experience with GCP, other applications on GCP, or prefer GCP tooling to Azure. I haven't compared pricing, so no comment there. Lastly, anti-ms pov.
    - mcny 8y ago
      For me there's main reasons are 1. Free tier 2. Features in that order It is perfect for "hobby" projects that have no revenue today. If a "revenue strategy" emerges, it isofcourseeasy to enable billing but there is no 12 month $300 trial.
wikibob 8y ago
Can you share even a smidgen of what took so long (10 years!)? From various comments over the years here and elsewhere, I’ve been led to the understanding that Python 3 was “coming soon” several times. 1. Why now? 2. Is it true this time? 3. Will Python 3 keep up to date with new releases, or 5 years from now will we be stuck on 3.6? 4. What is the future and roadmap of AppEngine? The feeling in the community is that AppEngine is another Google Reader, and death may be imminent. Can you reassure us? 5. What is the future of Standard and Flex? Should all new projects be started on Flex? Is standard ever going to keep up with language releases? Thanks
- vira28 8y ago
  Awesome questions. We do understand from the company standpoint that its difficult to give the roadmap and the timelines of the product. However, a lot of the user's decision is completely based on the road map of the product. Without being clear on this, how would you expect users to use the product?!
- bradfitz 8y ago
  See https://news.ycombinator.com/item?id=17297472 https://news.ycombinator.com/item?id=17297472 elsewhere in this thread for why.
rhodysurf 8y ago
Awesome I have been waiting for this for soooo long

lostmsu 8y ago

How about .NET Core?

rattray 8y ago
Ooc, why run .net core on gcp instead of azure?
- tracker1 8y ago
  I'd presume the most common are probably other experience with GCP, other applications on GCP, or prefer GCP tooling to Azure. I haven't compared pricing, so no comment there. Lastly, anti-ms pov.
  - mcny 8y ago
    For me there's main reasons are 1. Free tier 2. Features in that order It is perfect for "hobby" projects that have no revenue today. If a "revenue strategy" emerges, it isofcourseeasy to enable billing but there is no 12 month $300 trial.

wikibob 8y ago

Can you share even a smidgen of what took so long (10 years!)? From various comments over the years here and elsewhere, I’ve been led to the understanding that Python 3 was “coming soon” several times. 1. Why now? 2. Is it true this time? 3. Will Python 3 keep up to date with new releases, or 5 years from now will we be stuck on 3.6? 4. What is the future and roadmap of AppEngine? The feeling in the community is that AppEngine is another Google Reader, and death may be imminent. Can you reassure us? 5. What is the future of Standard and Flex? Should all new projects be started on Flex? Is standard ever going to keep up with language releases? Thanks

vira28 8y ago
Awesome questions. We do understand from the company standpoint that its difficult to give the roadmap and the timelines of the product. However, a lot of the user's decision is completely based on the road map of the product. Without being clear on this, how would you expect users to use the product?!
bradfitz 8y ago
See https://news.ycombinator.com/item?id=17297472 https://news.ycombinator.com/item?id=17297472 elsewhere in this thread for why.

rhodysurf 8y ago

Awesome I have been waiting for this for soooo long