search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
ideology


out of the equation Keeping


Is the debate on open- source vs. proprietary software for scientific computing just irrelevant


ideology? Andrew Jones investigates


C


apable soſtware, not fast hardware, is the real differentiator of scientific computing. However, even though soſtware is so important (or maybe


because it is so important), there is much disagreement on the best way to create and use soſtware for scientific computing. One of the most recurrent themes is that of


open-source vs. proprietary code. Tis debate is oſten painted with the idealistic open-source evangelists on one side, and the business- focused proprietary soſtware advocates on the other. Tis is, of course, an unfair depiction of the topic. In reality, when debating open- source vs. proprietary, several issues tend to get conflated into one argument – open- source vs. closed-source, free vs. paid-for, restrictive vs flexible licensing, supported vs. unsupported, code quality, and so on. Open-source really means no more and


no less than making the source code readily available to anyone. Tus, open-source makes no statement as to the licensing conditions for using the soſtware, whether there are charges for using the soſtware, whether the soſtware is supported, or actively developed, or any good, and so on. Closed-source means that source code is not readily available, but makes no comment on issues like licensing, costs, support, and quality. Making the source code open means that


people can look at it, help spot and fix bugs, verify that the code does what is promises and help port to new hardware. Keeping the source code private helps protect any IP or competitive advantage believed to be in the code. If the code is subject to restrictive licensing or usage fees, then closed-source helps prevent people from using the code against the licence or without paying. If such a


12 SCIENTIFIC COMPUTING WORLD


@scwmagazine l www.scientific-computing.com


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36