ctide

These things aren't pain points in the browser the way they are in Node. I have never felt the need for an ORM in the browser. I have never dealt with client-side code that was using so many libraries I had to worry about whether exceptions would be handled via exceptions, or the first argument of the callback, or rejected promises. No one (at least, no one I know) is installing node modules like isArray to use in the browser.

Yes, these things _could_ technically apply to the browser, but it's not commonplace. In the node world, these are all things you deal with consistently.

Companies do this all the time.

I hear this position often when people talking about contract-to-perm, and I just don't see it. If you're good at what you do, and people enjoy working with you, why wouldn't you take a contract to perm position? The only reasons I can see are that you are afraid you don't get the job (well, then you wouldn't have been a good fit if they hired you) or you end up not liking the team/company as much (same as if they had hired you.)

So, why wouldn't you? And I don't buy the 'I have a good job' line, because you wouldn't even be entertaining offers if you weren't interested in leaving your current role.

I'm an engineer with 15+ years of experience at all levels of the stack. Have worked both for, and at, a handful of YC companies. Currently have about 20 hours / week of availability, with potentially a bit more freeing up next month.

Main Technologies: Rails, React.js, Backbone, iOS, HTML/CSS/etc, Postgres, Chef, Puppet, Ansible, AWS.

http://www.github.com/ctide - http://www.twitter.com/ctide - chris at fifteenb.com

A fucking whiteboard.

https://coachella-streamer.herokuapp.com/?ids=8,12,16,17,19,... is my planned listening for the weekend. Hope someone else finds this useful!

I won't argue that calling it 'data compression' is nothing more than cute spin, though.

I mean, shit, lots of startups completely eschew IE support, and they're a way more significant portion of the market than the neckbeards who disable javascript.

I was never especially good at making art, but this was my favorite of the things I did make: http://artpacks.org/1995/fsn-0895.zip/CT-ASY.ANS

I feel bad for people who were born too late and missed out on the whole BBS scene. Those years were tons of fun, and nothing on the internet has ever been quite like that world.

It's not more responsive when you break the basic functionality of the web. Open in new tab has basically never worked with Instacart's site. I see that they attempted to remedy it a bit since the last time I placed an order (about a month ago). Now instead of generating hashbang URLs that the frontend completely ignores, it just generates broken URLs instead such as: https://www.instacart.com/store/whole-foods/departments/whol.... I get that there are a lot of challenges involved in building a business like this, but a frontend that's had basic functionality totally broken for months shouldn't be one of them.

1) This version contains binary, obfuscated or minified code. We need to review all of your source code in order to approve it.

We included all of the source, but we didn't explain how to setup a local environment to build handlebars templates, setup grunt, etc. so apparently source is not good enough on it's own. The reviewers have to understand enough about your app to build it themselves. Writing enough documentation so that someone in 30 days can hopefully glean everything they need (with no understanding of your app, or structure) without them being able to ask you questions is absurd.

2) Please use the CSS 'text-overflow' property rather than trying to deal with overflow via `innerHTML` modification.

We have multiline text we need truncated and displayed correctly. This means not having a random floating ellipsis at the end of the div, and it means we can't use text-overflow.

Mozilla's addon policy is just hostile, period. It doesn't have anything to do with open source.