Live data from Hacker News

Ask HN: What web framework do you use? Why did you choose it?

news.ycombinator.com

81–90 of 122 posts

Re: Ask HN: What web framework do you use? Why did you choose it?

#81
For us not-so-smart-people who liked MS Access: PHPRunner.

From a programming standpoint, it's the worst thing in the world: A Windows GUI thing that builds PHP apps and it's closed source.

From a get-stuff-done standpoint: I made a tracking web-app for large expensive tools that knows about Customers, Project Locations, Scheduling, Work Orders and Invoicing - it will grab a customer signature and email them the receipt. I did it in about four hours.

It has hooks in the system for those that actually know what they're doing (not me) to embed PHP code at important points.

Re: Ask HN: What web framework do you use? Why did you choose it?

#82

Meteor - It's a fullstack framework that let's you write JavaScript both on the front- and backend. It let's you choose what you want to use for your frontend (e. g. React, Vue, Blaze, Angular...). Best feature: It's realtimeness. And right now I'm trying Laravel (PHP). It has a great documentation. I like the ORM and that it's easy to use. I want to build an API with it and consume it with a SPA and react.

you might want to try lumen(larvel minus view part) created by the same author since you say you want to build API's

I'm curent developing a rest api in Laravel. I tried lumen before switching but configuring just some basic packages to work with lumen (Dingo, JTW) was such an headache that I moved to laravel.

Re: Ask HN: What web framework do you use? Why did you choose it?

#84
Koa 2 with Nunjucks, Sequelize and Typescript. Koa 2 with async/await is a real pleasure to work with and Nunjucks is powerful enough for pretty much every templating need. Sequelize has been a pretty good ORM. Typescript brings the right amount of type safety to catch easy mistakes while typing. Angular 2 for SPA:s.

Re: Ask HN: What web framework do you use? Why did you choose it?

#86
post #7

Merry 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 always been curious as to how you structure your models in Django.

I'm building a personal project in Tornado and MongoExpress, and the only thing I can see about structuring my models is to put all of them in one file called models.py

I'm used to the RoR way of doing things, so this seems very counter-intuitive to me.

In addition, whenever I try to break the classes into different files, I'm not sure of where to store my DB connection logic, and how to ensure that all models are accessible from the controllers.

Ideas?

Re: Ask HN: What web framework do you use? Why did you choose it?

#87
post #7

Merry 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 always been curious as to how you structure your models in Django. I'm building a personal project in Tornado and MongoExpress, and the only thing I can see about structuring my models is to put all of them in one file called models.py I'm used to the RoR way of doing things, so this seems very counter-intuitive to me. In addition, whenever I try to break the classes into different files, I'm not sure of where t…

You can make `models` a package, where `models/__init__.py` just imports models from the package's modules (`models/thingamabobs.py` and ` from .thingamabobs import Thingamabob`).

Also, you shouldn't need to worry about database connection logic in Django unless you're doing something very specific.

Re: Ask HN: What web framework do you use? Why did you choose it?

#88
post #71
post #42

ASP.NET MVC, on .NET Core. It's super fast, C# is mad fun to develop in, and now it runs on Linux. We've even started deploying production sites to CentOS-based VPSes.

Do you self-host them in Linux? Or are you using something like nginx reverse proxy?

We use nginx as a reverse proxy. It was a little bit of a pain to set up with all the SSL stuff at first, especially since we wanted to keep hosting some Wordpress blogs on URLs nested within the .NET infrastructure, but overall it's worked out well now that it's up and running.

Each site gets its own dotnet instance, and for a while I was even running them all within a screen session. It was kinda neat to be able to flip through all of them, and see the dotnet instances at a glance, but now they've got proper startup scripts.

Re: Ask HN: What web framework do you use? Why did you choose it?

#89
post #87

Earlier quoted context omitted.

I've always been curious as to how you structure your models in Django. I'm building a personal project in Tornado and MongoExpress, and the only thing I can see about structuring my models is to put all of them in one file called models.py I'm used to the RoR way of doing things, so this seems very counter-intuitive to me. In addition, whenever I try to break the classes into different files, I'm not sure of where t…

You can make `models` a package, where `models/__init__.py` just imports models from the package's modules (`models/thingamabobs.py` and ` from .thingamabobs import Thingamabob`). Also, you shouldn't need to worry about database connection logic in Django unless you're doing something very specific.

Depending on the situation, I think it's usually better to seperate the models to different apps instead of using a single app with a models.py-package. This way you'll have seperate views, forms, urls, admin, templates etc.

For common functionality (ie an abstract model or a mixin that is used/inherited by multiple models/views) I like to add another django app named common or core that is used by the other apps.

Post reply on HN