I like your zoology analogy. I would like to add that naming things is useful and important.

Years ago, I presented a 5-10 page design for a software component to my manager and the company architect. I had a nice document with diagrams and all that. After about 10 minutes in the meeting of presenting some stuff, the architect patiently said something like "So you plan on using a builder pattern, using chain of responsibility to dispatch the events. Sounds good, go for it!" He called for the meeting to be over and, slightly stunned, that ended the meeting.

This was a really good experience. Had I known the design patterns for what I was putting together, I could have simplified my document into a few paragraphs and saved a lot of time. Having a common vocabulary makes it easier and faster to communicate.

Anyone who has designed with multiple teams with different backgrounds will have similar experiences with vocabulary. One person says "queue" but they really meant "signal" and 45 minutes of arguing happens before the parties realize they meant the same thing but didn't know the word. (P.S. Microsoft loves to confuse terminology by naming their products after industry acronyms. Their development platform is "Dot Net" their SQL server is "SQL Server" and their web framework is "MVC")

The submitter has asked for input on a solution, but not defined the problem yet. So we can't truly help.

I don't know about other OSs, but with Windows, the OS actually already knows some of this information. The appdata\roaming folder is important stuff that should go with you. The appdata\local can be lost, and just stays with the machine. appdata\locallow is even less important. The folders above appdata are user's files and are extremely important. Also, there are hints in the Windows CreateFile API where you can specify access patterns, including one which means "delete upon close."

Unfortunately, most apps don't use these features correctly. But if they did, they could be useful hints to the drive as to how to allocate things.

Are you familiar with the recent judgement against Time Warner Cable over a very similar matter?

Then they are not clearing it out: they are either incompetent or lying. Consider having a lawyer draft a letter referencing this recent judgement. That might help.

As a discussion grows longer, doesn't the probably of every topic increase?

Engine.dll
ExhaustManagement.dll
SteeringBrakes.dll
IRRangeFinder.dll
BackupCamera.dll
CupHolder.dll

I think weilawei really meant to say: "Provide a technical argument for why Node.js is gaining so much popularity." I am not sure if your post does that.

The features you listed are in pretty much every other major language. The book you referenced is a somewhat tongue-in-cheek look at how to use the good parts of a bad language. The conclusion I reach from those points is "yeah, it's bad, but see how people took the good parts and made it useful." Which doesn't really support the argument for why it is gaining popularity on the server-side.

The rebalancing is why a historical comparison is valid. If they didn't rebalance, it would have even fewer companies, and become even less representative of the economy.

If you are looking, the hubble space telescope is HST or 1990-37B. If you want to find more designations, follow the external links in https://en.wikipedia.org/wiki/International_Designator like the NSSDC Master Catalog.

I rarely post to Slashdot unless I have something to contribute, but this time I just have to say:

WOW.

1) I didn't know there was a .space domain.
2) Holy moly that is beautiful.

If they don't sell your friend list to marketing companies, don't display ads offering hook-ups, and don't send invites to play Cow Clicker and Farmville, then I'll sign-up.

It was refuted in the 1970s, not the 200's. It was never a popular theory. No one should doubt Global Warming on the basis that the scientific community switched its stance. It never did: the majority of scientists were saying it was warming all along.

It has been called "climate change" since before 1988, when the Intergovernmental Panel on Climate Change (IPCC) was formed. Today, people act like the name is some kind of knee-jerk defense against the switch between "global cooling" and "global warming" when in fact, there was no name change at all, nor was there ever a switch.

Is it? Or is it like reimplementing code licensed under BSD, and putting it under the GPL? Put another way: Is the API "code?"

agreed.

mod up. That statement, along with the following one, made no sense to me.

I wasn't aware that IPv6 was fundamentally flawed. This sounds more like bad network design or something.