Welcome, Guest. Please login or register.

Author Topic: Consequences of the AmigaOS 3.1 source code "leak", one year after?  (Read 36884 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Quote from: Pat the Cat;818803
But it can't legally state "Do not translate". :)


Depends, some places class the translation as a derivative work and that permission needs to come from the copyright holder in the first instance. Places like the US where the source code is copyrighted.

Back OT, I think we can see what the consequences of the source code release have been - apart from random Amigans arguing about it and getting their post counts up - nothing.
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #1 on: January 03, 2017, 02:22:58 AM »
Quote from: Pat the Cat;818806
Nope. You cannot legally prevent translation.


Of course you can, read your EULA.

Quote from: Pat the Cat;818806

Even worse, if you could demonstrate the new version was a substantial improvement, you could counter claim for malicious prosecution...


What a load of crap. Improving something you've violated the copyright on doesn't give you any extra rights and admitting it makes you an even bigger target, ffs.

Quote from: Pat the Cat;818806

Who can claim that a new WB3.1 derivative is going to hurt them, financially?


Whoever owns the copyright..
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #2 on: January 03, 2017, 02:59:44 AM »
Quote from: Pat the Cat;818818

But it wouldn't be violating the copyright of the C code.


You don't violate the copyright of the C code, you violate the author's rights.

Ok, this thread has done one thing - it's brought the nutters out of the wood-work who have no idea about copyright.
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #3 on: January 03, 2017, 03:15:16 AM »
Quote from: Pat the Cat;818824
Well, I think you're a snotty nosed little tosser who couldn't find his dick without a map, a microscope, and some tweezers.


All good Pat, I had your momma helping me the other night, so I'm happy to call it even..


.. and at least I understand copyright law.
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #4 on: January 03, 2017, 10:43:20 PM »
Quote from: kolla;818878

Wrong, it has _nothing_ to do with open source, it's just not the goal of certain popular Linux distributions.


And the need some people have to "upgrade". If you've got a working system that does everything you want, why would you want to upgrade and potentially break things. Just to whinge about how bad open-source is?

This is universal, it applies to open-source and closed-source environments.

It's why people have old DOS boxes still hanging around, or Amiga's controlling heating systems, or C64s controlling machine tools..
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #5 on: January 04, 2017, 01:30:17 AM »
Quote from: Thomas Richter;818917

Because then somebody else will break the machine for you. Seriously, if you connect a system to the internet today, and you do not keep the system up to date, then you're soon running into trouble.


Not every machine necessarily needs to be connected to the internet :-)

Quote from: Thomas Richter;818917

That's again the experience over and over again - which of the two models is more satisfactory *for you* is then of course another question.


Of course, and in my experience I've seen the most computer-illiterate people use Linux on a daily basis without any of the hassles you're describing. Upgrades and all that mess as well. These people are nowhere remotely close to what anyone would describe as a "developer".

If I really wanted to mess with them, I'd give them an AmigaOS 3.1 machine ;-)
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #6 on: January 04, 2017, 10:35:35 PM »
Quote from: EugeneNine;819046
Same finger pointing issue I run into I bet.  Bought my wife a laptop with windows 8.  It got a forced upgrade to 10.  Dell says its Microsoft's fault, Microsoft says since it was an OEM windows originally its Dells support issue.  Meanwhile wife can't print on legal size or use headphones.


That is the "ease of use" that open-source can't possibly achieve, rotfl.

The die-hard fanatics on either side are completely blinded by their own belief in their One True Way. Thing is, software and hardware is bloody hard to get right when both are static but when one of them keeps changing underneath you the end-user has almost no chance of getting it right.

You've just got to shake your head at those who blame everything on "open-source".
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show all replies
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #7 on: January 04, 2017, 10:43:43 PM »
Quote from: kolla;818992
So... woop woop for compatible closed source drivers from Microsoft.


rotfl, the Win10 upgrade on my mother's ASUS ended up making the audio beep every few minutes. The "official" recommended methods of stopping it was to a) not upgrade to Windows 10, or b) uninstall the drivers for the sound card. Good fun.