Oh man Palau has NaN% software engineers accepted :(

don't despair, maybe they have infinite engineers.

those are the export formats

Thoughts on which has the better type system?

In my opinion both has strong and weak point. I love how flow can capture generic for higher order function and I love flow non-null types. In the other end typescript seems 'safer' especially in the field of type inference, sometimes flow infer union types where you really would not expect to happen. Which ends up with some weird bugs.

<neo-voice> I know category theory </neo-voice>

Kidding. Where's the tl;dr?

tl; dr Collections of objects and maps between them are themselves good objects to consider. So meta, much abstraction, wow.

I know how you feel.

I've worked at a couple of startups, two groups at Apple, two groups at Google and now at Twitter. I've learned two things chasing a feeling of fulfillment, like you seem to be:

1. You can't expect your job to give you the all of the fulfillment you need.

2. The most fulfilling work is the kind of work that's just challenging enough, but not too challenging--http://en.wikipedia.org/wiki/Flow_(psychology)

Hilarious, but needs more vbscript.

The authors makes it sound like after designing the UX, the implementation will become trivial. I think this is a bit naive because most serious applications go through many iterations of UX. Some of these changes will be small and not require significant re-plumbing, but others will necessitate a lot of behind-the-scenes churn.

My point is that it's better to design the plumbing of an application with some longer-term considerations than just "what do we need to implement that UI wireframe."

Minimal viable products are cool and all, but let's not use that as an excuse to write something that will need to be thrown out wholesale to add that big traction-building feature.

So how do you reply when the interviewer asks you why you left the previous job?

Yes, Javascript the language is getting better support in browsers, but DOM manipulation without a framework (like jQuery) is still horrible.

That's completely contrary to what I've experienced. Only browsers that "need" a little extra JS/CSS are the old IE versions. Quotes indicate you don't necessarily need to enhance pages in those browsers at all these days.

If your experiences indicate otherwise, you are simply doing something wrong.

PS. jQuery is horrible. Every time you think you've figured out all of their undocumented quirks, they change the logic. It's famously inept in IE 6/7.

If you don't understand basic memory management without ARC, you have no chance of ever understanding the weak reference annotations that ARC requires in certain cases (e.g. to avoid retain loops).