As someone who works in many facets of the music industry, I used to seethe with a mixture of anger and jealousy when I would hear people in more “traditional” goods-based industries argue in favor of music content-based piracy. They made all the classic talking points, like “I wouldn’t spend money on this artist normally, and maybe if I like it I’ll spend money on them when they come to town” (which never happened), or “artists are rich and I’m poor, they don’t need my money” (rarely the case), or the worst, “if it were fairly priced and worth paying for, I’d buy it” (not true).  I always wondered if they’d have the same attitude if 63% of the things acquired by customers in their industries weren’t actually paid for, as was conservatively estimated as the case for the music industry in 2009 (other estimations put the figure of pirated music at 95%). Well, we may soon see the answer to curiosities like that. Though one can say with tentative confidence that music piracy is on the decline thanks to services like Spotify and Rdio, it could be looming on the horizon for the entire global, physical supply chain. Yes, I’m talking about 3d printers.

Before I get into the heart of this article, let me take a moment to make one thing clear: I think these machines are incredible. It’s damn near inspiring to think of even a few of their potentially world-changing applications: affordable, perfectly fit prosthetic limbs for wounded servicemen and women; the ability to create a piece of machinery on the spot instead of having to wait for a spare to arrive in the mail, or en route if your car or ship breaks down in a far away place; a company based out of Austin, TX even made a fully functioning firearm from a 3d printer a few months ago.

If these machines become as consumer-friendly and idiot-proof as possible (like computers), it’s possible that in a matter of decades (maybe less), a majority of U.S. households will have their own 3d printer. There’s also the possibility they could take the tech-hobbyist path, one that is much less appealing to the masses. Dale Dougherty of Makezine.com estimates there are currently around 100,000 “personal” 3d printers, or those not owned for business or educational purposes. I don’t think they’ll ever be as ubiquitous as computers, but there are plenty of mechanically inclined, crafty hobbyists out there who would love to play around with a 3d printer if it was affordable enough.

That being said, is there reason to worry about the economic implications of consumers making what they want, essentially for free, instead of paying someone else to produce it? Or will the printers instead be used for unique items more so than replicating and ripping off other companies’ merchandise in mass amounts? The number of people working in industries that would be affected by a development like this is far greater than the number of people who work in content-based industries, so any downturn would probably have a much larger economic implications. Certainly, those times are a ways off, but a little foresightedness never hurt anyone!

Invoking an external command in Python is a two step process:

from subprocess import call
call(["ls","-1"])

Sage wisdom states that there are two sides to every coin. This timeless wisdom will be borne out in spades with Windows 8/RT. Let's get into the dark side first.

If your users are veterans of Windows it is safe bet they are going to take one look at Windows 8 and scream blasphemy. Users whose brains are geared towards visual learning will undoubtedly yell the loudest and longest.

There's a good reason for this. Mick Jagger brought his band to the Redmond campus, performing live "Start Me Up" in the summer of 1995 (it was a great show). This heralded in the abandonment of program icons sitting on the desktop and introduced the now legacy Start button.

Ending the life of the 17-year-old start button is not going to go well with some users.

It is said that spoken languages shape thoughts by their inclusion and exclusion of concepts, and by structuring them in different ways. Similarly, programming languages shape solutions by making some tasks easier and others less aesthetic. Using F# instead of C# reshapes software projects in ways that prefer certain development styles and outcomes, changing what is possible and how it is achieved.

F# is a functional language from Microsoft's research division. While once relegated to the land of impractical academia, the principles espoused by functional programming are beginning to garner mainstream appeal.

As its name implies, functions are first-class citizens in functional programming. Blocks of code can be stored in variables, passed to other functions, and infinitely composed into higher-order functions, encouraging cleaner abstractions and easier testing. While it has long been possible to store and pass code, F#'s clean syntax for higher-order functions encourages them as a solution to any problem seeking an abstraction.

F# also encourages immutability. Instead of maintaining state in variables, functional programming with F# models programs as a series of functions converting inputs to outputs. While this introduces complications for those used to imperative styles, the benefits of immutability mesh well with many current developments best practices.

For instance, if functions are pure, handling only immutable data and exhibiting no side effects, then testing is vastly simplified. It is very easy to test that a specific block of code always returns the same value given the same inputs, and by modeling code as a series of immutable functions, it becomes possible to gain a deep and highly precise set of guarantees that software will behave exactly as written.

Further, if execution flow is exclusively a matter of routing function inputs to outputs, then concurrency is vastly simplified. By shifting away from mutable state to immutable functions, the need for locks and semaphores is vastly reduced if not entirely eliminated, and multi-processor development is almost effortless in many cases.

Type inference is another powerful feature of many functional languages. It is often unnecessary to specify argument and return types, since any modern compiler can infer them automatically. F# brings this feature to most areas of the language, making F# feel less like a statically-typed language and more like Ruby or Python. F# also eliminates noise like braces, explicit returns, and other bits of ceremony that make languages feel cumbersome.

Functional programming with F# makes it possible to write concise, easily testable code that is simpler to parallelize and reason about. However, strict functional styles often require imperative developers to learn new ways of thinking that are not as intuitive. Fortunately, F# makes it possible to incrementally change habits over time. Thanks to its hybrid object-oriented and functional nature, and its clean interoperability with the .net platform, F# developers can gradually shift to a more functional mindset while still using the algorithms and libraries with which they are most familiar.

Related F# Resources:

F# Programming Essentials Training