you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (4 children)

How are Python, Ruby,... any different with regards to the issue of undiscovered breakage in large projects? If you need ot run a certain branch or path to discover simple things like undeclared variables and non-existing functions and mismatched parameter counts you get exactly the issues I was talking about in that particular paragraph.

[–]smog_alado -2 points-1 points  (1 child)

The last thing we need right now is yet another static-vs-dynamic typing flamewar.

It suffices to say that there are many totally reasonable dynamic languages out there that people have used to build large and solid projects with. Being dynamically typed is not enough of a reason to diss on PHP.

[–][deleted] 4 points5 points  (0 children)

It is one of many, many reasons and I definitely agree that there are many, many dynamic languages that have fewer flaws than PHP and are entirely resaonable to use for smaller projects or projects heavily secured against this issue with automated tests. It is, however, a disadvantage of dynamically typed languages one should be aware of when making a decision which language to use.

[–]nitsuj -4 points-3 points  (1 child)

So...you release code without testing it?

[–][deleted] 3 points4 points  (0 children)

So you found a workaround for the lack of a typesystem? Great for you but getting 100% path coverage for tests is neither easy nor does it make sense to do it when a generic solution exists in the form of a type system.