neither did you. in fact, you italicized probably the least objective portion, that of staically typed languages being more readable. and that's likely to be the opposite case for most people. the draw for most dymaically typed languages is that they are often quite readable.

sometimes people prefer different stuff, and that's all the commenter was saying. i myself like both.

A really big and complex program, is right now doing airline planning for over 800 companies, taking into account 4000 airports. To get an idea of the complexity look at this pdf:

http://www.demarcken.org/carl/papers/ITA-software-travel-com...

Both examples are software programmed in a dynamically typed language, Common Lisp.

And in that highly dynamic language, should any bug appear in production, it can be patched without stopping the system and of course without having to recompile the whole code. This bears repeating:

The system can be patched without stopping it and of course without having to recompile the whole code. That is, patched at runtime by correcting the offending function and re-attaching the new version of that function to the running system.

Try doing that with your favorite statically-typed language.

Your arguments are just common beliefs of the typical developer who is lacking more experience in the field of developing real-world systems. You are just regurgitating common myths, and in the process, calling "fucked up mentally" people probably wiser (more experienced and learned) than you.

And BTW,

If you think all dynamic languages are equal to javascript, which is not only dynamically typed but also weakly typed, then you need to try more dynamic languages. For example strongly typed dynamic languages.

I wish i had $1 everytime a developer mixes up "dynamic typing" with "weak typing"

This is not a necessary feature of dynamic languages; some have proper object systems with class declarations.

Dynamic languages can contain crap design decisions, like using functions to simulate objects and classes, and that will reflect badly on the programs.

Most of your argument is emotional and anecdotal, and what remains is only a compelling argument for code quality, not static/dynamic.

I, too, have worked in large code bases in both static and dynamic languages, and generally, I found the latter was a far better experience than the former - but code quality trumped any static/dynamic effect.

Even in just terms of reading and understanding what was going on, it was generally far more challenging to understand the point of code blocks due to boilerplate to deal with typing; indirection through wrapper classes in particular. A function might take an object foo, which would typically be on some level on an inheritance tree, and you'd have to trace up and down both the tree and the call stack in order to understand, and discard more than half the characters to get to the logical meat. Pure hell on development - the absence of REPL consoles means you really can't explore what's actually going on at a point in the code, you have to infer it. Grr.

Every time I get in production [in static languages], I run into some issue processing data that would never happen had it been written in a dynamically typed language.

I don't want to grab people like you and punch them, I want to either find a way to chill you the fuck out so we can have an actual discussion, or fire you so the rest of the team doesn't have to deal with religious fervor.

I think you have to be lacking mentally to not appreciate the beauty, power, clarity and flexibility that high-quality dynamically typed systems bring, in languages like Ruby, Javascript, Python, Lisp, etc.

People limited to one paradigm - static/dynamic, OO/functional - are a bane.

This is not to deny that some dynamic code bases are poor, but that's true of everything.

But solid dynamic systems are a huge advantage.

I don't actually wish more people spend time researching and building more advanced and better dynamic systems, because the ones we've got are plenty kick-ass as it is. We're already better off for it.

--

In actuality, in my experience, the strengths and weaknesses of static/dynamic are entirely based on how well or poorly "typed" the data you're dealing with is - over the lifetime of the project - although at small scale it really doesn't matter.

This is why dynamic languages took over the web - not only do you have very flexible information in systems you've already built (see "myths programmers believe about names, gender, time, etc" for a good example), but your development speed is such that the type of information changes ~1/mo anyway. Static languages are great for when have a well-defined problem that's not really going to change on you, and you need a solution that's fast and/or extremely safe.

The problems really only happen when you shut down the conversation with insults and vitriol.

The author asserted nothing but their own person experience. No logic argument is needed to support the claim "I feel X." Assuming a truthful author, the claim is self-supporting.