Wrong. FDM is used commercially to produce parts - including airplane parts. (I know, because one of my (OpenBeamUSA.com) vendors is printing cosmetic trim pieces for the Airbus A380). Commercial systems have no problem with overhang because they use a water soluble support system. And if you want something prototyped out of production representative material, it is one of the faster (and hands off) way to do it. I've used FDM for Ultem, Polycarbonate and ABS parts before.

The reason you don't see this in the hobby market, is because Dimension's patent on water soluble support, and heated build chamber, is valid until 2014 (or 2016). That's why there is no hobby grade 3D Printer on the market that is completely enclosed and they only have a heated bed. Most people enclose their printers if they are printing with ABS for a variety of reasons.

-=- Terence

Except that, according to the article, that was exactly the problem: Google Maps would expire mid-next-year. Which meant either they'd have to sign another contract — and I would be *stunned* if, in such a situation, Google didn't demand Latitude be included or some other sort of data-collection concession — or have Maps go dark *during* iOS 6's lifetime, requiring Maps to be replaced in a point-release, rather than changing over at a major OS release.

Whether or not I think this was a great decision, I can totally see why they made the move now from a business aspect. Imagine if they had done this changeover in iOS 6.2...

Renault and Nissan came up with the Quick-Drop battery swapping system that another poster mentions in regard to the Fluence ZE, though Nissan doesn't use it for the LEAF platform; the LEAF battery packs *can* be swapped out fairly easily, but it's not set up for the Quick-Drop method. Tesla originally talked about offering battery swaps at their Supercharger locations, but I think that's fallen by the wayside.

Honestly, with so many different battery capacities — the LEAF has 24kWh worth of batteries, while the highest-end Model S has 80kWh — I think standardization would be hard. I mean, we can't even fully finalize on a quick-charging standard!

In Japan and France, they have a system called CHAdeMO, a large plug capable of delivering up to 62.5kW of charge and thus charging the LEAF from near-empty in about 25 minutes. Japanese EVs and a number of European ones use this as a charging connector.

Meanwhile, the US came up with SAE1772, a replacement for older charging standards, with a smaller plug but which is limited to about 6.6kW of charge at 220V, meaning they can be installed many more places but take hours to recharge. (These are the little stations in many parking lots, for 'charge while you shop' at a mall or whatever.) Given the differing standards, various cars released in the US — the LEAF, the MiEV, etc. — support J1772 for slower charging and CHAdeMO for fast charging. And so CHAdeMO quick chargers have been put in along freeways.

Now SAE has come up with a variant on SAE1772 — a bigger form of the plug with the original plug as a subset of the design — which could allow quick-charging. The idea being that you'd only need one plug; the new SAE1772 variant sockets could use the old plugs, so older charging stations would work, but you'd have to have new sockets for any new plugs. However, no one's committed to supporting that yet that I've heard.

Then Tesla, disgusted with everyone else, designed their own Supercharger system which charges at up to 100kW — heavier duty than CHAdeMO — so that they can charge the 80kW pack of a high-end Model S much faster. They made adapters to allow SAE1772 charging too, for all the little parking lot stations, but there's no easy way to convert CHAdeMO for those quick chargers.

Standardization among EVs is... well, we still have a way to go.

Posted also on the Kickstarter comment section:

Kickstarter project creator here: I'm the guy behind OpenBeam (http://www.kickstarter.com/projects/ttstam/openbeam-an-open-source-miniature-construction-sys).
And in case anyone's wondering - we shipped the majority of our rewards a *month* before the original promised date. That probably puts me in the top 5 percentile of projects...

Let's take a look at the new rules one by one:

“What are the risks and challenges this project faces, and what qualifies you to overcome them?”

- Okay, this is perfectly valid. I am surprised KS haven't done this earlier, because there are quite a few clueless guys (http://www.kickstarter.com/projects/277210494/paint-be-gone) - *(http://www.kickstarter.com/projects/277210494/call-key) and http://www.kickstarter.com/projects/277210494/key-pad-case) out on here who seems be doing the "throw s*** at the wall and see what sticks" model of development.

"Product simulations are prohibited. Projects cannot simulate events to demonstrate what a product might do in the future. Products can only be shown performing actions that they’re able to perform in their current state of development."

"Product renderings are prohibited. Product images must be photos of the prototype as it currently exists.
Products should be presented as they are. Over-promising leads to higher expectations for backers. The best rule of thumb: under-promise and over-deliver."
Okay, so KS want a working prototype. I get that; that's pretty straightforward. But it doesn't stop someone from *faking* a prototype on camera. This however, won't stop a project like iCase (http://www.kickstarter.com/projects/1791911961/i-case-iphone-4s-and-iphone-4-bumper-case) from being a train wreck, as the protoytype would likely have been SLA, painted, and the problem wouldn't have been apparent until the metal parts were CNC machined and fitted and found to short out the iPhone's anntenna.

The OpenBeam project would have passed these requirements; we had a physical prototype for shooting the video, as part of a good product development practice.

"Offering multiple quantities of a reward is prohibited. Hardware and Product Design projects can only offer rewards in single quantities or a sensible set (some items only make sense as a pair or as a kit of several items, for instance). The development of new products can be especially complex for creators and offering multiple quantities feels premature, and can imply that products are shrink-wrapped and ready to ship."

And how would KS define "Multiple copies" of a reward? This I have a problem with. When you're in production, you are trying to get the manufacturing volume up to bring the costs down. If I were launching OpenBeam now, would I be limited to selling one stick of aluminum and one of each bracket to my backers (who wouldn't be able to do anything useful then with this?) If I packaged it up as a "kit", like I had on my KS, would I have gotten around these restrictions? Who decides whether multiple copies of the same item is required for the item to work (ie, construction toy kit), and when it becomes a way to side step your rules? How much "individual judgement" is there to allow the listing of a project, and do you consider the project creator's background (ie, having successfully delivered on a previous project) when you allow them to post? With the amount of controversy about what gets allowed (*cough* Tangibot (http://www.kickstarter.com/projects/mattstrong/the-tangibot-3d-printer-the-affordable-makerbot-re)*cough*) and what doesn't on Kickstarter already, this rule is probably going to make your selection process more Apple App-store like (arbitrary with no recourse for the project creator if you are not selected).

(Edited to add: The real problem, that KS probably don't want to admit, is that none of their hipster workers have a sufficient engineering / science / technology background to effectively monitor and approve Kickstarter projects to begin with. That's why they let stupid shit like Z-Torque (http://www.kickstarter.com/projects/1202837765/z-torque-bicycle-cranks-ride-faster-longer-easier?ref=live) in, but plenty of GOOD projects get rejected).

-=- Terence

If I'm reading the news articles properly, available evidence actually indicates the protesters themselves were peaceful and the protests got used as cover for violence by extremists. Some articles suggested that this was a 9/11 'reminder' planned anyway, and the protests over the film just provided a convenient cover for them to get into place in a crowd.

Sadly, the lunatic fringe is often what a group gets judged by, which is hardly unique to Islam; many people also judge Christianity by groups like the Westboro Baptist Church or the Christian groups who bomb abortion clinics. Heck, the same is true of political parties or — to use a more Slashdot-relevant example — OS platform advocates. The loud lunatic ones end up being the voices outsiders notice the most readily, because they're shouting and starting fights.

As a result, the story many take from this becomes not, "Violent lunatics seize on convenient excuse to thinly justify their attacks" but "ZOMG YOU GUYS, MUSLIMS ARE CRAZY-VIOLENT." Which is unfortunate.

...that this would affect a lot more than just Apple if upheld. I understand Google's got a small interest in touch-based devices, too, and I seem to recall that Microsoft's considering maybe supporting some of this 'touch' stuff in Windows 8. (Sarcasm tag heavily implied there, which was hopefully clear.)

Seriously, I feel that patents have become sort of like nuclear weaponry; you either try to amass enough weapons in your patent portfolio that the other side won't launch, as with mutually assured destruction between the big companies, or else you get held hostage by patent-troll terrorists who get ahold of a weapon and threaten to take out everything they can unless you pay them. Maybe we need the patent law equivalent of Jack Bauer to deal with patent trolling. :P

I'm afraid that IBM beat you to this by several years, as they patented patent trolling back in 2007. Your technique is not precisely the same, but it would probably infringe on their patent...

No, Skyhook's definitely not the technology under the hood. In fact, Motorola replaced Google's built-in geolocation with Skyhook on their Android handsets, but Google pitched a fit about this. And so Motorola dropped Skyhook again and returned to Google's geolocation system, and Skyhook sued Google.

Japan never used to have power outages to speak of, but in the wake of the tsunami and Fukushima Dai-ichi being taken offline, outages are heavily on the mind of the average Japanese citizen. They had a ton of blackouts in March, and the Tokyo area in particular has been engaging in a ton of power-saving measures; the article from the summary even mentions a few (dimming subway station lights, to draw less power, for instance). Given that everyone's looking for ways to reduce their draw on the power grid at peak times, I'm not surprised that Nissan is looking into this possibility.

www.facebook.com's AAAA record resolves to 2620:0:1cfe:face:b00c::b -- however, most folks can't resolve it. According to posts on the ipv6-ops mailing list, Facebook is still doing IPv6 in a limited testing phase, so they have DNS whitelisting enabled to avoid folks other than Hurricane Electric IPv6 testers getting the AAAA record while the IPv6 version of the site is still not quite there yet.

Presumably they'll turn off the whitelisting and let it resolve universally for IPv6 Day.

No, Android stores the last 50 unique cell-derived locations (in cache.cell) and the last 200 unique wifi-derived locations (in cache.wifi). In other words, the file /is/ truncated, but based on quantity of data rather than age/time. Apple's logfile is not truncated, whether by design or programming error.

Conversely, Apple's log remains on the device only for Core Location caching; it's stored in iPhone backups, but isn't ever sent back to the mothership (at least so far as anyone has been able to tell). Google truncates the log, but does send the data when you hit a WiFi point and have a GPS signal; they use this to update their WiFi location database for GPS assist, as they use their own service rather than Skyhook. (If your base station advertises itself, open or otherwise, go to http://samy.pl/androidmap/ and enter your local router's MAC address; you can see where Google thinks that base station is, based on how Android devices have paired your station to their GPS data.)

Some of that may be due to the fact that Apple charges a lot less -- a LOT less -- for OS upgrades than Microsoft does, and some of it may be due to the fact that OS X is a lot less likely to be heavily tied into some company's corporate network than XP was.

Either way, you're still correct that no company can be expected to support an older OS forever. As was noted elsewhere, RedHat's long since retired support for many versions of their software, and no longer roll RPMs to update various things based on older systems.

Honestly, "YourSQL" seems more accurate than "MySQL" given that apparently even the developers can't keep control of their own database. ;P

In fairness to Gates, he's willingly given away something like $39 /billion/ dollars of his own money through philanthropic and charity efforts. Even as a stockholder in MS, I doubt he cares much about $1.2 million. But there were probably some chairs thrown in Ballmer's office...