News for hackers. Stuff that matters.
Re:Ask HN: What stack would you use to build a CRUD web app ... by userbinator on Wednesday September 30, 2015 @07:08AM (#10303030)
It doesn't change my impression much if the answer to "lots of boilerplate" is to use another tool to generate it automatically...
Re:Ask HN: What stack would you use to build a CRUD web app ... by jeremyjh on Wednesday September 30, 2015 @07:55AM (#10303230)
Actually the example I was thinking of is the finder methods which require only an interface definition conforming to a naming convention. Bytecode is generated at runtime - there is no generated source to manage.

Not much of what Jhipster generates could be considered boilerplate - the application code is pretty DRY. I've used Rails off and on since 2005 and it is fairly comparable in that respect at this point though Java is more verbose of course.

Re:Ask HN: What stack would you use to build a CRUD web app ... by mercurial on Wednesday September 30, 2015 @01:42PM (#10305689)
It's difficult to take Spring seriously after trying Jersey. Resource traversal is a powerful concept. Also, recent or not, Spring still comes with way too much complexity and magic. I'd really go for something more Sinatra/Flask-like. Haven't tried Dropwizard, but from what I saw it looks a lot more sane.
Re:Ask HN: What stack would you use to build a CRUD web app ... by jacques_chester on Wednesday September 30, 2015 @03:23PM (#10306405)
> It's difficult to take Spring seriously after trying Jersey

I'm using Spring Data REST at work. We have a dozen endpoints. We've had to write code for one of them.

The rest were generated by introspecting our models. Complete with HATEOAS links, sorting, searching, paging and HAL. It made a whole bunch of work simply disappear -- even compared to Rails.