Re: [appengine-java] Can't decide: JDO, Twig-Persist or Objectify?
Twig, Objectify and Slim3 are all open source, so the "one developer" problem is mitigated by the fact that you can fix your own bugs/add your own features. It's no worse than most open source projects. On Mon, Apr 26, 2010 at 9:26 AM, Guillermo Schwarz < guillermo.schw...@gmail.com> wrote: > Hi, > > Why is Twig "only one developer"? > > Cheers, > Guillermo. > > > On Sat, Apr 24, 2010 at 3:04 PM, jbdhl wrote: > >> >> >> * Twig >> Pros: simple, low startup latency >> Cons: only one developer (major drawback), GAE-only >> >> > > -- > Saludos cordiales, > > Guillermo Schwarz > Sun Certified Enterprise Architect > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- Ikai Lan Developer Relations, Google App Engine Twitter: http://twitter.com/ikai Delicious: http://delicious.com/ikailan Google App Engine links: Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Can't decide: JDO, Twig-Persist or Objectify?
Hi, Why is Twig "only one developer"? Cheers, Guillermo. On Sat, Apr 24, 2010 at 3:04 PM, jbdhl wrote: > > > * Twig > Pros: simple, low startup latency > Cons: only one developer (major drawback), GAE-only > > -- Saludos cordiales, Guillermo Schwarz Sun Certified Enterprise Architect -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Can't decide: JDO, Twig-Persist or Objectify?
Hi jbdhl, You can choose Slim3, too. Please see the following tutorial using GWT. http://sites.google.com/site/slim3appengine/getting-started-with-gwt Slim3 supports HOT reloading when you use GWT, too. HOT reloading means new version of a class is automatically reloaded on the fly. Due to HOT reloading, when you change the source code, you can see the changed result on your browser without restarting web application. Yasuo Higa On Sun, Apr 25, 2010 at 4:04 AM, jbdhl wrote: > Hi > > I really can't decide which datastore abstraction to use for my app. > Any help deciding, would be much appreciated! > > The app is build using GWT and there is a lot of one-to-many relations > (so I would value if all children could be automatically deleted if > the parent is deleted). > > So... Which one of JDO, Objectify or Twig-Persist should I use? > > * Twig > Pros: simple, low startup latency > Cons: only one developer (major drawback), GAE-only > > * Objectify > Pros: simple, low startup latency > Cons: slightly more verbose syntax than in Twig, GAE-only > > * JDO > Pros: not GAE-only > Cons: complex, long startup latency > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Can't decide: JDO, Twig-Persist or Objectify?
I like Objectify, but you will find out that using the low level api its the best option due the appengine limitations. 2010/4/24 jbdhl > Hi > > I really can't decide which datastore abstraction to use for my app. > Any help deciding, would be much appreciated! > > The app is build using GWT and there is a lot of one-to-many relations > (so I would value if all children could be automatically deleted if > the parent is deleted). > > So... Which one of JDO, Objectify or Twig-Persist should I use? > > * Twig > Pros: simple, low startup latency > Cons: only one developer (major drawback), GAE-only > > * Objectify > Pros: simple, low startup latency > Cons: slightly more verbose syntax than in Twig, GAE-only > > * JDO > Pros: not GAE-only > Cons: complex, long startup latency > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Can't decide: JDO, Twig-Persist or Objectify?
Hi I really can't decide which datastore abstraction to use for my app. Any help deciding, would be much appreciated! The app is build using GWT and there is a lot of one-to-many relations (so I would value if all children could be automatically deleted if the parent is deleted). So... Which one of JDO, Objectify or Twig-Persist should I use? * Twig Pros: simple, low startup latency Cons: only one developer (major drawback), GAE-only * Objectify Pros: simple, low startup latency Cons: slightly more verbose syntax than in Twig, GAE-only * JDO Pros: not GAE-only Cons: complex, long startup latency -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
