Language Selection

English French German Italian Portuguese Spanish

What happens to Sun's open-source software now?

Filed under
Software

The deal is done. Oracle now owns Sun. Oracle's main message to Sun's customers seems to be "Don't worry, be happy." That's not easy when Oracle is not explaining in any detail what it will be doing with open-source software offerings like MySQL, OpenOffice, and OpenSolaris.

In general, we know that Sun's software product catalog will be cut back and that many Sun staffers will soon be laid-off. Historically, when Oracle acquires a company, deep cuts are the rule. For example, Oracle fired about 5,000 workers after acquiring PeopleSoft. This time around Oracle is saying that there will be only about a thousand layoffs. In particular, although no one is going on record, it's feared that Sun's open-source groups will take the brunt of these cuts.

No one is going on record either with what's going to happen to Sun's open-source software. We do know that at least one small open-source project, Project Wonderland, a Java-based platform for developing 3-D virtual worlds, has been cut off from Sun resources. In addition, Oracle is shutting down Project Kenai, Sun's collaborative hosting site for free and open source programs.

But as for the big open-source projects, after talking with people close to the situation, no one at the former Sun knows what Oracle has in mind, and Oracle isn't talking.

Rest Here

Also: Linux MySQL distros meeting in Brussels




re: Sun

So after years of ranting that Open Source is soooooooooo much better then propriatary software - when it actually hits the fan - we find out it isn't?

If your shop depending on any of those open source projects - and those projects die - you're no better off then if it was a commercial product.

Care to compare the cost to setting up your own dev team (with bottomless funding requests), or just buying (fixed cost) licenses to stuff that already works? Yeah, big surprise there.

So why is open source so much better?

Isn't it obvious?

Sure, for some reason or another an open-source project might die as well. It's not just about money since lack of user interest would be the real killer.

I don't understand how you can't see the logical benefit of open-source in this aspect? A proprietary piece of software is dead whenever a business decision is made to drop its support. That's a serious issue for business, something you probably are familiar with, and especially difficult to deal with when a big manufacturer drop driver support of fairly new products.

An open-source project on the other hand might survive as long as its user base stimulate development; it's not bound to be done under the roof of a company initially sponsoring it. It's even possible that they who pick up a project in danger are more talented and have clearer visions than the team dropping it. That's very difficult to achieve with closed-source patented software.

Therefore the shop deciding on which software to use can't be foolishly guided by a dogma that closed-source software equals long term support, just as it can't be naive and this that open-source software will eternally travel though universe with never ending improvements. Looking at this matter as you suggest vonskippy isn't practical. If you can't or it isn't economically beneficial to maintain the software in-house, do your homework and make research before deciding what route to take (be it close- or open-source).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

  • Security updates for Thursday
  • Security Tips for Installing Linux on Your SysAdmin Workstation
    Once you’ve chosen a Linux distro that meets all the security guidelines set out in our last article, you’ll need to install the distro on your workstation.
  • Fedora 26 crypto policy Test Day today (2017-03-30)!
  • Open-source developers targeted in sophisticated malware attack
    For the past few months, developers who publish their code on GitHub have been targeted in an attack campaign that uses a little-known but potent cyberespionage malware. The attacks started in January and consisted of malicious emails specifically crafted to attract the attention of developers, such as requests for help with development projects and offers of payment for custom programming jobs. The emails had .gz attachments that contained Word documents with malicious macro code attached. If allowed to execute, the macro code executed a PowerShell script that reached out to a remote server and downloaded a malware program known as Dimnie.
  • A scramble at Cisco exposes uncomfortable truths about U.S. cyber defense
    When WikiLeaks founder Julian Assange disclosed earlier this month that his anti-secrecy group had obtained CIA tools for hacking into technology products made by U.S. companies, security engineers at Cisco Systems (CSCO.O) swung into action. The Wikileaks documents described how the Central Intelligence Agency had learned more than a year ago how to exploit flaws in Cisco's widely used Internet switches, which direct electronic traffic, to enable eavesdropping. Senior Cisco managers immediately reassigned staff from other projects to figure out how the CIA hacking tricks worked, so they could help customers patch their systems and prevent criminal hackers or spies from using the same methods, three employees told Reuters on condition of anonymity.
  • NTPsec: a Secure, Hardened NTP Implementation
    Network time synchronization—aligning your computer's clock to the same Universal Coordinated Time (UTC) that everyone else is using—is both necessary and a hard problem. Many internet protocols rely on being able to exchange UTC timestamps accurate to small tolerances, but the clock crystal in your computer drifts (its frequency varies by temperature), so it needs occasional adjustments. That's where life gets complicated. Sure, you can get another computer to tell you what time it thinks it is, but if you don't know how long that packet took to get to you, the report isn't very useful. On top of that, its clock might be broken—or lying. To get anywhere, you need to exchange packets with several computers that allow you to compare your notion of UTC with theirs, estimate network delays, apply statistical cluster analysis to the resulting inputs to get a plausible approximation of real UTC, and then adjust your local clock to it. Generally speaking, you can get sustained accuracy to on the close order of 10 milliseconds this way, although asymmetrical routing delays can make it much worse if you're in a bad neighborhood of the internet.
  • Zelda Coatings
    I assume that every permutation of scams will eventually be tried; it is interesting that the initial ones preyed on people's avarice and dishonesty: "I will transfer millions to your bank account, then you share with me" - with subsequent scams appealing to another demographic: "I want to donate a large sum to your religious charity" - to perhaps capture a more virtuous but still credulous lot. Where will it end ?

Tizen and Android

Linux and Linux Foundation

Mesa and Intel Graphics