HN user

cgislason

63 karma
Posts3
Comments39
View on HN

I think the trick is to shed your imposter syndrome, but remain humble. You can be confident and humble at the same time. It can come with accurate self-assesment. Keeping your weakness in mind helps a lot.

How would you recommend becoming familiar with idiomatic Go?

I've read various articles including (but not limited to) tutorials, made a point of exploring a few open source projects and I've written a few thousand lines of Go. I enjoy writing Go, but I have a hard time so far figuring out if what I write is idiomatic.

BTW, feedbin.me DOES work on mobile. The layout adjusts and shows just the list or just the article view, instead of both at the same time.

The circles actually seems to reduce value because there is no intuitive order to each group. In some (many?) use cases for Trello, priority is important.

One thing that the circle metaphor does add is nested groups, which I can see being important for a different set of use cases.

I've heard a few times before that the iOS keyboard invisibly grows the touch target on the letters it predicts are most likely to be typed next. Unfortunately, my quick attempt to find a source failed.

Touché 14 years ago

Potty training; put baby on the toilet before the diaper gets wet. Babies can be "trained" a remarkably young age, if the parents can predict urination.

I personally find it useful to have a plankton mode and a shark mode, switching between them as necessary. Drifting is useful at times, but you definitely miss out on many of the best parts of life if you don't push yourself.

Don't get distracted by the politics and fighting in the mobile space. Work on what you love and enjoy.

My suggestion: start with native app development for the device that you own and use most. Run through a couple of beginner tutorials and write a few toy apps. This will give you a more solid foundation for making decisions. (I would not recommend using cross platform tool-kits until you understand the trade-offs.)

Then, I recommend that you build one of your ideas for the same device and release it. After releasing it, you can either move on to the next idea or port it for the other platform.

Last summer I evaluated Lift vs Play 1.x and was leaning heavily toward Play. I wrote some toy apps in each. We chose Lift only because it turned out that Play was incompatible with our Maven setup. (I have heard it has improved in 2.0 but I have not looked into it myself.)

I found Play to be fairly intuitive and it matched my mental model pretty well. It was lightweight compared to Lift and the other Java frameworks I looked at. Play 2.0 seems to have made improvements in the areas I found weak in Play 1.x. i.e. modularity, Scala support (specifically for continuations)

Lift is a fairly heavy framework, but you can ignore big parts of it if you need to. In Lift it took me a while to grasp the HTML transforming concept, partly because the documentation seemed to out of date. It felt both cumbersome and elegant at the same time. Sadly I didn't get very far on the project so I have no idea how Lift has changed/improved since then.

Today I would choose Play in a heartbeat if it fit the parameters of my project.

Introducing WebAPI 15 years ago

I agree, unless someone can point to anything Apple has ripped out or deactivated in WebKit. Apple seems to have been pretty open with Mobile Safari.

The most closed thing I can think of is when they only enabled their faster JS engine for the browser itself and not for apps. The next major release changed that, and it is not related to WebKit itself.