> All I have to say is "wow". I'm really glad you're just a troll here and not > actually responsible for anything I depend on.
Let's see... You spend your life complaining how the platform sucks. I release tutorials on how to make it suck less. I'm the troll? Anyone who thinks the low level api is analogous to assembly probably doesn't want to depend on me because the laughter when they asked a question might be deafening. Read EVERY optimization guide on Java for GAE and that is the first thing they tell you to do. If that is too hard, then this is not the platform for you. I have vouchers for Azure, hit me up off list I'll send them along, you will be happier in .Net where you never have to do anything low level. J# is supported for 3 more years... So you should have plenty of time to learn basic principles of cloud development in that time. All animosity aside. I'm sure you are a good Java dev, but this isn't Java. The Python I write isn't Python either. I mean it is, but not how you would write it if you were on a "real" server. You have to get over that. You are going to suck at GAE until you do. NO FRAMEWORKS. NONE. Deal with it. Every email you beat me over the head with why you need PMF. Well Frak PMF it is holding you back. It is making you stupid. You don't need it. If you need it for one really hard thing once in a great while that is what a lazy load is for. Yes classes suck we went over that. Which is why you build micro apps that are purpose built and only use limited classes. Yes I have an F8 that can be anyone of my Micro Apps, it has 63k Entities. It lazy loads. So it doesn't break, It is used for tests and for emergency off loading of traffic. You don't have that kind of traffic so you don't need that, I get that. But you need to get over yourself and look at profiling your app, and determining where you can cut the fat, and how you can break a single monolithic app in to 4 smaller apps. I don't know what that looks like, maybe it is Customer authentication and session handling, Credit card processing and Order insertion, and Product Look up and shipping calculation. In so doing you can limit your classes, you can make better use of your instance memory, and you can likely keep from ever hitting warm ups because each app will run more efficiently than the monolith. Yeah that is a lot of work, and sure it sucks that this guy who called you stupid told you to do it, but it is the right thing to do. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.