phink

no profile record

comments

·vor 6 Jahren·discuss

Yes, installed size is also an issue. And on iOS tens of thousands of small files will waste a lot of space. One may say that compared to photos and videos that's small potatoes but I disagree. Efficient use of resources, memory, bandwidth, battery, etc. matters.

phink

·vor 6 Jahren·discuss

On top of the discussed complexity and featuritis, I suspect over-engineering, NIH syndrom and "architecture" must have played a role. Misunderstanding, misapplying and blaming MVC to end up with twice the code in 3 or more times more classes.

phink

·vor 10 Jahren·discuss

It's not just methods starting with test, it's methods starting with test in a subclass of Test. It's a simple, working convention. Conventions are good, not pretty bad.

Adding more stuff to the language only makes it more complex and requires more effort. I don't see this as a much better solution but as an over engineered one, as much of what Apple is doing these days.

phink

·vor 10 Jahren·discuss

Swift is not even safer than Objective C since you can pepper your code with ? and ! and get the same runtime problems.

I would even say that it is less safe as time pressure and having to spend time on such trivial things combine to make you lazy about it and just add them to keep the compiler happy.

phink

·vor 10 Jahren·discuss

> Safety

if (indexPath == 3) {...} Results in a warning in Objective C, none in Swift. Did you see that .row is missing?

> Productivity

How is (notification.userInfo?[UIKeyboardFrameBeginUserInfoKey] as? NSValue)?.CGRectValue() more productive than [[notification userInfo][UIKeyboardFrameBeginUserInfoKey] CGRectValue]

Swift makes me waste my time on trivial things.