News for hackers. Stuff that matters.
Re:The State of Go by user5994461 on Sunday February 05, 2017 @11:51AM (#13573189)
Of course I mean ruby on rails when I say ruby.

Initial release 2005. i.e. Young.

Re:The State of Go by closeparen on Sunday February 05, 2017 @11:58AM (#13573230)
Are you using Struts or something?

How could a 12-year-old framework not be old enough for you?

Re:The State of Go by jankiel on Sunday February 05, 2017 @12:41PM (#13573442)
Ruby on Rails is a web framework, not a language. Also web dev is about shipping a product fast, that's why you don't see Java there.
Re:The State of Go by closeparen on Sunday February 05, 2017 @03:28PM (#13574424)
You do see a ton of Java web apps in in-house and consultant-built line of business applications. Just not so much from product companies.
Re:The State of Go by watwut on Sunday February 05, 2017 @05:27PM (#13575060)
Once you know whatever java framework well enough and your project is not something ruby on rail spits out immediately, shipping fast is not a problem. In 4 months timeframe, you can definitely produce more or as much as with node.js or something like that.

The issue is that you wont do good frontend in it (obviously), java programmers are more expensive, learning it well enough so that you can actually be that fast takes a lot of time and hosting is way more expensive. Learning language itself is easy, but absorbing necessary frameworks takes time. Moreover, people who are good in frontend prefer languages similar to javascript, because they already know it very well so those are easier to learn for them.

I think this is why it does good in enterprise - they have money to throw at hardware, most projects are under huge time pressure constantly and requirements change constantly. Frontend is super important for product, but not so much for enterprise.