7/30/2023 0 Comments Reactxp and webpack dev serverI turned down a job offer managing a Rails site because frankly I'm tired of trying to find Rails devs. It's easier, more affordable, and less time consuming to find developers with decent HTML5/CSS3/JS then it is to find dev's competent in the latest thing your senior dev is enthralled by. If your site has a rotating team of developers, I'd say start with the LAMP stack and go from there. You want a "simple" site made from node/react? You've already raised your technical requirements higher then they might need to be. If its a small org, or a company that basically just has a brochure site, all of these answers are huge overkill. The problem I have with most, if not all, of these answers is that they seem to be good choices for orgs that have a dedicated development team. Play 2.7 will be released soon, containing many nice enhancements and fixing many hickups (for Java users at least). We run major projects in production written entirely in Play Java. Back in the early Play 2.x days some features/components of the framework where usable only via Scala, meaning you had to write Scala code to make use of them, however these days are long gone. Yes, Play is written mainly is Scala (69% according to GitHub stats) however as a framework user you can choose between Java or Scala. There seems to be this wrong assumption that Play is a Scala only framework - which is wrong. However I try to look at other frameworks every now and then (Spring, Django) but I always come back to Play, because it just feels more "right" to me.īTW: You can use Play without Scala, but Java only. Using it for many years already, that's probably why I am most productive in it. Same here: Playframework for backend - but using Java instead of Scala.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |