Since August 2014 the St. Louis suburb of Ferguson MO has been in the news, not because it's a nice town (which it is) but because a Ferguson Police Officer shot and killed an unarmed black teenager. Purportedly the shooting was because the teenager had just committed a "strong arm robbery" by stealing a package of cheap cigars from a convenience store.
Remember why it was so important for "us" to go into Iraq to topple Saddam Hussain's sovereign government? I'm not talking about the real reason - access to Iraq's oil fields - but the reason we were told. Remember warnings of mushroom clouds, and Saddam's chemical and biological weapons research programs? The programs for which zero evidence was found once Western forces entered the country and toppled the government?
The default assumption for distributing a Node.js module is to publish it in the public npm registry. It's a simple declaration in the package.json, and then you tell your customers to simply type "npm install". The public npm registry takes care of the details, and you can even use versioning to make sure your customers use tested module versions. But what if you don't want to publish modules in the public npm registry?
There are plenty of new server side web application development technologies being developed. With the blizzard of choices before us, how do you choose between one or another? Will the newly hot web app technology really take off, or will it fizzle in a few years? For example, Node.js is getting a lot of excitement, but what about Go, or what about the mature platforms like PHP/Symfony or CakePHP?
Here's some ideas of how to choose a platform or technology.
We just watched Into the Dalek, and we have to acknowledge something - the story line references way back into Old Who, to a set of Patrick Troughton (Doctor #2) episodes collectively titled The Evil of the Daleks. In both cases we had a humanizing of Daleks, and Doctor#12's certainty there can be no humanizing of Daleks may stem from the experiences shown in The Evil of the Daleks.
Doctor Who is finally back on our screens, and I'm going to squeeze my episode reviews together. It's a bang-up opening for Peter Capaldi as Doctor #12 (or is it #14), so it sure looks like this new guy will do well with the role. As for the content - the main theme so far is "identity". Who am I? Why do I choose this face to show the world? That sort of thing. And then there's the question of "who the heck is Missy"? Heaven? Surely that's a setup for the end of the season, so we'll have to be patient about that.
URL's are not strings, but are a data structure that's represented as a string. How do you easily and reliably manipulate a URL string programmatically? Do you use regular expressions or other kinds of string manipulations? Given all the ways to encode data in a URL, how do you ensure it remains syntactically correct while doing string manipulation? Manipulating URL's with regular expressions is rather difficult because of the format and nature of a URL.
Housing costs in Silicon Valley are insane. Both rental and purchased housing has always have been outrageous, compared to the rest of the country, but the last two years has seen an absolutely insane rise in property values and rental rates. I haven't looked for data on this, but obviously those at the lower end of the pay scale are being priced out of the market.
Occasionally on Drupal sites (perhaps only Drupal 6), uploading a file to a file field, or the file uploads area on a node, results in the "filepath" indicating a different name than the "filename". That is, in the data model for a Node, you can attach files in the "uploads" or in a CCK field (in Drupal 7 this is slightly different) and each attached file is an object (or array) containing attributes named "filename" and "filepath".
Node.js is horrible with CPU bound processing, supposedly. Why? Because CPU-intensive algorithms block the event loop from handling events, blocking the Node.js platform from doing its core competency. Actually, as I demonstrate in my book Node Web Development (see sidebar for link), it's possible to use "setImmediate" to dispatch work through the Node.js event loop, and perform intensive computation while not blocking the event loop.