Forgot your password?
typodupeerror
Open Source Software Technology

Navigating the Vast Ocean of Open Source 23

Posted by Soulskill
from the we're-gonna-need-a-bigger-boat dept.
Nerval's Lobster writes "Open source is no longer relegated to the discount software vendor that serves cash-strapped startups. In enterprise software development these days, open source is not only immensely valuable, but increasingly crucial to stay competitive in releasing high quality software at regular intervals in a world where technology is changing so fast and every edge matters. Today, rolling your own logging package instead of using something like log4j is as silly as trying to build your own web server instead of using Apache httpd was 10 years ago. Still, there are other components like guava that are less well known, but are currently making a name for themselves as libraries that can take the solution you are building to the next level of sophistication and quality. Just knowing they exist — and knowing where they fit — can help you design and build better software at a lower cost. In addition to conducting a traditional build versus buy analysis, it's critical to think about the maintenance and support story surrounding an open source package. This article lists some things to consider and questions to ponder."
This discussion has been archived. No new comments can be posted.

Navigating the Vast Ocean of Open Source

Comments Filter:
  • by QuietLagoon (813062) on Saturday November 03, 2012 @11:13AM (#41864523)
    ... other than it was written by a person who used unsupported software then complained about the lack of support.
  • by wdef (1050680) on Saturday November 03, 2012 @12:09PM (#41864923)

    Speaking from experience here and also as a strong believer in FOSS: the single biggest hassle with using certain FOSS code for commercial use/adaptation can be getting hold of the right person to modify/fix the code for use in a for-profit project. You'd think it'd be easy, right? Just post to the dev list and start a discussion offline about paying them for adaptations, right?

    Wrong. Usually doesn't work if you go in cold and the devs don't know who you are, even if you start shaking bags of cash at them over email. Many foss developers work for other companies and aren't interested. If it's sophisticated, difficult code, hiring someone to get across and then hack the code base may just be too slow a fix commercially. This is why Google, Red Hat, Canonical etc snap up key foss developers in challenging areas such as the kernel. Even if their pool of key developers don't know how to fix something, chances are they might know how to get hold of the right person. Notice the inbuilt randomness of "chances are".

    The ad hoc-ness of that situation is just not acceptable in many industries. They want to pick up a phone and get the work done now, not chase people around on an obscure development list trying to hire them. It's no wonder that Microsoft et al had the game sown up for so long and that it took a huge company with massive resources (Google) to put linux on so many devices that weren't server boxes.

  • Only point #10... (Score:4, Insightful)

    by vikingpower (768921) <exercitussolusNO@SPAMgmail.com> on Saturday November 03, 2012 @02:05PM (#41865865) Homepage Journal
    ... on this guy's list makes sense to me, for having encountered the situation in practical life, more than once. Traffic-attracting set-up or not, the article does make some sense. I would recommend it to younger guys preparing to do their first software project as a team leader, project manager or software architect.
  • by rueger (210566) * on Saturday November 03, 2012 @02:23PM (#41866075) Homepage
    Minor quibbles: it's friggin blog post, not an "article." And it's not about "navigating an ocean of open source" in any sense that you might imagine. It's more along the lines of an About.com "Here are ten tips for using Open Source in your business" page.

    However, there's a lot of truth in it, and points well worth discussion.

    When, exactly did we wind up being our own support desks? When did Google, forums, and bug lists become the primary resources for solving problems with software and hardware?

    I'm staggered at the issues that I have with a Google branded Android phone running Google branded apps within Google branded operating system. At the end of the day it is IMPOSSIBLE to get any response from anyone at Google to any problem.

    This, to me is everything that's wrong with Open Source, even Corporate Open Source; an attitude that goes way, way back to the days downloading Linux boot floppies by modem, then struggling to get X windows or a modem to work using only Man pages and snotty comments from geeks.

    There was a time when I would spend hours or days fighting with recalcitrant software trying to make it work. I can no longer be bothered. I know I can install a Windows or Ubuntu variation and they'll just work. I know that LibreOffice will just work 90% of the time. After which I'll boot up Windows and use MS Office.

    Beyond that I'll try a software package (Android apps too) once and if it doesn't work out of the box I'll toss it. And if all else fails, yeah, I'll pop the money to buy a commercial, closed source package. Life is too short.

"Consequences, Schmonsequences, as long as I'm rich." -- "Ali Baba Bunny" [1957, Chuck Jones]

Working...