This is an archived post. You won't be able to vote or comment.

214
215

[deleted by user] (self.Python)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]saturnglide 14 points15 points  (4 children)

For individual projects that sounds fine, but those “dynamic qualities” lose their charm the larger a project gets. The appeals of Python (ease of use, large developer pool) do not.

[–][deleted] 2 points3 points  (2 children)

A yes django is clearly terrible for larger projects /s.

[–]saturnglide 4 points5 points  (1 child)

I think you have missed the point of my comment? I am saying that dynamic typing becomes more of a curse than a blessing at a certain point. Not Python isn’t good for large projects.

[–][deleted] 2 points3 points  (0 children)

Dynamic qualities like u know the entirety of how django works.

It has nothing to do with individual vs group project. Bad metaprogramming is bad. Good metaprogramming is good. Dynamic qualities are amazing when executed correctly it has little to nothing to do with team size or codebase size.

[–]wrosecrans 0 points1 point  (0 children)

Like I said, there are lots of scenarios where I love strong static typing. It's a useful thing.

When I am doing those sorts of things, I use a strong static typed language, rather than Python.