2) Not at all. But you need seasoned developers.
3) Our platform runs mostly in Java. So far good performance.
161–164 of 164 posts
2) Not at all. But you need seasoned developers.
3) Our platform runs mostly in Java. So far good performance.
I'll give you my take on this as a Java programmer of 10+ years experience. The problem you will have with Java in a startup is that Java's frameworks are by and large built for "enterprises". I put that in quotes because in one sense it doesn't really mean anything. In another, it's more of an idea of what governments and large companies want. Even when using Spring (which, in my opinion, is a "must have" for pretty…
Sorry, I have to call you out on this. In your list above PHP is really interchangable with Python, Ruby, etc (the scripted languages). The MVC architecture you mention above perfectly describes Rails. So I have to ask, are you seriously saying that Rails is horrific? Seriously?
Earlier quoted context omitted.
I think one major difference/hurdle of java web development and deployment is the fact that you HAVE to setup something like nginx in front of the app server or else you're working on port 8080 for everything. Or you have to know how to configure the app server for port 80 directly and mitigate the security concerns of doing so. By comparison, apache defaults to port 80, no tricks required.
changing the port of an app/web server z no big deal..if u really wanna deploy something.
Earlier quoted context omitted.
I think one major difference/hurdle of java web development and deployment is the fact that you HAVE to setup something like nginx in front of the app server or else you're working on port 8080 for everything. Or you have to know how to configure the app server for port 80 directly and mitigate the security concerns of doing so. By comparison, apache defaults to port 80, no tricks required.
If one is unable to change the port from its default, one doesn't have any business in developing web apps in any technology. Just sayin'.