News for hackers. Stuff that matters.

antelopesalad

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @06:36PM (#7159933)
I shouldn't have to buy an SSD to develop comfortably with a dynamic language.

Even compiled languages like Go using non-trivial frameworks (Revel) reload faster than django's runserver. It's like django's runserver is still in 2007 while everyone moved on years ago.

I'm also not the only one who isn't happy with the speed because right now runserver polls for updates every second. Some core dev implemented a change so that it's push based now instead of polling every second and should be in 1.7, but this only happens if you have pyinotify.

Want the know the kicker? The ticket to do it was opened 5 YEARS AGO.

https://code.djangoproject.com/ticket/9722

That's only a small gain though but it's crazy to think that it's been polling this whole time. I'm all for polling in web apps when possible but seeing a comment you didn't know even exist pop up 3 seconds after it was made is much different than expecting immediate feedback when you spend ~60 hours a week developing a web app.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @03:17PM (#7158925)
I'm already proficient in rails, it's why I'm so jaded by having an unbelievably good developer experience. I'm not talking about ruby or even the rails API/community/etc. either.

It's just the problems that they address are the problems that matter for people who actually develop web applications full time because the core rails team develops basecamp full time and extracts rails features from their experiences.

The django guys are simply not doing this. I can't put my finger on it exactly but Python calls to me like a siren. It's unfortunate that Django doesn't seem to want to address problems that people have, aren't addressing modern web development problems and are calling out to the community to raise money to introduce features to django's core.

It took me like 3 weeks of hunting down random packages that add certain functionality, forking and fixing libs because the maintainers of those libs hate python 3 and won't support it just to get to the point where django was even usable as a development platform and now after all that I'm stuck having to waste 5 seconds of my life every time I touch a view or model.

Then I have to wait 1.5 seconds for SASS to recompile between page reloads because the django-pipeline author (who is awesome btw) doesn't have the time to make pipeline cache the sass files and only recompile them when they change.

It's one of the more anti-productive environments I've ever developed under and it's a pity because the django API is actually pretty good and I want to give it a chance.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @12:44PM (#7157896)
I don't have the time to audit and analyze the entire django framework and every third party app I touch. I am only using a few apps too that are popular in the community.

Realistically I'm a web app developer who wants to be productive. It's insane that I need to even consider doing that just to not have to wait 5 seconds for runserver to reload in development mode on a trivial app. It should be on the shoulders of the django core team to make sure their platform makes developers happy.

P.S., if you want to give me $100,000 I will quit my job and spend the next half a decade learning advanced python, audit the entire django code. You would probably laugh and call me insane right, but this seems like what the django core devs are forcing us to do because they don't want to address the problems with the framework.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @12:20PM (#7157766)
Except you could go look for yourself on Google and see this is my normal IRC name and if you wanted to read the conversation that sparked this topic since I'm pretty sure the #django IRC logs are public.

You can accuse me of down voting you but you're accusations are misplaced. I wouldn't waste my time. How about you go ask the site owner to check who down voted you.

I will bet my life that it's not associated to my IP address or this account. Go troll someone else man and lay off the insults, it makes you look like you're a child.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @09:57AM (#7156919)
This has nothing to do with production mode.

The development experience is unacceptable with runserver in development mode. I have a trivial app with half a dozen apps and it takes 5 seconds to reload runserver when I touch a view file.

On the same hardware a ~6k SLOCs rails project with 40 gems reloads pretty much instantly because the rails dev server is smart enough to do code swapping.

Edit:

runserver_plus does nothing to make runserver reload faster, it is an improved stack trace with a built in debugger. Since I am already using django-extensions I tried runserver_plus and it added 2 full seconds to each reload.

So now it takes 7 seconds just for runserver_plus to reload after touching a view.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @09:51AM (#7156886)
That's even worse. So the author of south threw out all of his work and re-wrote it from the ground up rather than the core devs just working on it?

That's disgusting...

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @09:50AM (#7156877)
You seem to have a grudge against the world for some reason. Why are your posts so hostile?

Do you not see the bigger picture? The runserver problem is only 1 thing. People are expecting to be fed tens of thousands of dollars through kickstarter to create features that people want instead of the core django devs implementing them.

The reason why rails has an amazing development experience has nothing to do with rail's API or ruby.

It's because rails is extracted and built out of a product that some of the core devs work with 24/7 (basecamp). They add useful things like a development server that isn't garbage because they work with it on a daily basis full time.

I don't want to see Django fall over because they don't add any features that people actually want and instead force the community to beg for money on kick starter to do it.

Re:Has Django become a pay-for-features framework? on Friday January 31, 2014 @08:59AM (#7156623)
That's kind of my point. If there's no love from the core devs to solve real problems that the community has then what are our choices?

Having to throw up kick starters for every feature is unreasonable.

Migrations were something that SO many people wanted and the core devs didn't even think to add it. It had to be merged in by a random person in the community for $30,000 and it also took 14 months assuming Django ships 1.7 in May going by their roadmap.

That is 14 months and $30,000 to get a feature into the framework while already having a tested and battle hardened implementation as a third party module.

Has Django become a pay-for-features framework?

I happened to ask a question on IRC last night to see if it would be possible to improve runserver such that it was able to reload between code changes faster or swap in new code on the fly without reloading.It got a response from Russell Keith-Magee and others who are very skilled with Python/Django.Basically the general census was it's possible but it would be a ton of work. Russell...

( Read More... | 27 comments | 13 points | on HN )