slexaxton

25 ms·

1.
by slexaxton 12y ago
no ur absolutely horrible
2.
by slexaxton 13y ago
I don't believe they had much say in the change. They are still using the money to do what they said they'd do in their campaign, and many people are setting up their registry as their default. As far as I know they just got caugh
3.
by slexaxton 13y ago
This is a common confusion. The scalenpm crowdfunding was done by the good folks who ran the npm servers for free (mostly nodejitsu) up until the recent switchover to the new infrastructure with Npm, Inc. You can still use the nodejitsu reg
4.
by slexaxton 13y ago
[Stripe Developer] [edited for clarification] I appreciate your interest in the security of Stripe, I think we definitely share the same goals here (making everything as secure as possible). However, I think there's some misunderstandi
5.
by slexaxton 13y ago
(Stripe Developer) - tl;dr -- This claims that Stripe.js runs on the merchant's server environment, causing the server to be subject to PCI DSS. In reality, Stripe.js is served from Stripe's servers, and runs only in the browser,
6.
by slexaxton 13y ago
Agreed, this is what I did say several times in the article, as well as calling much of it non-scientific. Though I did cite 2 scientific studies, and some non-trivial biology, I meant the article as a personal experience piece more so than
7.
by slexaxton 13y ago
I don't know if I can properly distinguish the difference between programmers being overpaid and the rest of humanity being underpaid. > Even if it were true, it would be against our interest to say that we're an overpaid, enti
8.
The Productivity Cycle(alexsexton.com)
143 points by slexaxton 13y ago|38 comments
9.
by slexaxton 13y ago
Many important parts of checkout are open-sourced via our jQuery.payment plugin [1]. It allows you to build your own checkout flow from component parts. As for open sourcing (capital C) Checkout entirely, we're working hard to provide
10.
by slexaxton 13y ago
This varies from project to project based on needs. The checkout stuff uses sprockets-commonjs, browserify and require.js are used in other projects though. The decision is often made based on the backend (is it already ruby/sprockets?
11.
by slexaxton 13y ago
Hi, Stripe Developer here. We have a mostly per-project set of code style and tooling guidelines. Most (if not all) of our larger projects are coffeescript and commonjs based. That's mostly because they all share at least some code. As
12.
by slexaxton 14y ago
Thomas and Amy speak a lot on never accepting outside investment. So this was probably their own money. ("Bootstrapped," if you want)
13.
by slexaxton 14y ago
bentlegen _is_ an expert in third party javascript, and is correct that both domains need to opt in to a `document.domain` even if they would match with only one changing. This is to prevent this exact security exploit.
14.
by slexaxton 14y ago
You don't have to go from IE8 to IE9. You can go from IE8 to _any other browser_, and things will look up.
15.
by slexaxton 14y ago
Most people also apply this to object literals. There are no var statements in this situation.
16.
by slexaxton 14y ago
I don't believe that this is just an oversight because "people say you shouldn't use `with`". It simply cannot be optimized in the way that normal property accessors are. If you look at old IE perf, they're actually pretty close (both rea
17.
by slexaxton 14y ago
Brendan's other words included: > My two cents: be careful not to use ASI as if it gave JS significant newlines. http://brendaneich.com/2012/04/the-infernal-semicolon/
18.
by slexaxton 14y ago
Doesn't `with` have significant runtime costs? I didn't think people didn't like that one because it was a 'bad pattern' - I thought it was because it was really slow. EDIT: I went ahead and JSPerf'd it, and it is 13x slower to run the exam
19.
by slexaxton 14y ago
I agree consistency is key, but it _was_ consistent before (in it's use of semicolons), and is still (in it's non-use of semicolons).
20.
by slexaxton 14y ago
Fair enough, I'm not claiming that other, much more difficult work didn't go into the feature updates. What was the reasoning for switching to semicolon-less? Why wasn't that a concern when the project started? (Apologies if I missed it in
21.
by slexaxton 14y ago
Naturally, the semicolons have always been stripped by the minifier. This makes the code no more 'minimalist.'
22.
by slexaxton 14y ago
Not using semicolons seems fine enough. Going through and removing the semicolons that you already used seems like you're just trying to start drama. Why not use that time to do something that effects the code positively or negatively?
23.
Jed - Gettext Style i18n for Modern JS Apps(slexaxton.github.com)
31 points by slexaxton 15y ago|0 comments
24.
by slexaxton 15y ago
27 minute FTFY
25.
by slexaxton 15y ago
What about shoes proxy support?
26.
by slexaxton 15y ago
What are you referring to? This is a blog post and the talk that she refers to in the first paragraph has full audio/video available here: http://jsconf.eu/2010/speaker/the_jquery_divide_by_rebecca_m... Hope that helps your hate.
27.
by slexaxton 15y ago
Unrelated to the OP, but related to this: I get that it's real life, and people forget that all the time on the internet. You should start feeling better soon. Forealz. I demand it. CFS sounds terrible and we're all rooting for you to figur
28.
by slexaxton 15y ago
I agree, but I think the point of Tom originally linking it was to show that Dustin had integrated a micro-framework (from you), and couldn't get a response from you (even to say the stuff you mention above) and eventually closed the ticket
29.
by slexaxton 15y ago
Mostly agreed, and well articulated. Though, the point I believe that Tom was trying to make about Diaz having to ask Thomas to change things was more valid with the links that were likely stripped from your comment: https://github.com/mad
30.
by slexaxton 16y ago
Actually it makes a ton of sense to asynchronously require javascript files on your production page. If you load them asynchronously and in parallel, you can often get much better performance than one single request (serially). http://blog

More ›