| ▲ | ofalkaed 6 hours ago |
| When this got released I really expected someone in the opensource community to run with it, but as far as I know no one has. Back around 1990 a Graphic designer that had his office n the same building as my mom worked in let me copy his Photoshop 1.x disks and nothing has ever compared to it for me. When will we get the linux port of Photoshop 1.0? I would love to see how it develops. |
|
| ▲ | delaminator 5 hours ago | parent | next [-] |
| If they did, they can only send you screenshots > 2. Restrictions. Except as expressly specified in this Agreement, you may not: (a) transfer, sublicense, lease, lend, rent or otherwise distribute the Software or Derivative Works to any third party; or (b) make the functionality of the Software or Derivative Works available to multiple users through any means, including, but not limited to, by uploading the Software to a network or file-sharing service or through any hosting, application services provider, service bureau, software-as-a-service (SaaS) or any other type of services. You acknowledge and agree that portions of the Software, including, but not limited to, the source code and the specific design and structure of individual modules or programs, constitute or contain trade secrets of Museum and its licensors. |
| |
| ▲ | ofalkaed 5 hours ago | parent [-] | | I was talking about more than just a literal port, running with it is broader than just a literal port. I guess my general point is that I am disappointed that all these releases of historical code have so little to show for being released. Edit: Disappointed is really not the right word but I am failing at finding the right word. | | |
| ▲ | ndiddy an hour ago | parent | next [-] | | What would you expect to happen? Photoshop 1.0 is an almost unusably basic image editor by modern standards. It doesn't even have layers (they were introduced with Photoshop 3.0 4 years later). Even if the code was licensed in a manner that allowed distribution of derivative works (which it isn't), it's written in Apple's Pascal dialect from the mid-80s and uses a UI framework that's also from the mid-80s and only supports classic Mac OS. CHM didn't even release the code in a state that could be usable out of the box if you happen to have a 40 year old Macintosh sitting around. Here's a blog post showing how much work it took someone to compile it: http://basalgangster.macgui.com/RetroMacComputing/The_Long_V... I think Adobe decided to release the code because they knew it was only valuable from a historical standpoint and wouldn't let anyone actually compete with Photoshop. If you wanted to start a new image editor project from an existing codebase, it would be much easier to build off of something like Pinta: https://www.pinta-project.com/ | |
| ▲ | pm215 5 hours ago | parent | prev | next [-] | | I think there's two parts to this: 1) these historical source code releases really are largely historical interest only. The original programs had constraints of memory and cpu speed that no modern use case does; the set of use cases for any particular task today is very different; what users expect and will tolerate in UI has shifted; available programming languages and tooling today are much better than the pragmatic options of decades past. If you were trying to build a Unix clone today there is no way you would want to start with the historical release of sixth edition. Even xv6 is only "inspired by" it, and gets away with that because of its teaching focus. Similarly if you wanted to build some kind of "streamlined lightweight photoshop-alike" then starting from scratch would be more sensible than starting with somebody else's legacy codebase. 2) In this specific case the licence agreement explicitly forbids basically any kind of "running with it" -- you cannot distribute any derivative work. So it's not surprising that nobody has done that. I think Doom and similar old games are one of the few counterexamples, where people find value in being able to run the specific artefact on new platforms. | |
| ▲ | delaminator 2 hours ago | parent | prev [-] | | you literally said: > When will we get the linux port of Photoshop 1.0? |
|
|
|
| ▲ | LollipopYakuza 2 hours ago | parent | prev | next [-] |
| I understand it was a very unique and powerful piece of software in 1990 but why would it be such a game changer to have the 1.0 running on Linux today? |
|
| ▲ | msk-lywenn 5 hours ago | parent | prev | next [-] |
| The source is now readable but it’s not open source at all. |
| |
| ▲ | bromuro 4 hours ago | parent [-] | | It is open source but not free software. | | |
| ▲ | chongli 4 hours ago | parent | next [-] | | No, it’s source available but not open source. Open source requires at minimum the license to distribute modified copies. Popular open source licenses such as MIT [1] take this further: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This makes the license transitive so that derived works are also MIT licensed. [1] https://en.wikipedia.org/wiki/MIT_License?wprov=sfti1#Licens... | | |
| ▲ | sigseg1v 2 hours ago | parent | next [-] | | Not quite. You need to include the MIT license text when distributing the software*, but the software you build doesn't need to also be MIT. *: which unfortunately most users of MIT libraries do not follow as I often have an extremely difficult time finding the OSS licenses in their software distributions | |
| ▲ | aeon_ai 2 hours ago | parent | prev [-] | | MIT is not copyleft. The copyright notice must be included for those incorporated elements, but other downstream code it remains part of can be licensed however it wants. AGPL and GPL are, on the other hand, as you describe. | | |
| ▲ | chongli 15 minutes ago | parent [-] | | Modifications can be licensed differently but that takes extra work. If I release a project with the MIT license at the top of each file and you download my project and make a 1-line change which you then redistribute, you need to explicitly mark that line as having a different license from the rest of the file otherwise it could be interpreted as also being MIT licensed. You also could not legally remove the MIT license from those files and distribute with all rights reserved. My original granting of permission to modify and redistribute continues downstream. |
|
| |
| ▲ | ptx 41 minutes ago | parent | prev | next [-] | | Open Source is the same thing as Free Software, just with the different name. The term "Open Source" was coined later to emphasize the business benefits instead of the rights and freedom of the users, but the four freedoms of the Free Software Definition [1] and the ten criteria of the Open Source Definition [2] describe essentially the same thing. [1] https://www.gnu.org/philosophy/free-sw.en.html [2] https://opensource.org/osd | |
| ▲ | Xerox9213 4 hours ago | parent | prev | next [-] | | It’s is “source available” but not open source. | |
| ▲ | cgfjtynzdrfht 4 hours ago | parent | prev [-] | | It's "source available" [1], not open source [2]. Words have meaning and all that. 1: https://en.wikipedia.org/wiki/Source-available_software 2: https://en.wikipedia.org/wiki/Open_source | | |
| ▲ | nothrabannosir 14 minutes ago | parent | next [-] | | > Words have meaning and all that. Ironic put down when “open source” consists of two words which have meaning, but somehow doesn’t mean that when combined into one phrase. Same with free software, in a way. Programmers really are terrible at naming things. :) | |
| ▲ | geokon 3 hours ago | parent | prev [-] | | cant blame him. We're in a bit of a bananas situation where open source isnt the antonym of closed source | | |
| ▲ | jefftk an hour ago | parent [-] | | This isn't that uncommon: * If a country doesn't have "closed borders" then many foreigners can visit if they follow certain rules around visas, purpose, and length of stay. If instead anyone can enter and live there with minimal restrictions we say it has "open borders". * If a journal isn't "closed access" it is free to read. If you additionally have permissions to redistribute, reuse, etc then it's "open access". * If an organization doesn't practice "closed meetings" then outsiders can attend meetings to observe. If it additionally provides advance notice, allows public attendance without permission, and records or publishes minutes, then it has “open meetings.” * A club that doesn't have "closed membership" is open to admitting members. Anyone can join provided they meet relevant criteria (if any) then it's "open membership". EDIT: expanded this into a post: https://www.jefftk.com/p/open-source-is-a-normal-term | | |
| ▲ | denotational an hour ago | parent [-] | | * A set that isn't open isn't (necessarily) closed. * A set that is open can also be closed. |
|
|
|
|
|
|
| ▲ | ofrzeta 4 hours ago | parent | prev | next [-] |
| You could try having an LLM port it to Linux :) As an aside I was always (well, no longer) hoping that Photoshop gets ported to Linux because at least an IRIX port existed, so there has to be some source code with X11 or whatever library code. https://fsck.technology/software/Silicon%20Graphics/Software... |
|
| ▲ | gwbas1c 2 hours ago | parent | prev [-] |
| What about GIMP or any of the other open source image editors? Just supporting a modern OS's graphical API (The pre-OSX APIs are long dead and unsupported) is a major effort. |