toddgardner

> Important: It’s worth noting that each one of these Base64 encoded images is counted as a “request” in the Network tab of Chrome developer tools. This explains why there are so many images “requested” but the page is so fast. The browser never goes over the network to get them!

I don't think you read the article. Devtools shows 130 requests because it considers inline data URIs to be a request--instead, there are lots of inlined images. so the page looks mostly complete with only the original document request.

The most frustrating bug I ever fought only showed up on a remote device. I was working on an AngularJS component, and for some irritatingly-unknown reason, it would not render on a Samsung Android device. One specific device. It just happened to belong to someone really important.

Debugging remote devices sucks because you don’t have access to your tools. You can’t just open the inspector and dive in–you have to build and deploy custom debugging code. Then do it again with what you missed. And again.

We built RemoteJS to help with this--to help connect easily with troublesome remote browsers with the tooling you'll need to understand what's different there and debug it.

The service is based around the TrackJS agent, with some extensions in place to grab screenshots and execute commands. It establishes a websocket connection to a simplified debugger application, built in React.

Nothing is stored as part of the service, so it's all very inexpensive to run. A few folks might have put us on production sites today, which was a fun load test :)

Thanks for checking it out!

This is the best comment. Thanks k you for making it about the customer and the user instead of "code beauty".

I believe most Minnesotans are a little uncomfortable by this attention, and we'd like to go back to quietly making lots of money now.

Considering talent, you also must consider the culture of the region. Minnesotans are generally very understated and humble. I have met many people here who at first blush consider themselves average, but are amazingly talented.

There are truly amazing people here. They just aren't broadcasting it--and their not looking for work.

Giving your customers a soft landing is really important to maintain trust. They loved your product, and proved that the market existed--but it wasn't as big as you thought.

When closing down, has anyone explored not completely shuttering the company, but instead continuing to exist as a licensing entity? License the source code itself to your existing customers so that they can continue using it, without all the messiness involved in open sourcing it completely?

Probably a terrible idea, but it's what this blog left me thinking.

Our VMs and websites on USEast are unreachable, however our storage seems to be working fine. There is something very backwards with how they are communicating this outage.

The most clever exploit of XSS I've ever seen. Beautiful. Bravo.

Brilliant, very useful. Found and applied to a few that I didn't know were open.

Wow everyone, thank you so much for your support! Your comments and ideas have been amazing and positive. We're thrilled to be making an impact and to help make the web better.

Thanks HN, you're awesome.

You can specify the user id and the session id (these are just arbitrary strings you can set to whatever makes sense in your application)

Arbitrary key/values and filtering these values is coming soon as well.

TrackJS supports IE8+. For IE7-, we disable our instrumentation but your application remains functional.