chucknibbleston

5 ms·

1.
by chucknibbleston 10y ago
#1 - Nginx #2 - Redis #3 - Postgres
2.
by chucknibbleston 10y ago
This is interesting but the fact they list "adchoices" as a site's monetization makes me wonder how much they know about adtech...
3.
by chucknibbleston 13y ago
Is this a joke?
4.
by chucknibbleston 13y ago
I find "VSRE" unnecessary: if you write efficiently, anyone capable of a VSR will follow suit.
5.
by chucknibbleston 14y ago
If they know what you pirated, why don't the content providers just get your ISP to shut off your internet until you watch enough ads to make up for the cost (they could do a little rev-share to incentivize comcast). Piracy will exist as lo
6.
by chucknibbleston 14y ago
this is why I love the 3 finger drag in osx.
7.
by chucknibbleston 14y ago
or this: http://www.google.com/trends/explore#q=javascript%2C%20jquer...
8.
Server-Side Javascript Guide (1998)(docs.oracle.com)
2 points by chucknibbleston 14y ago|0 comments
9.
by chucknibbleston 14y ago
I bet that setting an interval to check for the specific node is actually more performant than using the mutation event (which as @Vekz pointed out, slows down the whole DOM)...
10.
by chucknibbleston 14y ago
we are living in the future
11.
by chucknibbleston 14y ago
Just to put this out there -- since nobody has really mentioned it -- ruby (as a language) doesn't have the greatest performance. You can do some tricks with GC to speed it up (Ruby EE might be a faster option), but you're still looking at
12.
by chucknibbleston 14y ago
I agree; the whole node socket/handshake is a ton of overhead if you're not interested in using the socket to make calls over the API you just authenticated.
13.
by chucknibbleston 14y ago
Unless you're providing an API/external access for your users, you can just use authentication internal to your app. It's pretty easy to roll your own (here's a tutorial for doing it in RoR: http://www.aidanf.net/rails_user_authentication_
14.
by chucknibbleston 14y ago
my 2 cents: These are interesting ideas, but besides being difficult to monetize (@mchannon), I'm not sure there's a huge demand for them either. The first one is going against a couple of big trends: 1. Mobile (even with low latency, strea
15.
by chucknibbleston 14y ago
1. I think you should consider dropping your first product. If it isn't bringing in good revenue and it's eating up your development time, you might be better off with just your mobile options. This would also handle #3. You should pick a s
16.
OAuth & One-Page Apps: Avoiding the Redirect(nicholasjacob.com)
32 points by chucknibbleston 14y ago|13 comments