nerd_in_rage

I've taken a look at both Backbone and Knockout over the past week or so, and I definitely prefer the Knockout approach.

Backbone... I just don't get it. It seems like there's too much complexity. I'm mainly a back-end developer, so perhaps it's just me.

It's good because it's not something that should be done.

Ask yourself why you need to detect the user agent.

Good. User-Agent detection has always been a hack.

Is it a framework for making a site that looks like it was designed by a pre-schooler? Then, yes, good job.

Otherwise ...

No, that's unlikely. PHP's main advantage is its ease of deployment on shared web hosts: upload your files and you're done.

Just keep your mouth shut about what you do in your own time and you'll be find.

Eventual consistency, yes. What I'm saying is if a few pics disappear for a half hour while things resolve themselves, nobody is going to care... or likely notice.

It's not a bank.

By the way, I believe social networking is mostly bullshit, which is my "LOL" at the "social graph".

What? It's the absolute truth. If someone's wall post or tweet goes missing, it's totally inconsequential.

"Social graph" - LOL.

I have my own /24 routed to my basement. Back in the early/mid 90's could get their own provider independent block.

If I knew now what I knew then, I would've gone for a class B block. lol.

I witnessed one guy implement an OAuth 2.0 provider completely wrong (he was accepting user credentials as client credentials, or something similar.) This guy was smart, and just couldn't understand the spec.

Upon reading the spec, it seemed that OAuth2 is really just some rough guidelines. Pick and choose what you need for the particular flow you're implementing.

If it's 1999 again, you know what's around the corner, right? pop

hasn't lying has always been a business model?

How much did you guys raise initially? How long did you take to figure out the original idea wouldn't work?

This is fairly common (liars and frauds...), though there are some great managers out there: they're just as rare as great developers, and worth their weight in gold when you find them.

Most companies go nowhere.

How is this surprising?

I had a UUCP feed through the early 90s. Fun times!

Just use text.

actually, the domain does "resolve". it's a web server configuration issue.

Because then it wouldn't be C?

Registering a business is a waste of time and money until you actually have a business to register.

Dozens.

odds are nothing will happen. just give adequate notice, as professional courtesy. it happens ALL the time. i've done it a couple times when projects go awry and never gave it a second thought.

if you want to waste time and money over a trivial issue? then talk to a lawyer.

this mirrors my experience with scala, except we had about 100+ maven dependencies and build times were closer to 10 minutes.

hibernate will make you throw up with all the verbosity and nonsense.

sqlalchemy, on the other hand, is good.

XMPP is still bloated and the specs still suck, so not much has changed.

yes, this happened to me, too. shocking. ;)

not really. it's pretty expected.

stock options are lottery tickets.

Yes, the PHP "language" sucks. But that isn't what matters: From a practical standpoint, it's good for getting things done.

The reason? Almost zero deployment complexity. You can take Joe Web Designer off the street, give him SFTP (or, more likely, FTP) credentials, and have him modifying your site in minutes.

Modify a file, click refresh.

Good article. The app store stuff is spot on (coming from someone who's either directly or indirectly worked on over a dozen iOS apps.)

I tried talking a client through deploying his stuff to the app store. It took about a half hour to figure out what weird setting (overridden by his target settings) that he had different.

Does stuff really need to be this difficult? it's almost absurd.

I thought about getting 2 jobs telecommuting: twice the pay for half the work.

URL please.