The canonical way of solving that would be to have a unique code, an "international standard artist number", for each artist and a tag that can hold multiple artist codes.

This might be useful: http://www.isni.org/

Yeah, I'm sure there are plenty of people who do like to control their tags themselves.

The tried and tested way to solve this sort of conflict would be for tags to have namespaces. That way your music files could have multiple sets of tags. Your music player could then be configured to either look for a single namespace, or to use some algorithm to merge multiple namespaces.

Wow, I guess that means that more than half of all advanced computer users that I encounter in my day to day life must have machined their own custom laptops to look just like Macbooks!

No, but seriously, many advance users do not care to have advanced control over their music library.

Many advanced users unwittingly had Itunes destroy their music organization about a decade ago when they switched from Winamp to Itunes. They swore about it for a while, then accepted that Apple controls their music folder now and that having advanced control over your music organization is nice, but not essential. If we turn off our RDF deflectors temporarily we might even think of it as a feature. Remember what a time sink music file organization used to be.

It sure doesn't look anything like the concept art that Nintento released back in those days. I'm pretty sure the SNES had an expansion port on its bottom. The idea was that you would mount your SNES on top of the SNES-CD / Play Station unit.

Console ad-ons have rarely had much success, which makes me doubt that that either company was ever very serious about launching the product. If they were serious about it they would probably ultimately have launched a standalone console that could play both CD and cartridges instead of a CD ad-on for the SNES.

The next major US coal disaster is just coal plants operating as designed on July 2.

Based on Elon's cryptic comment on Twitter I think you might perhaps be on to something.

"There was an overpressure event in the upper stage liquid oxygen tank. Data suggests counterintuitive cause."

Sounds to me like "the vent on the second stage oxygen tank was venting too fast and / or not smoothly enough".

I watched SpaceX's own feed. The cameras kept on the vehicle for the duration of the failure and kept tracking some larger pieces of first stage debris for several seconds after it exploded. Beyond that point there would not be any large pieces of vehicle left to look at, except perhaps for the Dragon spacecraft which looked relatively intact.

I for one doubt that they did manage to get a camera on the Dragon before it crashed into the ocean.

Yeah, it could be the grind fins.

It could also be condensation caused by under-pressure caused by the humps (the solar panel covers) on the Dragon.

If you pause the video at 3:16 you can see a tiny white dot on the second stage. I don't think that dot is suppose to be there (unless it's the sun reflecting off something shiny or something). Fuel / oxygen tank leak?

Here's a gif of the failure: http://imgur.com/SYwUIbI

Looks like:
1. Second stage comes apart in a cloud of oxygen and fuel.
2. Dragon spacecraft falls off / gets overtaken by first stage.
3. First stage is destroyed.

He also posted a gif: http://imgur.com/SYwUIbI

Looks like the Dragon did "fall off" too. Of course, it would always do that if the second stage was destroyed.

Looked to me like the second stage burst into pieces and the first stage was destroyed seconds after. I think that white stuff that seemed to come off before the first stage blew up was probably a cloud of cold oxygen from the second stage oxygen tank.

Maybe they should investigate why they have problems with code merges first. Having everyone bunch up in front of one editor seems like a workaround that does not get at the root cause of the problem.

If you use reasonably loose coupling between software components and define interfaces between components before you start writing them and have one and only one programmer work on each component or sub-component between merges you will only have problems with merges if and when someone makes a mistake.

People who aren't interested in VR may be interested in augmented reality, like the stuff Magic Leap is developing.

VR has proven to be useful for things like training soldiers and experts in other fields, but it's not clear that it'll be useful for anything else. AR is pretty much guaranteed to be useful if it will work, because augmenting reality is pretty much useful by definition.

Yes, but the decimal time system actually had reasonably long seconds, they were 0.864 seconds long by our way of counting. Most people count slightly faster than 1 count per second (hence the old one thousand and- counting trick), so having shorter seconds would probably be good for counting.

I don't know how well we would adjust to having only 10 hours in a day, though. That would make business hours only about 4 hours long, which would make it impossible to schedule many appointments at precise hour or half-hour times.

I'm also no too sure about having 10 months in a year, especially in cultures that recognize four seasons.