Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SlackTextViewController: A new growing text input for iOS

github.com

Post reply on HN
Print view View original

31–35 of 35 posts

Re: SlackTextViewController: A new growing text input for iOS

#31

Post by pilif »

jbrooksuk wrote: post #19
Void_ wrote: post #8

Earlier quoted context omitted.

Agreed! Where I work, GitHub graphs make it look like I'm doing 5 times more work than everyone else. But I'm really just pushing commits more often.

Since January I've been insisting that we make atomic commits, but now I'm looking to switching to squashing them into one before merging. This makes it a lot easier to roll back a whole feature and not half way through it. Plus, our graphs look ridiculous, I'm easily 5-10 times over the others, but it's not that I'm doing more work, I just commit more often.

We're using atomic commits since 2009 when we moved to git. However: we very often merge features with --no-ff to make it way easier to back them out at once if needed.

That way you get the best of both worlds (very easy archeology and very easy backing out of features)

Re: SlackTextViewController: A new growing text input for iOS

#32

Post by dirtyaura »

rip747 wrote: post #13
kclay wrote: post #10

As someone that doesn't do iOS development it boggles my mind that you guys have to build this feature into your apps.

I'm with you. I don't do iOS development at all, but I will literally sit there and go through the entire code of every iOS control submission to Hacker News just to see how they accomplish what they do. I cannot believe how much code it takes to do something I feel you can accomplish easily in javascript. Kudos to all the iOS developers out there. I don't know how you guys manage to do it, but I'm sure glad you do a…

I've been on the both sides of the fence: writing native iOS apps and trying to do mobile web iOS apps. From the bottom of my heart: writing native apps is far more enjoyable and productive at the moment.

With the browser engine underneath, you get nice benefits in text layouting, image handling and some inputs, but it requires a lot of work to get good performance, to get touch interaction and scrolling feel natural, to make transition animations to work well. Offline access is also PITA if you have a lot of data - indexedDB crashes left and right if not used carefully. The last 20% of the app takes 800% of the time :) and the result is still not what you wanted.

I haven't encountered many good mobile web apps. HN app by @premii is pretty good (http://hn.premii.com/), and the developer once described here in HN that he didn't use any JS library like jQuery for performance reasons, everything had to be coded manually.

Re: SlackTextViewController: A new growing text input for iOS

#33

Post by dirtyaura »

kclay wrote: post #10

As someone that doesn't do iOS development it boggles my mind that you guys have to build this feature into your apps.

Autoresizing text areas aren't supported by browsers either, you have to use Javascript to implement it. http://stackoverflow.com/questions/454202/creating-a-textare...

Re: SlackTextViewController: A new growing text input for iOS

#35

Post by thrush »

Void_ wrote: post #8
dzenbot wrote: post #7

Earlier quoted context omitted.

Atomic commits yo! But yes, it was built with much love and attention to details.

Agreed! Where I work, GitHub graphs make it look like I'm doing 5 times more work than everyone else. But I'm really just pushing commits more often.

I think atomic commits can either bump or decrease your commit frequency.

If you had a giant piece of logic that wouldn't be atomic in multiple commits, but you have multiple commits on your machine for the sake of saving your butt in case you roll down a weird rabbit hole, then you'd probably squash before merging into master and end up decreasing your total quantity of commits.

If you had a lot of small changes that all were safe seperately, you might break up what could have been a single commit into several commits so that you have a more descriptive history, and increasing your quantity of commits.

Post reply on HN