4 ms·
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
by antelopesalad 13y ago
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.
- rbanffy 13y agoSo, this is your first access to Hacker News? Why should I believe it? BTW, an SSD would be much cheaper than paying for someone else to solve your problems.
- antelopesalad 13y agoI 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 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.