In fact, Samsung internationally hasn't been on the winning side - they've instead been stirring up shitstorms of controversy. Because what patents Samsung does assert are ones under FRAND, and it's lead to many a jurisdiction doing inquiries about asserting FRAND patents in this fashion, including the EU and Korea.
That's actually the bigger problem with everything that's been going on that supersedes Apple and Samsung. The total market value of a FRAND patent must exceed the total market value of a non-FRAND patent. The FRAND patent may have lower royalties per device, but it makes up in volume what it lacks in price. If the total value of a FRAND patent is less than a non-FRAND patent, then you've just destroyed all incentive for anyone to submit their patents under FRAND. Why in the world would anyone decrease the value of their patent by submitting it under FRAND?
Unfortunately this is precisely what was happening with Samsung losing because their patents were FRAND. The courts were getting lost in arguments over minutia and losing sight of this bigger picture. FRAND patents were being devalued relative to regular patents. The difference in pricing Apple was asking for (a few cents per device for FRAND, vs $15-$20 per device for regular patents) would've required FRAND be applicable to hundreds of times more devices than a regular patent before they'd be worth it. In other words, almost never worth it - a single licensing deal with a manufacturer with more than about 0.3% market share would've guaranteed keeping the patent non-FRAND was more profitable. It was setting us on course for a tech world where everything was proprietary and non-interoperable. That they've decided to drop all litigation before more damage was done is great news.
I am assuming that the answer is simply that they had to manually paint in the parts of the photos that were revealed when other parts were removed.
If you've used a recent version of Photoshop, their content-aware fill often does an amazing job at automatically filling in hidden backgrounds.
Everyone developing FOSS wants to do all the fun programming stuff. But no one wants to do the boring hard work of documentation, UI polishing, promotion/marketing, etc. That's why FOSS tends to suck in those areas compared to the commercial stuff (where they actually pay technical writers, designers, marketers, etc.)
Let me present an alternative hypothesis. There are plenty of technical writers, designers, and marketers out there interested in and using FOSS. They'd probably be more than happy to contribute to documentation, UI polish, and promotion just as programmers are happy to contribute to development. The problem is the FOSS developers won't talk to these guys, brushing them off with "if it's that important to you, figure it out yourself noob!"
The problem is a lack of respect for those who aren't programmers, including users. Commercial software developers respect users because the users are the ones who ultimately pay for the commercial developers' paycheck. One of the unintentional side-effects of the unpaid FOSS philosophy is the lack of a need to respect the users. Whether or not your FOSS project lives or dies depends on how many programmers contribute to it, not on how many users use it.
Services that people need in order to live - energy, water, medical - shouldn't be on the free market. All that stuff should be publicly owned and the goal shouldn't to be to make money but to provide critical services to the people for the cheapest amount possible.
Services that people need in order to live should start off on the free market. Once it becomes clear which method of providing the service is most efficient, then it should be transitioned to a publicly-owned service. e.g. What's the best way to provide fresh water? Wells? Desalination? Buy it from your neighbors and pipe/truck it in? The answer to that isn't at all clear and is constantly changing, so you need market forces to indicate to you the best (cheapest) method of acquiring fresh water. Distribution OTOH tends to be more static - there aren't any up and coming new ways to send water through pipes. So laying down and maintaining pipes is more amenable to a public service.
GSM is a good example of the trouble you can get yourself into if the government prematurely decides something should not be subject to market forces. The EU mandated all wireless phone carriers adhere to GSM. The U.S. did not. Consequently a different method of transmitting phone calls and data - CDMA - was also tried in the U.S. CDMA turned out to be superior to the TDMA used in GSM, particularly when it came to data services (TDMA divides bandwidth equally between users, even if they aren't using the bandwidth; CDMA bandwidth effectively gets allocated as needed as a side-effect of how the technology works). And eventually CDMA was incorporated into the GSM standard (most HSPA and HSDPA implementations use wideband CDMA - yes your GSM phone uses CDMA). If the U.S. had gone along with the EU and required GSM, data services would've been several years behind where they are now, and we'd probably still be stuck at around 1 Mbps cellular data speeds.
The distinction needs to be based on the size of the technological solution space and the uncertainty over the best solution - factors which are inherent to the technology required to provide a service. Not based on whether or not those services are necessary for life - a factor completely independent of the technology needed to provide the service. Once you realize this, you realize that other things not necessary for life should probably be publicly owned - e.g. cable TV lines. When cable TV first began, it wasn't at all obvious what was the best way to distribute high-bandwidth content to houses. But now it's pretty clear that fiber to the home is the end-game. So the government should be installing fiber to each home, then allowing multiple cable TV vendors to compete selling service over that fiber.
Logan -> Blue line -> Orange or Green Line -> Red line -> Kendall/MIT
How hard is that?
Three transfers on the T (there's also a bus you have to take from the Logan T station to your airline terminal) is hardly ideal when you're hauling around luggage with kids in tow and on a schedule. When I was traveling by myself with a single suitcase I'd do the three transfers. But outside that case, a taxi is just easier and quicker.
The meters on traditional cabs may sometimes be tinkered with, but that's illegal, and in the vast majority of cases they're accurate and legally binding. Whereas with the new wave of rideshare apps there's no indication of what charges you're reacking up until you arrive.
There's another way to tinker with meters besides hacking them - drive a different route. My first taxi ride from Boston Logan to MIT took what seemed like an unusually winding route through downtown Boston. A year later when I got a car and began driving around the city myself, I realized I'd been taken for a ride, literally. I mentioned this to a fellow student at my lab, and he remarked that it had taken him 3 years to figure out what the actual cost of a cab from his apartment to the airport was, because every time he'd be taken on a different, circuitous route to rack up extra miles. It was 3 years until he actually got an honest driver who took him straight home.
Modern navigation software means you can get an exact distance from start point to destination before you even step into the taxi. There's no need for a meter (other than to time the ride). A lot of airport taxis already do this for longer rides - they charge based on zones, with further zones costing more. No meter needed. The only case this doesn't handle is rerouting to avoid traffic. An alternative might be a meter which prints out your GPS route so you can see that you were taken almost straight to your destination, and not in circles.
Crazee Edeee, his prices are INSANE!!!