... making further distribution by Sony

or their agents (i.e. YouTube, with Sony still on the hook for the money)

subject to the $150,000 statutory damages penalty.

That is an explicit claim associated with Sony Pictures Movies & Shows. To get that, Sony had to upload content to the YouTube content system saying "I own this content. Anyone matching it is in copyright violation."

This is a very important legal argument to make in court. By submitting content to the system - or to YouTube in a way that would be interpreted as being "Copyright Sony, rights reserved" by the system - Sony knowingly made a claim of ownership.

This both disparaged BlenderFoudation's title and voided their license to distribute the content, making further distribution by Sony subject to the $150,000 statutory damages penalty.

And yet on my Xbox360 I've been able to play games, movies, TV shows, access streaming services and live video for five years. How is that late to the game?

And I've heard a LOT of REALLY BAD ideas.

Most of what has gotten worse in Unix/Linux over the last couple decades has been the progressive hiding of the system admimistration mechanisms - previously built on human-readable text configuratin files - behind GUI configuration interfaces and excessive complexity. (See upstart and systemd for examples of the latter.)

Now they want to bury the kernel error messages in a QR code? That REALLY takes the cake.

The issue with AF447 is that they disregarded *all* instrument readings, not just the ones they were trained to in the event of an air data mismatch. So they never even realised they were in danger, because they didn't think the rapidly declining numbers were true - remember that the descent was 1G, so they didn't even have any feeling of descent, which added to their mistrust of the data they had infront of them.

So as the other poster said, there was nothing to call someone about other than they didn't know what was going on, and they weren't about to admit that to everyone listening.

You must be so warped with hatred, because your posts are starting to become incoherent.

The legal issue of "reasonableness" is well tested, and it doesn't go your way (fortunately). Software cannot wear out, but the Sales of Goods Act is not about forcing an entity to support anything until it wears out, its about ensuring the product lasts for a reasonable period of time - so your car doesn't die catastrophically in two years time, so your fridge doesn't stop working a year from now, so you know that when you invest a significant sum of money into something, it can last a reasonable period of time.

13 years is a reasonable time, as is 6. And the software doesn't stop working after the EOL date, it just won't receive updates, so it hasn't even "worn out".

Its also worth noting that software does not necessarily fall under the Sales of Goods Act, or its amendments - case law in the UK provides for it as a per-case consideration, and not a standard entitlement.

http://www.mablaw.com/2011/03/...

So even "sticking to legislation" shows you to be full of crap.

I'm afraid its actually *you* who is full of shit in this case, as the Sales of Goods Act 1979 and its amendments are precisely what I am referring to, and as I have intimate knowledge of that act and its various legal successes, I can safely say that you are full of bollocks.

The Sales of Goods Act is not meant to cover a product for all eternity, for an indefinite period, until the product actually wears out or for any other purpose than to require a manufacturer to provide a reasonable life span for the product in question. The Sales of Goods Act is not even intended to require a manufacturer to fix bugs or issues past the reasonable period of support, just provide a reasonable period of support.

So lets see what other Operating Systems have endured longer than Windows XP...

Red Hat Enterprise Linux 2.1 - released in mid-2002, died in mid-2009.
Red Hat Enterprise Linux 3 - released in late-2003, died at the start of this year.
Red Hat Enterprise Linux 4 - released in early-2005, dies at the end of this year.

Ubuntu 6.06 LTS - released mid-2006, died mid-2011.
Ubuntu 8.04 LTS - released mid-2008, died mid-2013.

OSX 10.1 - released late-2001, died mid-2002.
OSX 10.2 - released mid-2002, died mid-2003.
OSX 10.3 - released late-2003, died mid-2005.
OSX 10.4 - released mid-2005, died late-2007.
OSX 10.5 - released late-2006, died late-2009.
OSX 10.6 - released mid-2009, died late-2011.
OSX 10.7 - released mid-2010, died late-2012.
OSX 10.8 - released mid-2012, death TBD.

Hmm, I can't see any other consumer or corporate desktop OS that has been supported as long as XP has.

So out of all other reasonable time periods for Operating Systems, XP's support length is definitely an outlier and you would get laughed out of court if you tried to force Microsoft to support it beyond its current and well known EOL date.

If you are giving any sort of legal advice based around the Sales of Goods Act, please fucking stop as you have proved that you know shit about the topic.

99.9999% of all work a fighter pilot does in normal operation is HOTAS - hands on throttle and stick. There are enough controls on those inputs, or within close reach to them, that you can operate the aircraft without ever taking your hands off them.

And while multifunctional displays are a staple in cockpits these days, they are invariably not touch screen in military aircraft.

And that relevance pales into insignificancy when you consider what you would have to replace application wise, as in the real world people dont just boot to a desktop and then sit and stare at it for their working day.

Office applications might be easy to replace, but how about certified xray or MRI viewers, medical record viewers etc?

AF447 never made any calls because the crew didn't have anything to call about, so its hardly a good example - see the Swiss flight over the North Atlantic some years ago that crashed while fighting a fire on board for ages while they diverted, they were making a load of calls about their situation.

In the NHS? A huge amount, since its basically run on third party applications developed for Windows. The last lot that tried essentially what you are suggesting (rewrite the entire NHS infrastructure so its unified) ended up spending well into the tens of billions of pounds before the project was cancelled.

Also, as a UK taxpayer, id prefer my money get spent on solutions that work rather than solutions that play to the idiosyncrasies of the geek/nerd population.

Sorry, thats a load of bollocks - the NHS has had over half a decade to do something about their situation and they failed, so its not the software operator thats at fault here, and any attempt to do as you say could be seen as undue and unwarranted restraint of trade, and open the country up to WTO issues.

UK law requires that a purchase be fit for a reasonable period of time (depending on the item involved, but the maximum time is typically six years), and XP is well past that test - saying the government could force them to open up the source code is laughably incorrect and completely unreasonable, as that would take an act of Parliament itself and be subject to public ridicule.

Plenty of things go out of warranty and support without the requirement that the creator allow anyone to replace them as supporter.

The government is to blame here, not Microsoft, so its only right that the government pay the fine, not Microsoft.

I do not see why TCP and IP could not have been created as single layer.

That was one of the major divergences from other networking schemes of the time that gave TCP/IP an advantage.

IP is a lower layer than TCP. It's about getting the packet from router to router, and is as deep into the packet that core routers have to look to do their jobs. Core routers are supposed to be "as dumb as rocks", putting as little effort as practical into forwarding each packet, in order to get as many of these "hot potatoes" moved on as quickly as possible and keep the cost of the routers down (and to drop any given packet if there's any problem forwarding it).

TCP is one of several choices for the next layer up. It runs only at the endpoints of a link. It does several things, which are all about building a reliable, persistent, end-to-end connection out of the UNreliable, "best effort", IP transport mechanism. Among these things are:
  - Breaking a stream up into packet-sized chunks.
  - Creating reliability by hanging error detection on packets and saving a copy of the data until the far end acknowledges successful reception, retransmitting if necessary to replace lost or corrupted packets.
  - Scheduling the launching of the packets so that the available bandwidth at bottlenecks is fairly divided among many TCP sessions, while as much of it is used as practical.
  - Adding an out-of-band "urgent data", channel to the connection (for things like sending interrupts and control information).
Some other networking schemes of the time did this on a hop-by-hop basis, requiring much more work by the routers. TCP put it at the endpoints only.

If TCP/IP had included crypto, we'd all be using IPX now days...

The reason TCP/IP proliferated was because it was light-weight and easy to implement. Crypto would have killed that.

There would have been more resistance to adopting it, too.

As it was, there was substantial resistance among people and institutions sited outside the US, because the Internet was a DARPA project, i.e. U.S. Military. Other countries, organizations within them, and even some people in the US, were concerned about things like what the US might be building in - like interception and backdoors for espionage and sabotage - or just because "Military! Bad!". Including encryption from the then officially nonexistent, deepest secret, communications spy agency would have boosted that resistance substantially.

With the recent changes, almost all of those in actual control of Microsoft have a significant and continuing coding history, so it really is a case of Microsoft going back to grass roots.