re: The non-broken promise of static typing VIEW POST

re: To me this isn't really about finding bugs. When the codebase start to grow and you need to find the impact of a change, there are IDE that will be...

Yeah, I agree with all the points you bring up. Although, how often does a small, one person codebase dramatically increase to a large, multi-person project? ;)


I would say most successful projects in a company will eventually become something large. You'll want more features, the people working on it will change over time and so on.

Sure you can be in "one shot" mode where you create a website for client that will not change, maybe even for a short event and then you can trash it. But most often if it work well, if it is valuable you'll want to build on it and it will eventually become huge.

Most of the applications and libraries used by people around the world are actually big or huge. Your operating system, your beloved IDE, your photo sharing program, even just a network library...

But for one successfull application there hundred of failure. If you are alone and can go faster with a dynamic language and can fail faster, that's great. Once there a significant income/budget for the project as people recognize it's value you can always change technology. A bit like twitter that gone from ruby on rails to java and scala.

code of conduct - report abuse