I don't know that open sourcing Java killed Sun. More likely it was Intel coming close enough to SPARC performance at a lower price, and Linux coming close enough to Enterprise reliability also at a lower price. But it's certainly true that open sourcing Java and Solaris didn't save Sun.
Likewise, open sourcing Mozilla didn't save Netscape. In fact, I would bet the vast majority of companies that start out proprietary before deciding to open source ultimately die because they're already unhealthy and doing it as an act of desperation.
If a company isn't designed from the start to support an open source model, it's very hard to make the transition and survive. And we have no right to demand they try. Just like everyone should respect the license F/OSS authors choose, everyone should respect Wolfram's right to stay proprietary.
Of course it's also important to remember that proprietary software vendors are more likely to yank the carpet from under their users without warning. Instead of demanding the vendor open source, users should just find and support open alternatives.
I think that was part of the point - let people run their existing applications on Sun hardware. Yes it was more expensive but it was also more capable. Emphasising running on lots of smaller 'commodity' instances wasn't yet the done thing at the time.
Sun was riding high on the dotcom era where every new company ran out and bought an E10000, and maybe one with less specs for a development server. I've heard stories of these being shipped before payment just so they could declare the sales early -- once the bloodbath started, it Sun was left holding the bag.
BSD and Linux on commodity hardware killed everything at Sun and Java really had nothing to do with it.
It's never worth saying this on HN. "downvoted" has temporal dependence, and so right now, for example, the comment you're replying to is not at net-negative. Just comment on what they said, not on how other HN readers are voting what they said.
Even your more qualified point has loads of counter-examples, that companies that did not start with their software as open source find it hard to succeed at open source: Google's search engine and much other software is not open source. Many companies mix their approach to open source with proprietary systems and products. As did Sun.
That Wolfram's justifications are weak is not necessarily a knock on their decision. But the specific point that "High-level languages need more design than low-level languages" seems particularly odd. There are high level languages where all the widely used implementations are open source and few cases of them becoming chaotic. I suppose there is survivorship bias in that observation but there are also obvious reasons why no language user community would have a lot of patience for a proliferation of variants.
This doesn’t make a good argument that Microsoft is evil, so Silicon Valley created a mythology in which Netscape failed.
Netscape did not bet on open source. It didn’t fail. And the browser has a de facto monopoly anyway in the form of Chrome.
AOL bought Netscape (with stock) and the founders, Clark and Andreesen liquidated their Netscape stock. So did the investors. So did vested employees such as Zawinski.
Or to put it another way, if Netscape failed, then so did Viaweb. I don’t think the YC founders would describe Viaweb that way.
As a product, Firefox is still around. And Netscape disappeared in large part as an unsuccessful ground up rewrite as the brand continued following the company sale.
Bitcoin is not a company. Participants had different objectives. Those whose objective was to hold had success. Those whose objectives were political perhaps less so.
Entrepreneurs are in it to make money. Exits are how startups do it.
Telecom, oil, steel, and automobiles are state industries. Even if political correctness often demands pretending they are not…it wasn’t called the arsenal of democracy for nothing.
https://news.ycombinator.com/item?id=29605638
And to be clear I would like an open source Wolfram -- in fact it's almost a requirement before I spend the effort to learn it! (I have never learned a proprietary language outside of work or school)
I just think it's obvious why it's not open source -- because they have a working and sustainable business model! And on the other side, I think it's great to actually pay for what you use, rather than having something free that's filled with dark patterns or irrelevant ads, etc.
It's a hard problem, and it's obvious that we still don't know the answers :)
I don’t see them making that argument in all these points.
For example they say
> Crowd-sourced decisions can be bad for you
Well ok that’s a valid point so… don’t do that. Crowd sourcing design decisions or code is not a fundamental part of open source. You can have open source but do all the development internally if you want to.
I think they’re confusing source licensing with a development methodology.
Which is why as nitpicky as it sounds, we should really be making an effort not to use the term "open source" to refer to both.
Something is Open Sources if the code is published under a license that grants the user the right to study, change and redistribute to anyone and for any purpose.
There is other similar things, like source available, or stricter subsets like Free Software. And there is many things associated with open source, like collaborative development in public, community building and so on.
This is certainly not a universally accepted definition. ‘Open source’ has long been a generic term for any situation in which the source is available. People may want it to be a term of art with a technical definition, but that isn’t how it is used in general.
That's how some people define open source. Other people use it to mean being able to see the source.
There is absolutely no reason to have any doubt about the true meaning of the term when this definition is on every search result on Googles first page, in Wikipedia, when it's that name of a non-profit that defines it like that and when the page that literally is called opensource.org defines it like that.
This is not about owning a term, it's simply about the fact that term had a definition that people agree on. The fact that some people don't know about that definition or that some people don't agree with it doesn't change it.
Lol how is it 'official'? Who officiated it?
The folks who coined the term were among those that led the OSI.
> The “open source” label was created at a strategy session held on February 3rd, 1998 in Palo Alto, California, shortly after the announcement of the release of the Netscape source code. The strategy session grew from a realization that the attention around the Netscape announcement had created an opportunity to educate and advocate for the superiority of an open development process.
> Two of those present at the Palo Alto meeting (Eric Raymond and Michael Tiemann) would later serve as presidents of OSI, and other attendees (including Todd Andersen, Jon “maddog” Hall, Larry Augustin, and Sam Ockman) became key early supporters of the organization.
These folks went on to create the Open Source Definition: https://opensource.org/docs/osd
The folks who created the term started an organization named after the term, created an official definition, and registered the domain. If that's not enough for us to have an official definition, what does it take? And what do we gain by arguing about this? Reading your posts in this thread (and elsewhere), my impression is that you're invested in insisting that "open source" doesn't have that definition, but I can't figure out what your motivation is.
FWIW, my motivation is to create an environment where terms have precise meaning so we can discuss complex issues (like copyright, licensing, development models, etc.) effectively. If we're wrangling over terms and language all the time, communication becomes much more difficult.
You can see the term gaining popularity prior to 3 Feb 1998, and there are references to for example BSD being 'open source' as far back as 1990.
https://books.google.com/ngrams/graph?content=open+source%2C...
Martin's article pleads with readers not to be pedantic when using the term, but offers no alternative definition, beyond 'let people use it when they can read source code'. Perhaps that's the proposed usage you and Martin prefer?
If I'm understanding your position correctly, perhaps you would agree that Ocarina of Time has now been released as open source?
https://arstechnica.com/gaming/2021/11/reverse-engineering-t...
If so, the term is uselessly vague, as it says nothing about the rights of the licensee. In this sense, 'Free Software' has much more meaning...perhaps RMS was onto something!
If the OSI picked a term that wasn't simply descriptive they could trademark it, then they could enforce their definition and there would be no ambiguity. That would be better for everyone.
“Open source” has older non-software uses, most notably in the intelligence context, where it picks up sharply in the 1980s:
https://books.google.com/ngrams/graph?content=open+source+in...
I'm a suspicious, cynical person, so I think that's deliberate.
Conflation is a very useful rhetorical trick.
The name Sun Microsystems is one that I, and most people, associated with microsystems - with workstations (and servers). Sun was founded in 1982 with Bill Joy as a founder, who was already a renowned programmer from CSRG. Andy Bechtolsheim had an exciting hardware design. Vinod Khosla and Scott McNealy risked starting a new company, and had enough chops to manage it into a success. Sun IPOd in 1986. Sun almost bought Apple right before Java was released.
Java was released in 1995. Sun Microsystems already had over a billion and a half dollars in revenue a quarter, which was pretty good at the time.
One reason for Java was protective - Sun wanted a language people could run on workstations and servers that it had some say over. A free, open source language was part of that, it helped in its adoption. Java was more of a defensive move, that Sun wouldn't be locked out of some kind of language ecosystem controlled by Microsoft or Netscape or other companies.
Sun wasn't a software company, they were a hardware company that released a product to defend their hardware from being locked out of competitor's ecosystems. They also weren't in a position to put out a computer language and force programmers onto it, being free and open source, and the ability to run on multiple platforms helped in its acceptance. Being able to run on multiple platforms was the whole point, they didn't want people to get locked into the Microsoft ecosystem with the release of NT 3.51 etc.
Sun and its peers declined because PCs running Linux became good enough; selling commodity hardware is a different business model (https://yarchive.net/comp/sgi_market.html) and it's incredibly difficult to move down market.
Oracle acquired Sun because they didn't want Java be owned by a competitor (https://www.reuters.com/article/us-oracle-alphabet-trial/ora...). Java was also why IBM offered to buy Sun; it seems hard to consider Java a business failure when it's most of the remaining value of the business.
Additionally Java has been a major success to those that played into the ecosystem, people keep forgetting there were several (some are still around) commercial implementations of Java with features not available on the free beer JDK like AOT compilation.
The way Sun managed Solaris and SPARC hardware had more impact on their wallet than Java.
Java ultimately kept their declining hardware and operating systems afloat for longer than they would have been otherwise.
Just as Java is an afterthought to Oracle's database sales today, Java originally was an afterthought to Sun's workstation sales. Java was never intended to make money directly but rather as a conduit into the money-making side of both owners.
The fact that Java remains at all today is a testament to the power of open sourcing something.
The company that created Java went out of business and was sold to Oracle for a fraction of its original worth. So Java was a business failure -- or at least I'd be interested to see someone defend Java as a business success.
So I think it's realistic to at least engage with their argument seriously rather than dismiss it.
The argument is that open source licenses are incompatible with the kind paid license they're offering their customers. These licenses pay for the salary of their skilled employees.
Oracle makes money EXACTLY the same way -- by selling commercial licenses to a non-open-source database. That's why Java can be open source and not bankrupt the company.
Again, the argument here seems to be Just come up with a different business that makes hundreds of millions of dollars and use that to pay for Wolfram !
-----
edit: Since this comment is highly upvoted and visible, I'll mention that I'm seeking funding for a compiler engineer for the Oil shell, which I just mentioned on the blog:
http://www.oilshell.org/blog/2021/12/backlog-assess.html#mor...
So I know from over 5 years of direct personal experience that compiler engineers don't just show up to your open source project and start implementing things! Even if you have tens of thousands of readers on Hacker News for years. (Oil has had 48 contributors but not very consistently, which is understandable.)
To be clear, I did not expect help! I have asked for it, but I thought I would be able to finish it myself. So it looks like hiring someone with specialized skills is the most realistic way to accelerate the project (now that the language design is in good shape).
This funding is to finish the Python to C++ translation, which is already half done. Example:
Oil's Parser is 160x to 200x Faster Than It Was 2 Years Ago http://www.oilshell.org/blog/2020/01/parser-benchmarks.html (lots of progress since then)
I'm applying for 50K euros of funding from NLNet. Also in the process of setting up Github Sponsors. E-mail me at [email protected] if you want to make a donation -- I think I will need at least $250K to properly pay for this position. If you're a professional programmer and spend 2 hours fussing with a shell script, that's probably worth a few hundreds dollars.
I'll start mentioning this in more posts when everything is set up, but I thought I would use this extremely relevant topic to raise awareness. Programming languages don't pay for themselves! https://www.oilshell.org/release/latest/doc/oil-language-tou...