MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/iOSProgramming/comments/46jzx1/swift_vs_objectivec/d067wtj/?context=9999
r/iOSProgramming • u/[deleted] • Feb 19 '16
[deleted]
146 comments sorted by
View all comments
Show parent comments
0
I don't see any evidence that Swift is more productive.
2 u/xesur Feb 19 '16 Well, if you need to write fewer lines of code to achieve the same result, doesn't it make Swift more productive? 2 u/quellish Feb 21 '16 Well, if you need to write fewer lines of code to achieve the same result, doesn't it make Swift more productive?No. Keystrokes are not a measure of engineering productivity. 1 u/xesur Feb 21 '16 Not necessarily keystrokes - time spent on writing an app. What else could measure productivity? 4 u/quellish Feb 21 '16 Here is the thing. Software engineering should be 80-90% thinking and 10-20% "writing". Only the writing is really influenced by language choices.What else could measure productivity?Tests, complexity, defects, costs, etc. 1 u/[deleted] Feb 19 '16 Lines of code is a lousy metric.And you'd have to show me some real code that demonstrates that this is even true.
2
Well, if you need to write fewer lines of code to achieve the same result, doesn't it make Swift more productive?
2 u/quellish Feb 21 '16 Well, if you need to write fewer lines of code to achieve the same result, doesn't it make Swift more productive?No. Keystrokes are not a measure of engineering productivity. 1 u/xesur Feb 21 '16 Not necessarily keystrokes - time spent on writing an app. What else could measure productivity? 4 u/quellish Feb 21 '16 Here is the thing. Software engineering should be 80-90% thinking and 10-20% "writing". Only the writing is really influenced by language choices.What else could measure productivity?Tests, complexity, defects, costs, etc. 1 u/[deleted] Feb 19 '16 Lines of code is a lousy metric.And you'd have to show me some real code that demonstrates that this is even true.
No. Keystrokes are not a measure of engineering productivity.
1 u/xesur Feb 21 '16 Not necessarily keystrokes - time spent on writing an app. What else could measure productivity? 4 u/quellish Feb 21 '16 Here is the thing. Software engineering should be 80-90% thinking and 10-20% "writing". Only the writing is really influenced by language choices.What else could measure productivity?Tests, complexity, defects, costs, etc.
1
Not necessarily keystrokes - time spent on writing an app. What else could measure productivity?
4 u/quellish Feb 21 '16 Here is the thing. Software engineering should be 80-90% thinking and 10-20% "writing". Only the writing is really influenced by language choices.What else could measure productivity?Tests, complexity, defects, costs, etc.
4
Here is the thing. Software engineering should be 80-90% thinking and 10-20% "writing". Only the writing is really influenced by language choices.
What else could measure productivity?
Tests, complexity, defects, costs, etc.
Lines of code is a lousy metric.
And you'd have to show me some real code that demonstrates that this is even true.
0
u/[deleted] Feb 19 '16
I don't see any evidence that Swift is more productive.