5 ms·
If one bothers to learn about tools and why they are useful, they can think a little bit deeper and understand why some intellectual argument do result in softw
by sbilstein 14y ago
If one bothers to learn about tools and why they are useful, they can think a little bit deeper and understand why some intellectual argument do result in software that ships. We write Scala at my company because we've found that with the right developers who seek to understand type systems and fp we can ship fast as fuck. I'm dozens of times faster working in Scala than I ever would be in php. We want to beat the average, not be the average.
http://www.paulgraham.com/avg.html http://www.paulgraham.com/avg.html
- Domenic_S 14y agoThat's a situation particular to you and your team, unless you're saying everyone would do a better job in scala?
- balloot 14y agoI've programmed large projects in 6 or 7 different languages now and I simply don't believe your statement "I'm dozens of times faster working in Scala than I ever would be in php." That's like saying "I would write that essay dozens of times faster in Spanish than I would in English." The tough problems that take most of the time are the design and theoretical understanding of the problem. The actual tools used to implement the solution, while not trivial in their differences, are never as important as fully understanding the problem and having a good architectural design. Or put differently, if you found me the fastest, most knowledgable person in the world with PHP web development, and then found the same guy for Scala, my assumption is they would both build a particular project in the same amount of time, all other things equal. And I could guarantee that one of the two wouldn't be "dozens of times faster" than the other.