Might be a bit late but:

I really like Sketch. Have been using it for the last couple years, and I don't want you all to stop making great things.

I guess my question is: To the extent that you can answer - what does the future of Bohemian Coding look like? Strong? Focused on Sketch? Exceeding adoption expectations?

Have you considered more stable, long-term revenue models, or do you find that the semi-annual big purchase at this price point works well for the company?

Funny you mention that: Sketch documents used to be package files within the last year-ish? Not sure of the reason they switched over to binaries.

Even though they're based in print units, EMs have a lot of really useful applications. Here's a quick primer: http://trentwalton.com/2013/01/07/flexible-foundations/

tl'dr: Using EMs you can proportionally scale whole blocks with one line of CSS. As opposed to changing PX values for margin/padding/border/border-radius/font-size etc individually.

It's very pretty, and I'd live to see wikipedia look like this. I particularly like the editing features.

But it's very image heavy. Lets put aside all the articles that have ugly images tat aren't suitable for this design and instead think about bandwidth: every few months wikipedia needs to raise more money, and I'm sure some cost is shipping all the static resources out to people.

So, to keep costs down, it seems like wikipedia would want a minimal amount of extraneous images on their most visited page - their home page.

I generally agree with you. I like Sketch, but I think the best case would be Adobe gaining inspiration from Sketch, and stealing some of the features for Photoshop.

Great point. I would guess that any really holistic design tool is going to eventually have all the complexity of Photoshop. After all, you'll need to be able to set type, illustrate, modify photos and work within grids.

So if "bloat" is what you want to avoid than you may always have to work within a tool where the limitations may influence the visual style.

That said, going back to Photoshop I have noticed several things in PS that have subtle negative influences in the choices I make while designing.

http://blogs.adobe.com/photoshopdotcom/2013/09/introducing-adobe-generator-for-photoshop-cc.html

Why should people coming in later pay, ultimately, less than the rest of us for the same set of features?

What you say here perfectly describes a subscription software license, like CC too. Imagine Sketch as running on a subscription model as well. Sketch's bills just come every 1.5 years instead of every month.

Also, who here paid for a newer model iPhone/android when their 2-year contract is up? Buying the iPhone 1 doesn't entitle you to free phone updates forever...

Metaphors aside, devs gotta eat. I'm happy to pay, and see my payment as a small bit of insurance that Bohemian Coding will be around long enough to make Sketch 4. :)

Great advice. Rarely possible.