Nader Jafari 5 Years Ago Hi David thank you for sharing this usefull information and your experience in liferay. but I'm a bit confused after read the section of "What Framework Should We Use to Develop Portlets?". Why liferay developer team use Soy/MetalJS+Clay in own projects like "Liferay Commerce" , if MVC+OSGI portlets and Senna.js will give me same features? Please sign in to reply. Reply as... Cancel David H Nebinger Nader Jafari 5 Years Ago - Edited So while I don't know for certain, I can offer some guesses... First, I think the team put together to build commerce knew that they were going to be front end heavy and probably had front end resources assigned, so their focus was probably on front end design from the get go. Second, Liferay loves to eat their own dog food. To that end they are often looking for ways to fit together many of the things they've created, and soy/metaljs+clay with commerce was a way to do that. Finally, as I said in the beginning of the thread, these are mostly my opinion. I'm glad they used soy/metaljs because I think commerce turned out really well. Myself, I wouldn't have chosen soy/metaljs because I don't know how long it will be around. I come from Liferay 4+Prototype, Liferay 5+JQuery, Liferay 6+AUI and now Liferay 7+MetalJS. That's just too much change for me; if I had to build portlets in Javascript, I'd rather build on something that had legs like Angular or React or even good ole JQuery. But that's just me... Please sign in to reply. Reply as... Cancel Nader Jafari David H Nebinger 5 Years Ago Thank you again David. you are really expert in liferay with more experience and we KNOW so your recommendations is valuable for us :) we are choosing a framework to use in liferay 7 and migrate a lot of MVC portlets that developed in liferay 6. if we choose wrong, it is very costly to change it. Please sign in to reply. Reply as... Cancel David H Nebinger Nader Jafari 5 Years Ago - Edited Upgrades are a different story from new development, my friend. For upgrades, I always advocate doing the absolute minimum to complete the upgrade; if you have Liferay 6 MVC portlet wars, after the upgrade you'll have Liferay 7 MVC portlet wars. Only for new development do you take the opportunity to pursue other options. If you treat an "upgrade" as a "rewrite", you are absolutely going to take on more than you're prepared to chew, and the risk of project "failure" (over schedule, over budget, etc) increases significantly. Please sign in to reply. Reply as... Cancel
David H Nebinger Nader Jafari 5 Years Ago - Edited So while I don't know for certain, I can offer some guesses... First, I think the team put together to build commerce knew that they were going to be front end heavy and probably had front end resources assigned, so their focus was probably on front end design from the get go. Second, Liferay loves to eat their own dog food. To that end they are often looking for ways to fit together many of the things they've created, and soy/metaljs+clay with commerce was a way to do that. Finally, as I said in the beginning of the thread, these are mostly my opinion. I'm glad they used soy/metaljs because I think commerce turned out really well. Myself, I wouldn't have chosen soy/metaljs because I don't know how long it will be around. I come from Liferay 4+Prototype, Liferay 5+JQuery, Liferay 6+AUI and now Liferay 7+MetalJS. That's just too much change for me; if I had to build portlets in Javascript, I'd rather build on something that had legs like Angular or React or even good ole JQuery. But that's just me... Please sign in to reply. Reply as... Cancel Nader Jafari David H Nebinger 5 Years Ago Thank you again David. you are really expert in liferay with more experience and we KNOW so your recommendations is valuable for us :) we are choosing a framework to use in liferay 7 and migrate a lot of MVC portlets that developed in liferay 6. if we choose wrong, it is very costly to change it. Please sign in to reply. Reply as... Cancel David H Nebinger Nader Jafari 5 Years Ago - Edited Upgrades are a different story from new development, my friend. For upgrades, I always advocate doing the absolute minimum to complete the upgrade; if you have Liferay 6 MVC portlet wars, after the upgrade you'll have Liferay 7 MVC portlet wars. Only for new development do you take the opportunity to pursue other options. If you treat an "upgrade" as a "rewrite", you are absolutely going to take on more than you're prepared to chew, and the risk of project "failure" (over schedule, over budget, etc) increases significantly. Please sign in to reply. Reply as... Cancel
Nader Jafari David H Nebinger 5 Years Ago Thank you again David. you are really expert in liferay with more experience and we KNOW so your recommendations is valuable for us :) we are choosing a framework to use in liferay 7 and migrate a lot of MVC portlets that developed in liferay 6. if we choose wrong, it is very costly to change it. Please sign in to reply. Reply as... Cancel David H Nebinger Nader Jafari 5 Years Ago - Edited Upgrades are a different story from new development, my friend. For upgrades, I always advocate doing the absolute minimum to complete the upgrade; if you have Liferay 6 MVC portlet wars, after the upgrade you'll have Liferay 7 MVC portlet wars. Only for new development do you take the opportunity to pursue other options. If you treat an "upgrade" as a "rewrite", you are absolutely going to take on more than you're prepared to chew, and the risk of project "failure" (over schedule, over budget, etc) increases significantly. Please sign in to reply. Reply as... Cancel
David H Nebinger Nader Jafari 5 Years Ago - Edited Upgrades are a different story from new development, my friend. For upgrades, I always advocate doing the absolute minimum to complete the upgrade; if you have Liferay 6 MVC portlet wars, after the upgrade you'll have Liferay 7 MVC portlet wars. Only for new development do you take the opportunity to pursue other options. If you treat an "upgrade" as a "rewrite", you are absolutely going to take on more than you're prepared to chew, and the risk of project "failure" (over schedule, over budget, etc) increases significantly. Please sign in to reply. Reply as... Cancel
Konrad Szeromski 5 Years Ago Definitely "must-read" for everyone who has something to do with Liferay. Thanks David for sharing Your knowledge and experience! Please sign in to reply. Reply as... Cancel
Geert van der Ploeg 4 Years Ago Hi, just a quick fix re. Timezones: you talk about UDT but I suppose you mean UTC? Please sign in to reply. Reply as... Cancel
Geert van der Ploeg 4 Years Ago Hi David. Thanks for your bold statements, I like them more than the general 'it depends' escapes... One quick fix: with regards to Timezones you talk about UDT but I suppose you meant UTC. Please sign in to reply. Reply as... Cancel David H Nebinger Geert van der Ploeg 4 Years Ago Great catch, Geert, I didn't realize that I had done that. Updated the references to be the correct UTC... Please sign in to reply. Reply as... Cancel
David H Nebinger Geert van der Ploeg 4 Years Ago Great catch, Geert, I didn't realize that I had done that. Updated the references to be the correct UTC... Please sign in to reply. Reply as... Cancel