Computer, Lieutenant Commander Worf. Confirm auto-destruct sequence, authorization Worf 3-7 Gamma Echo.

Perhaps it needs more structure? e.g. a 10mx10m region shares the same two words and then the third word acts as a reference into that array of 100 points...

CTRL-ALT-F1 to get a non-vga terminal?

I was under the impression Big-O implies the existance of a constant c, for all x > c, f(x) > g(x) where f(x) is the function your bounding it by and g(x) is the function you're trying to describe..

Hence, its just saying "sooner or later", this will always be a bound...

You are right, there is nothing you can do with puppet that you can't do with SSH, and 10 years ago things like puppet didn't even exist so it makes total sense for you to be in the situation you're in and it wouldn't make alot of sense for you to switch just for the sake of using puppet.

But it's 2013, if you're starting off new - why would you roll your own when many solutions already exist that have been thoroughly tested and extended to have a rich feature set that you probally wouldn't have time to develop as a day-to-day dev op. Furthermore, Puppet allows for this idea of modules that people can write generic versions of "apache" or whatever and often times you don't even have to write configuration systems yourself but instead you can just clone it off github and customize it to your liking..

Your question about standing up servers is silly - why would a more manual solution be impacted differently than a puppet solution based on in-bound bandwidth? Puppet allows for client/server architecture and if bandwidth was your big concern, you could set up a local puppet machine in Chengdu and build servers in that data center based on that...

I worked in a largeish datacenter in 2002 and wrote alot of SSH scripts to manage those servers - it works but its tedious. The benefits of using something like puppet is enormous.. The company I work for now used to employ a full time sysadmin - now the devs just update puppet as we need and it hardly impacts our workloads given how easy it is for us to maintain...

This is why puppet has a very strong inheritance system... We have it broken down as generic server (2 factor/LDAP configs, nagios configs, etc) and then apache_servers which build out the basic web infrastructure and then more specialized configs for one-off speicalized servers... (admin server versus production web servers)



There is pretty much nothing you can do by hand that puppet can't also do - and often it takes just as much time to update a single puppet config file and run the puppet update process as it would be to ssh into the server and make the manual change.

Another advantage is what might go into traditional documentation is now just a puppet configuration.. Oh, fuck, this server crashed? Just roll another in 5 minutes... Who cares about the old one..

1. jQuery core is hardly bloated, its 32k.. If you are willing to drop support for older IE, you can use jQuery 2.0 which is even more streamlined than its ever been.

2. Animations are not part of jQuery, they are part of jQuery UI which is a totally separate library and which I agree, sucks.

3. Native JS syntax for ajax is convoluted..


$.ajax({
url: '/some/url',
success: function(o) {
}
});


Is much more maintainable to me than several lines of new xmlhttprequiest()... blah blah blah... every time you need to make an ajax call...

4. Jquery has lot of powerful stuff that lets you write less code much of the time such as .on().. Much of the bad javascript I come across is from people who are trying to write it all themselves and have onclick handlers hard coded into tags in a giant unmaintainable mess. Unobtrusive Javascript is for the win and you'll save yourself alot of headache using jQuery to write it.

This is dumb for a variety of reasons. jQuery lets you abstract away a ton browser inconsistencies. It also makes you alot more productive b/c you don't have to constantly event wheels...JS by itself is extremely tedious syntax wise . (do you really like document.getElementById riddling your code to the point of unreadability? I'm sure you'd say oh, i'll just write a helper. Well congrats, there you go inventing wheels) Some of the worst code I run across on the web always seems to be the guy that insists on doing things with pure javascript and he has tons of onclick handlers directly on tags and all sorts of other crap which makes sites completely unmaintainable...

I write code for both sides, there's no reason people need to live in their ivory towers...

I've dealt with similiar situations in my professional career. Rackspace's DDOS protection isn't worth it, after 3Mbps, they null routed our box because the size of the attack was so large that it was saturating their uplink capacity...

Prolexic has a cool approach, you proxy your site through them (either web proxy or they can annouce BGP routes for you) and they have massive datacenters that do nothing but scrub packets for you.

The downside is their service is very very expensive ($60k+ a year)

Political discussion is an activity for fools. It's like arguing which brand of anal lube or who's servant of satan is better

Not all personal lubricants are the same, silcon based are more effective in the short run but have the nasty side effect of hanging around for days. Water-based lubes are easier to wash off but need to be re-applied more frequently.

Even in thoose categories, the lubes widely differ beteween manufacturers, some are too viscous, others are too thin..

So I must wholeheartedly disagree that putting thought into your choice of anal lubricant is a fool's task.

iOS uses the same kernel and core infrastructure as OSX..