Live data from Hacker News

Django 2.1 released

docs.djangoproject.com

91–100 of 129 posts

Re: Django 2.1 released

#91

Are there any good reads on Django for former Rails devs? I'm learning Django now and interested for the "translation".

I am the same. Not because I want to stop using Rails (I <3 Rails), but rather just to increase my repertoire. Let me know if you find something!

Re: Django 2.1 released

#92

Can anyone recommend a framework like Django except for a static language? I tried Django and really liked what I saw, but I can't see myself using Python for a large project.

There's been some work to add type-hinting to Django if that helps.

Check out:

https://github.com/TypedDjango/django-stubs#django-stubs

https://gitter.im/mypy-django/Lobby

Re: Django 2.1 released

#93
post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

Another point: websockets. Golang is pretty good and (they say) Django kinda sucks. Have you used Django channels?

Re: Django 2.1 released

#94
post #93
post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

Another point: websockets. Golang is pretty good and (they say) Django kinda sucks. Have you used Django channels?

I have and it works but they completely revamped the implementation in 2.0. I'm procrastinating the upgrade because it is a royal pain.

Re: Django 2.1 released

#95
post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

At work because I have lately needed to roll web server/api/admin/client apps (embellished CRUD situations with some other serverside processing to generate user output) and for those my go to for dev speed, platform speed, familiarity, and a few other concerns I generally go with Node/Express/TypeScript and it's great to work with. However for my personal site I used Django to give it a shot. Once I wrapped my head…

I just use plain text-areas and markdown - it avoids a lot of footguns from text-editor-like widgets.

Re: Django 2.1 released

#96
post #6

Read-only model views are a great addition to the Django admin -- I've been watching that PR for a long time, glad to see it land. This will make it a lot easier to build internal admin dashboards that are safe to share with non-privileged users like support staff.

I've been looking forward to this as well. A lot of developers underestimate the time it takes to build CMS and resource dashboards (even small ones).

Re: Django 2.1 released

#97

Earlier quoted context omitted.

Why would anyone consider it obsolete to begin with ? If anything, I would consider someone making that statement miss informed

There are not currently many well-known products that use it. (Bitbucket cloud being the exception.) That's not the best of reasons; just because Django is not used by Google doesn't mean it isn't the perfect tool for you.

IIRC, I had read that Disqus uses Django, and that they were one of the biggest Django sites on the net, but that was a while earlier. Not sure about now.

Update: Just saw that HN user txcwpalpha said the same about Disqus in sibling comment.

Re: Django 2.1 released

#98
post #61

Earlier quoted context omitted.

A huge reason some people consider frameworks like Django obsolete is because they are focused on an older web paradigm of constructing elaborate html pages on the server side and pushing it out and letting some basic extra js stuff augment it. That's what lead to things like server side HTML form definition and form handling code. After the emergence of things like React, Angular, etc those "html templating" facilit…

Not true. django-rest-framework is so well adopted and widespread and it lets you very quickly put together a REST service. If you just want to talk json/xml/whatever with your client, it is easy. But the really cool thing about DRF is how it simply generalizes some of the concepts that already existed in in Django. If you started in Django and learned about Form and ModelForm, you can easily pick up DRF Serializers…

>it could not succumb to CADT.

I had to look up CADT.

Got this via Google:

CADT stands for Cascade of Attention-Deficit Teenagers

Re: Django 2.1 released

#99
post #61
post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

A huge reason some people consider frameworks like Django obsolete is because they are focused on an older web paradigm of constructing elaborate html pages on the server side and pushing it out and letting some basic extra js stuff augment it. That's what lead to things like server side HTML form definition and form handling code. After the emergence of things like React, Angular, etc those "html templating" facilit…

It seems you are confusing (conflating?) web pages with web app.

>...constructing elaborate html pages on the server side and pushing it out and letting some basic extra js stuff augment it.

I will take server side rendered webpage up against a fancy js spewed template any day of the week. In every metric possible the server side render wins.

Load speed, SEO, accessibility, file size, time to paint, time to render, time to interactivity. Not a single point goes towards the js rendered web page, period.

In fact, it has almost every conceivable downside, including the obvious, it requires javascript.

I develop webapps for a living, and I hate using them for browsing content, they suck for that. Vue.js/React/Angular for web apps all the way, for web pages/content, server side hands React its behind.

Re: Django 2.1 released

#100
post #84

Earlier quoted context omitted.

> because they are focused on an older web paradigm Which usually is faster and easier to use. > A modern fancy web application using React in 2018 Takes ages to load and melts your CPU.

One wonders if the web would be a better place if developers used machines and networks slower than their users'.

Heh well I'm trying to explain my customers that the load times I'm experiencing could be similar to their users and might be a problem. One of the advantages of being a remote developer with a pedestrian SDSL connection.
Post reply on HN