Not sure why publishing online necessitates getting to the point. It's long form and follows a very common story telling format. The world has room for different ways to tell a story.

I'm not sure that trying to keep everything in one file is necessarily a great argument. Optimizing for not having to open files doesn't seem like the best thing to optimize for. Even many of the react+inline styles examples include putting variables and other patterns into external files. Language (i18n) strings could be another external dependency. Data model, controllers, and routing are other good examples. (Rarely (if ever) have I seen an MVC framework that doesn't separate things into separate files.)

It's more conceptual than keeping everything in one file. I want to be able to see everything related to a component without looking at anything else, and to be able to easily change its styling in the same way I change its structure or behavior (at least with React). You can technically do this by creating a separate CSS file for every component, but the problem is your CSS has no context about your component, and so you end up doing all kinds of shuffling with classes to get things to display the way you want them to. This is a much more elegant solution, in my opinion.

While you can't modify pseudo elements or pseudo classes, you can replicate them using actual elements and conditional logic. I've seen React examples that do just that.

Yeah, it's the former. Their 2014 GMS (Gross Merchandise Sales) was closer to $2B.

I wrote a book a couple years ago called Scalable and Modular Architecture for CSS. I self-published in PDF, epub, and mobi formats. I also had the book on Amazon for awhile through the Kindle program and also have it available through pragprog.

I went ebook to start and then added a print version which I print up with a local printer in batches of approximately 500 at a time. I've since had the book translated into French and Japanese.

I've generated approximately $60k in revenue this year alone, not including revenue from Amazon or Pragprog, which were both relatively minimal in comparison.

We don't have a chip and pin reader right now but you can use your own chip and pin system with Shopify POS.

Specific to your abandoned carts comment, the view is filterable. Type in "Canada", for example, and it'll show all abandoned carts in Canada. We'd love to learn more about what you're looking to accomplish that is difficult to do right now.

Of note, there are other POS providers that use the Shopify API to provide integration and have been for awhile.

We had looked into other names and POS/point-of-sale was the most recognizable and familiar with storeowners. Yes, the acronym is a little unfortunate. :)

Animating transform doesn't affect page scroll, which is a more useful use case (since users need to scroll a page) than being able to use a translate transformation.

Of note, a translate transformation still isn't perfect. It seems to chug and then turn into a smooth animation.

Eh, updating page at end/cancel easy enough. I use this approach to animate a page scroll:

1. Animate #transform using jquery's animate (which doesn't work out of the box unfortunately, you have to use a custom #step fn)

2. Install "capture" event handlers on document.body that will cancel the animation, reset scrollTop to the state of the transform, then reset the #translate to 0 on #scroll or #touch (so we don't "fight" the user scrolling)

3. .. animation runs, calls my "complete" callback which uninstalls the event handlers, sets #translate back to 0, and updates scrollTop. Unfortunately there is a noticeable "glitch" here if the user tries to immediately further interact with the page.

#2 is optional (OP's implementation didn't handle canceling anyways). I'm sure there's a jquery plugin to do this and degrade to scrollTop on non-webkit browsers.

Edit: formatting.