5 ms·

Wait, you just said in a separate comment that you migrated away from App Engine. You also just said that you used it very effectively back when it was a diffe

by fhoffa 3y ago

Wait, you just said in a separate comment that you migrated away from App Engine. You also just said that you used it very effectively back when it was a different thing. I think we agree in many more ways than we disagree. Source: https://news.ycombinator.com/item?id=38020604 https://news.ycombinator.com/item?id=38020604

latchkey 3y ago
Ugh, now you're making me explain myself due to your poor understanding of what I was saying and taking different comments in different threads out of context. "We migrated"... meaning that over time, everyone is migrating from the concept of using GAE as a first choice, to using things like Run/Functions. Not that I actually physically took code for GAE and moved it to R/F. For example, my last project, I choose to use GCF, instead of GAE. The reason I went straight to GCF is because it is effectively what GAE has morphed into today. This isn't a slight on GAE at all. I've updated previous comment to hopefully clarify this for you. Again, I have used GCP extensively since about 2009. By the way, much of what you use today was a result of things I did back when I co-founded the Jakarta Apache project, open sourced Tomcat from Sun, brought Lucene under the umbrella, blah blah blah... I've been around the internet since 1991.
- deleted 3y ago
  [deleted]
- fhoffa 3y ago
  This is awesome, thanks for all the background info. Now let me give you an example of App Engine deprecating stuff: - In 2012 App Engine deprecated the "Conversion API". - They notified this deprecation in August 2012, and they told users it would stop working only 3 months afterwards. - You were affected by this deprecation. - You created an alternative to it, that worked on Heroku. Source: https://groups.google.com/g/google-appengine/c/-JJccGx5RRk/m/7umzYSzmyFMJ https://groups.google.com/g/google-appengine/c/-JJccGx5RRk/m... Did I get this right? You are awesome. We are just choosing to remember the past with different colored glasses.
  - latchkey 3y ago
    Yea, they deprecated something. I even noted that the market is small for it in the thread. I built another solution in a short amount of time, and even gave it away because it really wasn't something people were using a lot of. It was a super niche product. That also wasn't even AppEngine, it was just a nice to have, for me, sub-service. There was a point where people were upset about GCP and Google changed their whole deprecation policies to be more vocal and longer term about things. I really don't understand your point. What's the big deal?
    - fhoffa 3y ago
      You think we are disagreeing, meanwhile I just love how much I've learned (and confirmed) thanks to your replies. Thanks for sharing!

by fhoffa 3y ago

latchkey 3y ago

Ugh, now you're making me explain myself due to your poor understanding of what I was saying and taking different comments in different threads out of context. "We migrated"... meaning that over time, everyone is migrating from the concept of using GAE as a first choice, to using things like Run/Functions. Not that I actually physically took code for GAE and moved it to R/F. For example, my last project, I choose to use GCF, instead of GAE. The reason I went straight to GCF is because it is effectively what GAE has morphed into today. This isn't a slight on GAE at all. I've updated previous comment to hopefully clarify this for you. Again, I have used GCP extensively since about 2009. By the way, much of what you use today was a result of things I did back when I co-founded the Jakarta Apache project, open sourced Tomcat from Sun, brought Lucene under the umbrella, blah blah blah... I've been around the internet since 1991.

deleted 3y ago
[deleted]
fhoffa 3y ago
This is awesome, thanks for all the background info. Now let me give you an example of App Engine deprecating stuff: - In 2012 App Engine deprecated the "Conversion API". - They notified this deprecation in August 2012, and they told users it would stop working only 3 months afterwards. - You were affected by this deprecation. - You created an alternative to it, that worked on Heroku. Source: https://groups.google.com/g/google-appengine/c/-JJccGx5RRk/m/7umzYSzmyFMJ https://groups.google.com/g/google-appengine/c/-JJccGx5RRk/m... Did I get this right? You are awesome. We are just choosing to remember the past with different colored glasses.
- latchkey 3y ago
  Yea, they deprecated something. I even noted that the market is small for it in the thread. I built another solution in a short amount of time, and even gave it away because it really wasn't something people were using a lot of. It was a super niche product. That also wasn't even AppEngine, it was just a nice to have, for me, sub-service. There was a point where people were upset about GCP and Google changed their whole deprecation policies to be more vocal and longer term about things. I really don't understand your point. What's the big deal?
  - fhoffa 3y ago
    You think we are disagreeing, meanwhile I just love how much I've learned (and confirmed) thanks to your replies. Thanks for sharing!