Spring with Spring Boot in Java. Batteries included and easy to setup and get going. A statically typed language to catch errors at compile time. Easy to deploy by building an uberjar. Great dependency management and builds with Gradle/Maven and built-in support for pretty much any common database and message queue.
Ask HN: What web framework do you use? Why did you choose it?
21–30 of 122 posts
Re: Ask HN: What web framework do you use? Why did you choose it?
#22Anyone using an asynchronous python library? Interested in how that's shaping up.
Re: Ask HN: What web framework do you use? Why did you choose it?
#23Back-end: Node.js + Express + ws + Johnny-Five
Front-end: Bootstrap + (Three.js or Snap.svg) + ws
I create browser-based interactive UIs for controlling Arduino robots. I like to keep the web stack as simple as possible because the tricky/hard parts are in the robotics layer.
Re: Ask HN: What web framework do you use? Why did you choose it?
#24Spring Framework on backend -> ultra power and speed, especially if you go cloud and microservices route
Angular 1 on fronted -> easy enough to learn quickly, feels good to use and is powerful with great support and add-ons. Looking to start learning angular2
Will learn elixir and phoenix for some realtime and websocket stuff.
Re: Ask HN: What web framework do you use? Why did you choose it?
#25Merry christmas! For me it's Django for around 5 years. I use it for both personal and work projects for all the following reasons (they are well known but repetition is never bad): * A great (really great) orm * Best documentation I've ever seen in a project * Predictable, no magic * Easy to start but very powerful forms * Great community, positive attitude, always willing to help * Batteries included and, for anyth…
I've never developed using Django. How does it compare to Wordpress? Or under what situation is it preferable to Wordpress?
Re: Ask HN: What web framework do you use? Why did you choose it?
#26Django, because:
* Very little magic in the core.
* Well architected and loosely coupled (in spite of its sometimes-rep it's not actually monolithic: http://olifante.blogs.com/covil/2010/04/minimal-django.html)
* Largest/most solid ecosystem of 3rd party packages (except possibly rails) that does everything from authentication, CMS, CRM, ecommerce, comments, anti-spam, caching, REST APIs, file uploads, admin, emails, authorization, regular authentication, social media authentication, admin plugins, data import/export plugins, etc. etc. etc. meaning that there's an awful lot of code that you don't have to write.
* An opinionated core which means consistency which means that those 3rd party packages that all use caching, ORM, admin forms, etc. fit together and you don't have stuff like CMS plugins that just decided to use mongo for the hell of it (http://quokkaproject.org/) or 3rd party plugins forced to support 3 or more different storage backends (https://pythonhosted.org/Flask-Security/).
* Python is a terse and readable language with (relatively) strict runtime type checking and a huge ecosystem outside of just web stuff.
Re: Ask HN: What web framework do you use? Why did you choose it?
#27Re: Ask HN: What web framework do you use? Why did you choose it?
#28[deleted]
Re: Ask HN: What web framework do you use? Why did you choose it?
#29Merry christmas! For me it's Django for around 5 years. I use it for both personal and work projects for all the following reasons (they are well known but repetition is never bad): * A great (really great) orm * Best documentation I've ever seen in a project * Predictable, no magic * Easy to start but very powerful forms * Great community, positive attitude, always willing to help * Batteries included and, for anyth…
I've never developed using Django. How does it compare to Wordpress? Or under what situation is it preferable to Wordpress?
But you cant compare Wordpress with Django, Wordpress is not a web framework is just a CMS for blogs.
Or am i wrong?
PS... Django <3
Re: Ask HN: What web framework do you use? Why did you choose it?
#30I'm pretty sure I'll be minority here, but I don't use any backend framework for page rendering. All my apps are pure SPAs. They render all the screen content themselves on the client and only query servers for data. I prefer this, because I can simply take any app and deploy it to server just by copying its files. I only need to scale API servers and I don't have think about app scaling, because just single instance of nginx with proper caching setup can handle hundred thousands of clients (serving static resources is cheap and fast). Also you can take same app, package it as cordova and deploy to app/play store (although this can be probably achieved with any other frameworks as well). On the frontend I use combo of react, redux, redux-saga ...
Before I've used backbone, but react with redux is night and day difference. Even you're just starting with js, your apps will be less error prone, because of concept unidirectional flow.
Maybe this is no longer special to react/redux, but I'm really not in the age I can switch frameworks everytime some new stack arrive. React serves me well. And then, there is also react-native, which is 90% same as react so you can reuse what you have learned. Other frameworks don't have this close to native counterpart. (not counting cordova, which allows to use any fw, but performance will never be same as react-native).