tbatterii

Actually a MTV framework https://docs.djangoproject.com/en/1.8/faq/general/#django-ap...

The title of the submission is "Do not use IDEs".

But the page title of the submission it actually links to is "Exercise 0: The Setup:"

I think whoever posted this on HN was purposely taking things out of context for controversial lulz.

there was a need for this? yet somehow reader had to die?

ironically one of the reasons i've entertained the idea of quitting twitter is b/c of annoying things that showed up in my feed from the author(and others). But I just un-followed him instead. the technical things I'm interested in, but I dont care for the politics so much.

great advice here, I would have liked to see some code examples for #4, b/c I am currently struggling with a ng codebase where the controller are doing way too much in my opinion. using ui-router helps some, but, I would love to see more ways to keep the controllers slim.

Yep, for under 2K that w540 would be awesome. I had the previous version and it was probably my favorite laptop ever, ran linux like a champ.

how about one command...

$ /path/to/virtualenv/bin/python run.py

i was reminded of this video regarding polls. tldw: they are bullshit. http://youtu.be/If9EWDB_zK4

"stake holder" is not mentioned once in this article. PM tools, help with the communication that leads to trust between the doers, and those putting the cash up for it. it's either use PM tools, or suffer micro management hell and lack of focus until the $$ runs out.

I can sort of empathize, with having too much focus on the planning/pm process, I've been there, done that, it's a potential problem. But not a reason to disregard the tools or the need for them.

There's flaws in accounting processes too, but I believe sane people would all agree that accounting processes are needed.

If there are problems in the way you are measuring, deciding that measuring is bad is just silly.

getting rid of regex based routing would make it even simpler.

boycott javascript as well?

I was curious myself, and found this. http://www.un.org/en/documents/udhr/

Article 16.

(1) Men and women of full age, without any limitation due to race, nationality or religion, have the right to marry and to found a family. They are entitled to equal rights as to marriage, during marriage and at its dissolution. (2) Marriage shall be entered into only with the free and full consent of the intending spouses. (3) The family is the natural and fundamental group unit of society and is entitled to protection by society and the State.

It seems the UN is against gay marriage so that's where the next witch hunt should go

that sounds about right. I wasn't thinking about it from the technical end. I was just speculating the business angle.

my $$ is on a node runtime, assuming google is interested in increasing the # of people that use it. python 3 would be nice but it probably wont get people interested like node would.

new async framework landing in 3.4 is very exciting

this is the killer feature that would move me to python 3. alas, not released yet. And I took a rails job :(

I believe there is a plugin for working with the App engine.

You believe it, I tried it, and it failed, the non-rel project isn't even under active development anymore. And if appengine had not introduced cloudsql as an option, django would be useless on that platform.(IMO)

And also Django is modular enough that you only need to use the parts you require.

As I said before, without the django orm, there's not much useful stuff left in django that will work without it. There's better request routing options than regex based IMO. There's better form libs and validation libs. There are certainly better performing template engines, what is left of django that's a better choice over something else?

a) They will play nicely together.

depends

b) There will be consistencies between the libraries.

depends

c) Magic things like the Amdin interface will work.

true

the workflow for this particular project seemed to go like this...

* get requirement from client * search google for plugins/modules/etc * choose some * try to get them to work * use them or fork them or find others

which to me seems a pretty roundabout way of getting something accomplished if you already know what needs to be done. it doesn't feel like programming, it feels to me like assembling things and testing/hoping there are no issues. I'd rather be programming.

i just finished up a django project that also had "8 million" dependencies, the difference was a lot of them started with "django-" and some dependencies I would have liked to use were off the table.

five years ago in Python you put together a lot of small pieces (and e.g. Turbogears was a nominal framework that was actually a lot of small libraries being composed together).

I loved those days. :)

there's middle ground between something heavy like django and CGI/WSGI, I think they are called micro frameworks.

bigger frameworks like django tend to get in your way for anything that the framework was not intended for. not every web app is a "fetch content from db and display to users"

try doing something workflow heavy on appengine with datastore. The django orm wont work for datastore, so what you are left with out of the framework is regex based routing(ewww) and a bunch of crippled components(meaning depending on an orm you can't use).

django has it's place dont get me wrong, i would use it to quickly squeeze out internal db backed apps all day. maybe even use it as a cms. But i'd rather not do those kinds of projects at all.

not in my experience. i put id3 tags from ~32K songs in it and a query for an artist was around 700ms. same query in ES was like 10ms, same qry to sqlite db (select * from track where artist=...) was about the same as ES. the docs for whoosh make these claims that it's fast, but I haven't seen anything to backup the claims in unit tests or otherwise. I'm sure it's still useful for some purposes but ES is so easy to setup that I don't bother.

I read all that, I was more interested in information on the "eggs are dead" assertion.

I don't know much about the wheel format. But eggs being dead is news to me. You have links for those interested in more info?

i think you are confusing virtualenv with pyvenv which is what came with python 3.3 http://www.python.org/dev/peps/pep-0405/

when virtualenv was released with python 3.3 it didnt come with pip.

a flavor of virtualenv was bundled in 3.3 (http://www.python.org/download/releases/3.3.0/) but without pip or easy_install it was a pretty useless feature IMO.

I notice the author of this article is ceo of a company that sells personal and group productivity products and services. http://timebackmanagement.com/

org-mode works for me.

The decision of when to merge vs. rebase is still confusing to me.

i always thought it was "never rebase commits you have pushed" at least you know about rebase though. :)

prior to asp.net mvc or those master page things, every asp.net project I ever worked on eventually had a base webform which was the dumping ground for everything and thus nightmarish to comprehend or maintain. Django's CBV's remind me of that nightmare and I tend to avoid them because it feels like reinventing a poorly designed wheel with no real value.

I occasionally see comments on threads claiming they are the best thing since sliced bread, but rarely can anyone back it up convincingly.

So, to me they feel like a fad, and should be avoided IMO.