I've experienced a variety of results between switching between a dynamic and static types languages I think a lot of it has to do with context.
IMHO there's a certain rhythm to developing on any specific platform. Where using a certain set of technologies make more sense than others. Since everything in Sling is built on Java and you'll be dealing with Java API's, from a business logic perspective, I think you'll get the best results from writing that part In Java. I highly recommend the Sling Models as the starting point for that. >From the view perspective, which I'm using to identify that initial end point >service you're calling I don't think it matters as much, although I haven't >heard of a lot of people using ecma. I prefer to stick with JSPs since that's >what everything boils down to underneath anyways, sticking an abstraction >layer over it has always struck me as kind of wasteful. ________________________________________ From: lancedolan <lance.do...@gmail.com> Sent: Wednesday, January 11, 2017 4:41 PM To: users@sling.apache.org Subject: RE: JS Use API usability or limitations No architectural reason - purely speed of development reasons. Our team has switched from Java to Node.js on our other projects and are seeing real gains in dev time. We believe we could see the same faster development with lightweight JS files as opposed to traditional type-safe Java. I think this is a popular opinion amongst developers, that JS is faster to write in than Java? The question currently on the table is whether the difficulty in debugging esoteric Rhino interactions will negate that speed, in which case we might as well stick to Java and enjoy stability of type safety. -- View this message in context: http://apache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490p4069526.html Sent from the Sling - Users mailing list archive at Nabble.com.
