Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 4.0

djangoproject.com

Post reply on HN
Print view View original

161–170 of 226 posts

Re: Django 4.0

#161

Post by akulbe »

rlawson wrote: post #45

Django has allowed me to enjoy some side entrepreneurship. I have released three products as a solo part time dev that I would never have been able to do in a reasonable time using Java/Spring (my strongest stack). My first project went nowhere, but the second generated 1k+ a month and sold for 50k, and the third one is following a similar trajectory. My advice - keep it simple - function based views - centralize acc…

The one that you sold… what made you decide to sell, if it was a money maker for you?

Re: Django 4.0

#162

Post by slig »

skinkestek wrote: post #70
matsemann wrote: post #66

Earlier quoted context omitted.

Another classic is "c string".

Another classic was (I haven't tested recently) that while Firefox would search if you entered a word that was not an address into the adress bar, while certain older browsers, at least Safari just added .com :-/

I remember that, specifically Python dot com. (was NSFW back in the day, enter at your own risk).

Re: Django 4.0

#163

Post by rlawson »

anoojb wrote: post #100
rlawson wrote: post #45

Django has allowed me to enjoy some side entrepreneurship. I have released three products as a solo part time dev that I would never have been able to do in a reasonable time using Java/Spring (my strongest stack). My first project went nowhere, but the second generated 1k+ a month and sold for 50k, and the third one is following a similar trajectory. My advice - keep it simple - function based views - centralize acc…

I’ve found managed databases to be quite expensive at places like Azure and AWS. Especially compared to just installing pgsql on raw compute. What managed databases do you recommend that adequately meet price/performance needs of indie developers?

RDS - Aurora/Postgres flavor - small instance. Entire AWS bill was - WAF rules

- EC2 instance

- RDS

- Cloudfront

I use fargate when deploying now to get out of box management

Re: Django 4.0

#164

Post by holler »

Majestic121 wrote: post #14

We went all in on FastAPI with my team, but we're hit the issue that the projects of Tiangolo (FastAPI, SQLModel, Typer) seem to be turning pretty much unmaintained : https://github.com/tiangolo/fastapi/discussions/3970 We've already been hit by multiple bugs with fixing PR opened, but left to rot, and missing documentation : the 'tutorial' documentation is great, but if you want a reference you have to go read the c…

Have you considered moving to Starlette a la carte? I use marshmallow for schemas and a few other minimal deps and it's been a breeze.

Re: Django 4.0

#165

Post by rlawson »

kaba0 wrote: post #145
rlawson wrote: post #45

Django has allowed me to enjoy some side entrepreneurship. I have released three products as a solo part time dev that I would never have been able to do in a reasonable time using Java/Spring (my strongest stack). My first project went nowhere, but the second generated 1k+ a month and sold for 50k, and the third one is following a similar trajectory. My advice - keep it simple - function based views - centralize acc…

I’m sorry but I don’t buy that. Spring Boot is very highly productive — I really don’t believe any other stack would fare better by a significant margin.

Fair enough, I'm just a datapoint of one. YMMV

Re: Django 4.0

#166

Post by Daishiman »

kaba0 wrote: post #145
rlawson wrote: post #45

Django has allowed me to enjoy some side entrepreneurship. I have released three products as a solo part time dev that I would never have been able to do in a reasonable time using Java/Spring (my strongest stack). My first project went nowhere, but the second generated 1k+ a month and sold for 50k, and the third one is following a similar trajectory. My advice - keep it simple - function based views - centralize acc…

I’m sorry but I don’t buy that. Spring Boot is very highly productive — I really don’t believe any other stack would fare better by a significant margin.

You have to type and read a lot more code in Spring to get equivalent functionality.

Also, and it's hard to believe, but Spring has substantially more magic than Django.

Re: Django 4.0

#167

Post by nojs »

matsemann wrote: post #66
nisegami wrote: post #55

Earlier quoted context omitted.

>avoid fat models, use a service layer I had not heard the term "fat models" before so I googled it. It did not go in the direction I expected.

Another classic is "c string".

I remember studying fork/exec at uni and having some awkward queries involving “fork”, “kill” and “child”.

Re: Django 4.0

#168

Post by strzibny »

robomartin wrote: post #115

Love Django, yet the transition from local development to deployment, in my opinion, continues to be just plain ugly and painful. I've written about this before. I think the stock Django dev configuration needs to change to something that is equivalent to a reasonable deployment on a common VPS, whatever that means. The development server is a nice trick, but the things you have to do to move to a real server are pai…

What do you find hard in particular?

systemd service + gunicorn is not that bad, I think. You can have simple deployment and graceful restarts[0].

[0] https://nts.strzibny.name/gunicorn-graceful-restarts/

Re: Django 4.0

#169

Post by barrenko »

Toutouxc wrote: post #83
barrenko wrote: post #63

Earlier quoted context omitted.

As someone who knows some Python, and "gets" Django / Flask basics, what would my timeline look like for switch to Ruby / Rails? Thanks.

One day of learning the slightly more interesting Ruby syntax, one day of learning how each thing is called in the other framework, and then a few weeks until your code in Ruby stops looking like Python (i.e. you start using the fancy Ruby stuff).

Appreciate it!

Re: Django 4.0

#170

Post by Daishiman »

marcus_cemes wrote: post #92

Does anyone know how Python/Django compares to something like Elixir/Phoenix?

Django has more features, a _much_ larger ecosystem, excellent documentation.

Elixir is dramatically more performant and will scale better. A lot of people enjoy Elixir more or find it conceptually more interesting than Python.

IMO the number of packages and facilities provided by Django will outweigh Phoenix's performance for 95% of users.

Post reply on HN