Hacker News new | past | comments | ask | show | jobs | submit login

>My team doesn't need to waste days doing archeological digs and comprehensions [...] We simply grab the code base, modify the code [...] and then fix the chain of compiler errors along the way until our new feature works.

"We don't need to read and understand stuff. We just grab the code by the horns and spur it with changes until the compiler stops thrashing. Yeehaw!"

There are myriad things that distinguish long-term maintenance from greenfield development. Like transferring application ownership from one team to another, reverse engineering, adapting to the changes in external systems you integrate with, investigating bug reports and performance issues, doing monitoring, etc. etc. If your only concern in "maintenance" is making some changes while avoiding the kinds of bugs that can be prevented by a static type checker, then something seriously does not add up.




If you would stop thinking of your relationship with the compiler as adversarial and start thinking about it as a tool which guides development I think you might start to see where we're coming from.


I was literally commenting about your point on “maintenance“.


Yes, you were. And you effectively had proven the point I made in my root comment. If your notion of large-scale maintenance involves only the problems that can be caught by a typechecker, you don't know what real maintenance looks like. Which means that even your comments about the issues that can be prevented by a type-checker are suspect.

Again, the wast majority of claims made about FP on Hacker News right now (even in this thread) were made about Java in early 00s. Almost word-to-word, except some terminology. Unfortunately, back then I didn't have enough experience to spot the issues with those claims and people who did have real experience were mostly silent.


This reads to me as, “You filthy FP advocate, you have no clue what real maintenance is!” I’m not saying the type checker alone is enough to perform large scale maintenance, you and I both know there is more to it than that.

At the end of the day, sure, we all have opinions on tools and how they make our lives better. You and I may not agree that FP is the right tool, but I’m not going to make sweeping generalizations that you know nothing about large scale development and and maintenance solely based on your language paradigm choice and a few focused HN comments.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: